July 12, 2016 at 7:03 am #1436
Please publish on the rapidscada.org website the complete documentation for RapidScada and the .tbl interfaces, including list of all parameters with their descriptions, documented examples and syntaxJuly 12, 2016 at 8:35 am #1437
All the existing manuals are published.
If you edit *.tbl by Table editor, all parameters are accessible via GUI.
If you edit them manually, see ServerRoom.tbl as an example.
If something is not clear, ask on this forum.July 12, 2016 at 10:23 am #1438
The most problem could be is editing the configuration database in Linux, because it has Microsoft SQL Server Compact (*.sdf) format. This format is used for editing only, not for operating. I don’t know the context of your project and task. If you described it, I could generate an idea how to solve it in optimal way.July 12, 2016 at 10:31 am #1439
All the existing GUI apps those are used for system configuring (excluding view editors) will be joined to a one application. It is possible to make this application support Linux with help of Mono framework. The view editors will be ported to web.July 12, 2016 at 10:33 am #1440
> All the existing manuals are published
where exactly? I don’t see any link to it on the rapidscada.org website
> If you edit *.tbl by Table editor, all parameters are accessible via GUI.
How can I access it, since I don’t see it (neither the SchemeEditor) neighter in the download section of the page, nor in the downloaded file
> If you edit them manually, see ServerRoom.tbl as an example.
The params aren’t documented in it
> If you described it, I could generate an idea how to solve it in optimal way
How about replacing the Microsoft SQL Server Compact (*.sdf) format with more universal one, like for example sqlite (*.db)?July 12, 2016 at 10:55 am #1441
The params aren’t documented in it
Yes, but it’s easy to guess and try 🙂
The format is straightforward.
How about replacing the Microsoft SQL Server Compact (*.sdf) format with more universal one, like for example sqlite (*.db)?
It is a good and cross-platform alternative. Anyway it’s hard to configure the system by standard DB editor without a specialized GUI editor.July 12, 2016 at 11:15 am #1442
In short, the following things allow you to use Rapid SCADA on Linux without Windows:
– Convert the configuration database to SQLite and develop an editor for it
– Document all the XML configuration filesJuly 12, 2016 at 12:20 pm #1446
> Anyway it’s hard to configure the system by standard DB editor without a specialized GUI editor.
> Convert the configuration database to SQLite and develop an editor for it
there is no need to develop a special *.db editor since such ones are already avaliable, like for example: https://github.com/lazierthanthou/sqlite-manager. It has even a Firefox pluginJuly 13, 2016 at 6:19 am #1447
Specialized editor allows to choose values for foreign keys, has utility functions such as input channel generator, clone channels, creating channel map those significantly reduce work.July 13, 2016 at 7:41 am #1448
that’s true, but developing one would require time and resources (like for example programmers, money, etc.) and this would delay much the development process.
If I may, then I would propose to convert the database files to SQLite and till the editor get’s ready, allow to use the SQLite database managemnt and edition software.
My question is, who would develop such editior about You wrote and would it be a OpenSource, or other free kind license or a commercial product. If commercial then how much would it cost.
Please take it into attention that not every one can afford themself to buy a commercial license, so this why a free license would be the best choice here.July 13, 2016 at 12:02 pm #1449
I think that such editor should be open source because the core of Rapid SCADA is open source and the open source model is very powerfull. As usually happens in the open source world the development of the required feature could be sponsored to get it in time.
Let’s talk about the quick solution: convert DB to SQLite. This work consists of 2 subtasks:
1. Covert DB itself.
2. Develop a utility that will “pass the configuration database to server app”. It means convert SQLite to *.dat files used by the Rapid SCADA apps.
I can send you ER model of DB if you send me email request. It helps you to estimate how difficult to configure the system manually.July 14, 2016 at 1:22 pm #1454
> 1. Covert DB itself.
> 2. Develop a utility that will “pass the configuration database to
> server app”. It means convert SQLite to *.dat files used by the
> Rapid SCADA apps.
ad. 1: I think that there online some converters with could do that
ad 2: wouldn’t be easier to implement a direct support and actions on the database instead of doing so many additional (and mostly unnessecary) steps with would make the usage more dissicult?
I suggest that instead of *.dat use the extension *.db because not every software can correctly reorganize, read and write it.
About the app server… have you heard about the GO language? there is quite easy to create in it a system independant (it will be able to get compiled on Windows, Linux and Apple OS) server with could make the data accessable
You must be logged in to reply to this topic.