Thanks for the effort though, CraigWeb! Welcome to the ecosystem!

Hi Joe,

Interesting use of the TCP/IP data source! What have you gotten working so far? I hadn't used it as an HTTP GET'er before, but it works! I think you're going to need more HTTP in your read command. I would open the developer tools when you request the page in your browser and see the GET request that loads the page. You may need to have some of those headers in your HTTP GET, and you may need the double newline at the end of HTTP messages. For instance, to get the /help.htm page in my data source, I had to supply a Host header in my read command, like,

GET /help.htm HTTP/1.1\nHost: localhost\n\n

I think you'll also want to adjust your write commands. I didn't seek how write commands are specified in the manual (if you can post the relevant section I can look), but if you send a constant like 1 that will be the only thing sent when the value is set, regardless of what the value is. But, I may be misreading, that may be an l which should turn relay 8 on. The main issue I think you're going to have is setting the values, since that requires particular ASCII characters for turning on or off a relay. I think the easiest way to handle that will be either

hard code the logic for what character means on/off for what relay into your interface. Have every toggle on the interface set out the appropriate character to the same point, which is only settable and has the settable command VALUE. If you are comfortable with old Mango pages not having these points be settable, and only opening/closing the relay through an appropriate point, this is a good option. Have a level of indirection for points. This would be a scripting data source or some arrangement of point links that enabled virtual points to receive sets, which can then be translated into the appropriate character and sent to the device, or which the device's response to polling is set into. Similar to 1, create a point link that maps a human input to the appropriate character, then set that out to the device. For instance, set values to a virtual point like "1-ON" and the point link convert that into e and set that out the command point. Then use this virtual point when you need to open or close a relay, and the other point for current relay status. Edit: point link on this one, not meta

Given solution 3, you may consider using the HTTP retriever for getting values and only use the TCP/IP data source to send the relay set open/closed character.

Hi Joe,

Sorry this took so long to respond to. Is that toggle function working for you? You could tie your button to call a function that calls the toggle function several times,

function toggleStuff() { togglePoint("F6_B01_R01"); ... togglePoint("F6_B01_R08"); }

but perhaps your question is more complex? There are also endpoints for updating several data points at once, if you wished to make fewer API round trips, the /rest/v1/data-points endpoint (not data point xid, must be supplied in each point in the list in the PUT content.

Also, have you tried using the ES configuration module's network tools on the system settings page? If you can log into the Mango as admin, you can change the network settings if that module is installed.

@phildunlap said in Mango v3:

exact

thanks phildunlap ,

what i meant is if i installed mango service on a virtual operating system (lets say windows server 2012 on vmware environment) will mango handle communicate with mod-bus serial devices.

regards;

Hi Joe, welcome to the forum. This will really depend on the required settings from the device. Start by setting the baud rate and selecting your serial port. Then I would use the test tools to read some of the registers to determine which ones you want and that communication is working. Next add data points and set your polling rate and enable the data source and data points. You should then be able to see the data updating on the Watch List.

Here is a helpful article: https://help.infiniteautomation.com/configuring-data-sources-and-data-points/