Forum Replies Created
-
Posts
-
It’s possible that received values are rounded by the driver. I’m sure sure. You should get channel data as a byte array and play with it.
Do you use MQTT or Modbus protocol?
Could you make a screenshot of a device data page from Communicator?Hi,
Now as my data is changing frequently instead of using GET call, is there data streaming API call available by which my application will read the data as soon as it change ?
Try using DrvMqttPublisher driver which publish data on change by MQTT.
Do you mean the page in the image4 in the drive I shared? And what should I put in the tag?
Yes, image4.
Check this example https://ibb.co/ZMBdJBdHello,
Check this answer.So, does this mean that the Archives table can cover up to 32 entries at most?
31, because the archive mask is signed integer.
When writing, it’s possible to write to multiple archives simultaneously, so using a mask is appropriate.
However, when reading, you can only read from a single archive, so a bit is used.Correct.
Also check the ArchiveMask class.I’ve checked the source code of the driver. It converts numbers to Double.
Do you have any ideas on how to get around this?Hi,
It looks like Node Red does not send any data to the OPC client. If Node Red supports OPC UA instead of OPC DA, use OPC UA.You can try setting “Read synchronously” checkbox for the subscription.
Hello,
Channel values are converted to strings automatically when displayed. If you face displaying issues, please provide screenshots.How do you transfer data between CodeSys and RapidSCADA?
By default, channel values uses Double type. If you change a channel to use Int64 type, it can help. However, it may depends on a transfer method.
