Hi all,

I am using Mango to get MODBUS data from various sources, including RTU's residing on Xbee nodes via a Digi Connectport X4.

I would like to POST data to the Etherios cloud using the Mango HTTP sender publisher, and have successfully tested this using HTTP POST with a Python Script.

However, I am unsure as to the format of the Static Parameters in the Mango HTTP sender properties.

The path is http://<hostname>/ws/DataPoint/one
I need to add the following snippet of the HTTP POST method to a KEY:

<DataPoint>
<staticId>one</staticId>
<data>42</data>
</DataPoint>

I cannot use just the two entries:
KEY=data and Value=42
KEY=staticId and Value=one
Somewhere I need to add the "DataPoint" header

Obviously the value "42" would be where I put the Mango point "Parameter name", but
I am first trying to send just a static value.

The "staticId" is the Etherios Data stream ID, and remains constant.

Can anyone shed some light on this?

Hi all,

I am using Mango to get MODBUS data from various sources, including RTU's residing on Xbee nodes via a Digi Connectport X4.

I would like to POST data to the Etherios cloud using the Mango HTTP sender publisher, and have successfully tested this using HTTP POST with a Python Script.

However, I am unsure as to the format of the Static Parameters in the Mango HTTP sender properties.

The path is http://<hostname>/ws/DataPoint/one
I need to add the following snippet of the HTTP POST method to a KEY:

<DataPoint>
<staticId>one</staticId>
<data>42</data>
</DataPoint>

I cannot use just the two entries:
KEY=data and Value=42
KEY=staticId and Value=one
Somewhere I need to add the "DataPoint" header

Obviously the value "42" would be where I put the Mango point "Parameter name", but
I am first trying to send just a static value.

The "staticId" is the Etherios Data stream ID, and remains constant.

Can anyone shed some light on this?

Just as an update on this post.

Although I would recommend setting packetization and character timeouts as above, this was not the underlying problem.

zzzz....zzzz....zzzz WAKE UP!!! Can't respond to MODBUS polls when it is asleep!

I thought the router or coordinator the bee was attached to would buffer the request and then send it on when it wakes,
but I could not get it to do this. even with short sleep/wake cycles under the poll timeout value.

So I made sure all my nodes are running ROUTER firmware, so the do not go to sleep.
You could run end device firmware and set the sleep mode to "Pin Sleep" and then wire
the sleep pin permanently LOW, but using ROUTER firmware allows the radio to participate in the MESH.

@JoelHaggar said:

I'm not aware of a terminal window you can open. You just start and stop the service by right clicking on the service.

Joel.

I believe now I can access this information via the logs, which serves the purpose.

H

Thanks for the reply Joel.

I still can't connect on my mobile, so I asked another
friend to connect from another state on 8080/safari and he had no problems.

So I am going to put it down to poor internet connectivity here
in Australia and/or an issue with my mobile co.

One thing that concearns me with the iframes, is someone, or
many people could copy the iframe address out of my website source
code and paste it in another website/s. This could cause connectivity
issues and misuse of data. it would be good if iframes could be more secure
somehow.
A workaround for me would be to add my company logo to the graphical display.

Thanks Joel

Hi all,

I have had my 1.12.4 server running for about a month.
I have BEEN able to connect to:
8080 on my LAN
8080 on the WAN (Phone and PC)(Static WAN IP)
8080 via iframe remote view from my website.

Now the 8080 WAN has dropped off, but I can still connect via the other two methods.
I am getting gateway timeouts.

I have called my ISP, they said they have not blocked 8080.(anyway the iframes are getting through)
I have tried changing everything to 8081, no success.
I have obviously restarted and checked firewall exceptions and port forwarding.
Also I can access my webcams and modbus TCP devices directly from the WAN.

I'm using M2M as a test bench before moving to (and hopefully selling) Mango Automation,
and remote access is a must.

I recently ran a Java update, but that was JRE not JDK.....????

Any ideas? Can anyone throw me a freakin bone here?

Hi all,

I have had my 1.12.4 server running for about a month.
I have BEEN able to connect to:
8080 on my LAN
8080 on the WAN (Phone and PC)(Static WAN IP)
8080 via iframe remote view from my website.

Now the 8080 WAN has dropped off, but I can still connect via the other two methods.
I am getting gateway timeouts.

I have called my ISP, they said they have not blocked 8080.(anyway the iframes are getting through)
I have tried changing everything to 8081, no success.
I have obviously restarted and checked firewall exceptions and port forwarding.
Also I can access my webcams and modbus TCP devices directly from the WAN.

I'm using M2M as a test bench before moving to (and hopefully selling) Mango Automation,
and remote access is a must.

I recently ran a Java update, but that was JRE not JDK.....????

Any ideas? Can anyone throw me a freakin bone here?

Thanks for the reply Joel, but I can see the services window and see tomcat running, but I cannot see how to open the console.
Any other ideas?

Hi all,

Probably a quickie for all you Windows Guru's out there.
I am running 1.12.4 and have it running as a Windows service on XP. It now runs TOTALLY in the background,
I mean TOTALLY! The console is nowhere to be found.
Can anyone tell me how to see then console? I need to see what is going on.

Hi all,

Probably a quickie for all you Windows Guru's out there.
I am running 1.12.4 and have it running as a Windows service on XP. It now runs TOTALLY in the background,
I mean TOTALLY! The console is nowhere to be found.
Can anyone tell me how to see then console? I need to see what is going on.