[Mikhail]

Try changing 465 to 466 in the template.

I would like to take advantage of your offer and test the new version of Modbus driver with your device when the driver becomes ready. It would be great.

[Mikhail]

The next steps:
1. Open Device Template Editor.
2. Add element group by clicking the toolbar button.
3. Input any group name.
4. Choose “Input Registers” Data table (as written on the 5th page of your manual).
5. Set “Start element address” to 465.
6. Set “Element count” to 8 (from 465 to 472)
7. Save the template and restart SCADA-Communicator service.

Then watch the log and post it, please.
At this time KpModbus.dll can convert max. 4 bytes values. But in your case you need to convert 8 bytes. Fortunately, Modbus driver is now under upgrade and I’ll try to implement required functionality in the next week.

While waiting, you could tune the other necessary registers. Most of them are 4 bytes or less.

[Mikhail]

Hi Bret,

Fine. This log means that the connection is OK, but you need to tune your device template. Look for register addresses in the documentation of your device. After it is found, copy an appropriate part of manual here.

[Mikhail]

5a. Your Modbus TCP device is CeweMod gateway.
5b. Address field probably should contains the Modbus ID of the meter.

[Mikhail]

We will go the simplest way based on the default configuration.
Step One. Connect to the Device
1. Run SCADA-Communicator.
2. Untick “Use SCADA-Server”.
3. Untick “Active” of the Lines 2 and 3. The line 1 must be active.
4. Select Line 1, go to “Request Sequence” page and click on the first device in the grid.
5. Set “Call number” to the IP of your device.
6. Set “Command Line” to MyTemplate.xml
7. Apply settings changes.
8. Click “Device Libraries” node, then select KpModbus.dll and click “Properties”.
9. You should create a template of your device using Device Template Editor according the device documentation. Save it to file MyTemplate.xml. We can discuss it in details.
10. Start SCADA-Communicator service and watch the communication state.

• This reply was modified 10 years, 9 months ago by Mikhail.

[Mikhail]

Hello Bret,

There are a few articles which can help: http://rapidscada.org/category/articles/
If you read them and the situation is still not clear, let’s do step-by-step configuration right here in this topic.
What communication protocol is supported by your device?

[Mikhail]

My assumptions how the controls work:
– They locate in C:\SCADA\ScadaWeb\controls\
– Each control set has its own folder, for example, C:\SCADA\ScadaWeb\controls\myControlSet
– Each control is a div in DOM tree
– SCADA-Web “knows” what channels every control needs
– SCADA-Web periodically execute update control method
– A control can execute JavaScript methods for redirect to another view, send command, draw chart and show custom dialog

[Mikhail]

Hi,
Good news )

API for including components in SCADA-Web has not ready yet. For starting development right now you should develop some kind of shell that will be changed to API when it is ready. You can create custom web page like written here http://rapidscada.org/scada-web-development/ Then embed your controls in the page.

New schemes engine will be based on HTML5 and JavaScript. I suppose that each set of visual controls is a set of xml file that describes controls, js files, images, etc.
Every control should implements methods those will be executed by the engine, for example, Update, GetBoundChannels.

Please make a fork from https://github.com/RapidScada/SCADA/tree/develop
Later we can sync like described here (Fork & pull) https://help.github.com/articles/using-pull-requests/

Let’s discuss here any ideas about creating the controls.

[Mikhail]

Thanks for the good idea. It can be useful in some cases. But I’m not sure that this function will be implemented in the nearest future. If you would like to purchase it, please contact me in private.

[Mikhail]

Thanks. I’ve found the cause. It is a restriction of communication protocol between SCADA-Server and SCADA-Web. You can receive max. 65535 points. This means that you can store minute data every 2 seconds.

[Mikhail]

What about the other my questions?

[Mikhail]

Has you tried to view the chart using different browsers? Is there any difference?
If you press Show Data button, the data in the grid is correct?
Please save Diag.aspx by a browser and send to info@rapidscada.org

[Mikhail]

Use image hosting like http://postimage.org/
then insert a link to your image.

[Mikhail]

Could you clarify which parameter have you set to 1 second? Screenshot also can help to answer your question.

[Mikhail]

Thanks a lot for the detailed description!
Does you system work correctly at the moment?

For OWEN devices which use Modbus I recommend to choose native Rapid SCADA Modbus driver because it is more stable and lightweight than OPC.
Have you tuned Modbus connection between Rapid SCADA and OWEN?

[Author]

Posts