December 17, 2021 at 3:03 pm #9795
I’m working for a company that is considering using Rapid Scada for future projects, I’ve installed it and made a couple of Scheme’s, but I have a couple of questions when it comes to the tools and layout.
For me a scada system should have basic functions like
* motor/valve/actuator control
* sensor/feedback display
When there are a lot of valves/motors to control, it should be possible to have a group/genie/faceplate function where you can edit the look and behavior for a central/master one, with preferably a popup for control, and specify input/output of the group.
I can’t seem to find this function, I would really appreciate if there is a way to do this.December 20, 2021 at 2:00 am #9802JWParticipant
I’m not sure if I understand you correctly. Do you mean create a template for 1 machine (with pictures, texts, buttons), then apply the template to multiple machine?
Now there is no such function. I use a workaround for similar requirements.
The scheme .sch file is actually XML file. I create 1 set of the machine manually, then write a script to edit the .sch file, copy and multiple the manually created one, and change x-y coordinates, input channels and etc…December 20, 2021 at 8:34 am #9810
Please check the Image Pack from https://rapidscada.org/download-all-files/
You can put a Static or Dynamic Picture component on a scheme and use one of the above images. To prepare a scheme background it’s comfortable to use a 3rd party editor like Microsoft Visio, Libre Office Draw or Google Drawings, then export an image it to SVG and use in a scheme.
To copy/paste a group of components, hold the Ctrl button and select components by a mouse.
Also Scheme Templates can be useful if you have several equal schemes. The details about templates are here https://rapidscada.net/doc/content/latest/en/software-configuration/creating-views.htmlDecember 20, 2021 at 8:36 am #9811
Improving schemes is in the plans.January 7, 2022 at 9:39 am #9858
Well, there are several things, so I’ll try to rephrase and make it a bit clearer.
Say I have 15 valves on a page that I want to control. I would like to create a popup that will open when either valve is clicked. The popup will display 3 buttons, sending 1 to open, 2 to close and 3 to reset. This should be a simple task linking each valve with the popup and the tag which is to be manipulated.
Is something like this at all possible?
For an operator to send numbers for operating valves isn’t very user friendly in 2022…January 7, 2022 at 11:19 am #9860
1. Create a scheme file for popup.
2. In the Interface table create 15 rows using the same scheme file as a scheme template.
3. Setup links on the main scheme to open popups by view ID.
If some item above is not clear, ask for details.January 7, 2022 at 12:20 pm #9861
Yeah, I have a scheme file for a popup and can open that via a link (which I personally would prefer would be available from a button as well, not just link)
but how do I set up these three buttons to send different values to the same (dynamical) output?
January 9, 2022 at 9:43 am #9874
- This reply was modified 1 year, 8 months ago by Pengatom.
By changing link properties you can make it appearance similar to a button.
Every link should reference to a different View ID. The views are defined in the Interface table, and all of them uses the same *.sch file. Different channel numbers of the same scheme file because of channel number shift (see scheme templates).January 10, 2022 at 8:52 am #9878
Ok thanks, appreciate your feedback!
This means that if I have a popup with 3 buttons and 15 valves I would have to add 45 output channels and use an xml file to link them together?
Would it be at all possible to add a new property for buttons and links? under the Output channel there could be an Output value, when clicking on the link/button this value would be sent on the specified output channel?
Maybe only valid for Send Command now, as the send command still would show the popup…January 10, 2022 at 9:48 am #9882
You need 45 output channels. Which XML file do you mean? Probably, you don’t need any special XML file.
> Would it be at all possible to add a new property for buttons and links?
It’s a good idea which allows to use less channels. I’ve added it to the backlog.January 10, 2022 at 9:56 am #9883
Yeah, I think adding this would make it more intuitive which command would be sent.
According to Scheme Template description on the bottom of http://rapidscada.net/doc/content/latest/en/software-configuration/creating-views.html I could add a xml file to link the 45 output channels to the 15 valves.
Unfortunately when I click the “Upload Configuration” button, the files and directory I create under C:\SCADA\ScadaWeb\config\ is deleted. Is there anything else I need to do to keep these files? Or place them somewhere else?January 11, 2022 at 11:34 am #9888
All files should be located inside the project: C:\SCADA\Projects\YOUR_PROJECTJanuary 11, 2022 at 12:09 pm #9891
Makes sense, please update documentation 🙂
Another thing that would be good is to be able to hide layers/zindex.
When placing objects on top of each other its impossible to click on items that are not on top, if it was possible to hide this layer/zindex, then it would save a lot of time with moving objects around to get to the background items.
Also, error messages, when something isn’t working (usually because of human error) it would be good to have more info for debugging. Instead of “your not allowed to open this” it would be good to know *what* I’m not allowed to open, maybe that it would say item 22, and I wanted to open 21, but I typed wrong.January 12, 2022 at 11:14 am #9902
Currently, you can also select components from a drop down list of the editor. If you provide friendly names to components, you can easily find them in the list.
> Instead of “your not allowed to open this”
Do you mean errors when a user opens a view?January 12, 2022 at 1:45 pm #9909
Yes, that is also true. Nice feature!
Yes, I meant the general error message. Would be good with a bit more detail for troubleshooting
- You must be logged in to reply to this topic.