Forum Replies Created
-
Posts
-
Kevin, if you would like, I can help you to set up the system using remote connection. Is is payable service http://rapidscada.org/services/remote-troubleshooting/
Hi Kevin,
The default configuration uses formula, for instance, in the channel 101. Is there any difference with 901? You could try using the simplest formula Cnl – 1 for the test reason.
How about trying the new SCADA-Communicator that contains the required function?
1. Download the update from http://rapidscada.org/download/scada_4.5_update.zip
2. Rewrite the existing files.
3. Continue our discussion…Hi,
Looks like OK:
– input channel number is 901,
– value 720896 is hex 00 0B 00 00.The result of conversion doesn’t shown in SCADA-Communicator. You can watch it in a web page or with help of SCADA-Server GUI.
What is the value of the channel 901?Could you post here the content of C:\SCADA\ScadaComm\Log\kpXXX.txt ?
where XXX is your device numberpublic double SwapBytes() { UInt32 val = (UInt32)CnlVal; byte[] bytes = BitConverter.GetBytes(val); byte[] newBytes = new byte[] { bytes[1], bytes[0], bytes[3], bytes[2], }; return (double)BitConverter.ToUInt32(newBytes, 0); }How to use:
1. Run SCADA-Administrator
2. Open Formulas table and add this method.
3. Open Input channels table and find the appropriate input channel.
4. Tick Formula used field.
5. Input SwapBytes() into the Formula fieldIf it doesn’t work at once write here)
Play with order of bytes.Hi Kevin,
You can swap bytes using formulas which are edited by SCADA-Administrator application.
Seeing that Modbus driver is currently improved it is possible to implement this function in Modbus Template Editor of Rapid SCADA Modbus driver. Probable within 2 weeks.Does CeweMod provide any diagnostic tools, such as web console, for example?
In compare with other Modbus devices it’s behavior is strange.Hex values shown in log also contains address, number of bytes, etc. That is why they are not 0 when data is 0.
If meter shows not 0 voltages, there is a mistake in received data. May be you send a request to CeweMod support?Hi Bret,
Step Two. Try to display data in a web page using the default configuration.
1. Run SCADA-Communicator.
2. Tick “Use SCADA-Server” back.
3. Start SCADA-Server and SCADA-Communicator services.Then click to your device tree node in SCADA-Communicator and post here the content of “Device Data” page. The easiest way is copying it from the file C:\SCADA\ScadaComm\Log\kp021.txt
Voltages already should be decimal. To convert energies we need improve KpModbus.dll possibilities.
Hi,
It’s weird:
If “Address” field is 0, the result is allways [02] ILLEGAL DATA ADDRESS!
If “Address” field is 1, there are some success results and some errors [02].
If “Address” field is 2 or more, all the test requests is OK. But voltages and energies are 0. Is it normal? Do you have a clue why address must be 2 or more?I’ll send you a template file.
OK, send it to the e-mail written here http://rapidscada.org/contact/
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.
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.
