Forum Replies Created
-
Posts
-
If you are planning to make your derived project open source, Apache License 2.0 have some requirements to the source code. I can provide more details.
> 1.Based on your response, am I allowed to change the product name and the product name?
It is not allowed to change the name of the existing product Rapid SCADA. You are allowed to create a new product based on Rapid SCADA with a new name.> 2.Regarding providing information about the original product, can I credit the product’s source in the “About” section of the Main Menu? Does this count as providing information about the original product? If not, please provide a concrete example.
It should be enough to provide a reference to the original Rapid SCADA in the About page.Ask, I’ll be glad to clarify any non-obvious points.
In short, according to Apache License 2.0 you can create a derived product with a new name, but you have to explicitly provide information about the original product.
In the HelloWorld project, PlgChart is active by default. Just click an item in a table view to display a chart.
Hi,
Definitely.
More info is hereA data source configuration file will appear in Communicator – Configuration files, named like DrvDsOpcUaServer.xml.
> I guess I would need create multiple UA servers and then set their ports in the xml configs?
Yes. Click the Properties button to open the data source options. Create a new configuration for for a data source. Find TCP port in the created file. Please let me know about the result.> Are you able to explain connection between devices under the communicator vs devices in the configuration database?
On Server level, there are calculated channels. While on Communicator level, only data received from the devices.It’s different. It’s mostly implemented using JavaScript and a bit of C#. See the example here.
Hi,
I suppose, yes.
Using the Administrator application, in Communicator – Data sources, create several data sources with the DrvDsOpcUaServer driver. Each data source works independently.Note that OPC UA server in Rapid SCADA operates on Communicator level. It can access data of Communicator.
We are planning to implement access to calculated channels on Server level, but it’s in the future.
Hello,
The most likely cause is a change in the computer code due to a change in the computer parameters.Please email us a new computer code shown by Chart Pro to check.
Hi,
I suggest to install Communicator and Agent on the local Linux-based controller to poll the Modbus device. Then configure sending data from Communicator to the cloud server.
