Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Performing a "set" on a Persistent TCP point
-
Is it possible to perform a set on a persistent TCP point such that the set gets pushed from the data source to the publisher?
-
@psysak If youn mean you have a mango unit publishing data and you want to be able to set back the other way, The only way to do so is to create a publisher going back the other way. That way when you set the datapoint on the mango unit receiving the published data the changes are pushed back to the initial mango unit doing the publishing. This does mean you would have a new datasource to capture and hold the set data.
-
As Fox suggested, it is not possible through the Persistent TCP points unless you use a second publisher. You can't set values to persistent TCP points generally.
The TCP/IP data source is another choice to a new publisher.
-
Has anything changed with Persistent TCP being bi-directional now in 3.5??
-
Well it does allow you to set points back the other way assuming you tick the checkboxes to allow it. I still stick to separate points, at the cost yes it means more data, but easier debugging and troubleshooting means I'm happy.
-
Has anything changed with Persistent TCP being bi-directional now in 3.5??
Yes. As Fox mentioned there is a setting on the publisher that permits it to accept sets. If,
- the "Allow data source to set values back" is enabled on the publisher
- the original published point is settable
- it is set as settable in the point created on the receiver
- and the user has set permission to the point on the receiver
then you can set to the received point. It will behave as though it were set on the publishing device, such that the value is only recorded as it is echoed back in the normal course of publishing.
