Forum Replies Created
-
Posts
-
Could you provide screenshots?
The driver works with numbers and 4-character strings. Long strings currently not supported by the driver.Hi,
Thank you for the info.
In addition, try changing the service user as shown here (ScadaComm6 service). There is a chance to run Communicator as a service.OPC DA (Classic) may be unpredictable. It’s a bad technology. You should use OPC UA instead.
The checkbox is in the screenshot https://ibb.co/wzjYYrNIn the screenshots, the number of the output channel is 201 while in the configuration form 631 is specified, which is wrong. It should be 201.
Name Constraints
Class names and namespaces are important. Locations of the classes’ files are about code style.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.
