Hey mate, can the underlying host machine connect to the mail server on that port?

Even try just...

telnet smtp.gmail.com 587

See if you get an answer similar to...

220 smtp.gmail.com ESMTP p9sm17466733pfq.136 - gsmtp  

Although it does mention TLS so 587 should be correct? Certificate error is weird.

Thanks mate, I'll give it a go.

Hey Guys, I'm trying to work out if there is a way to access previous values in a data point's history from the scripting data sources so I can work out flow rate from water level data point in tanks.

I'm thinking I should be able to look at the difference in the values and work out the flow rate in litres per hour or litres per minute, then just update a virtual data point to display it. It's probably so simple I can't see it for looking :O)

I know PREVIOUSVALUE(datapoint) exists as I use it frequently, but is there one for say a minute ago?
Or could I simply mirror a data point value but only update it once a minute, then just work out the flow rate by comparing the current value to the previous only.

Cheers
Dan

I tried a little bit of script magic to see if it would do it at the same time, but I think still not quick enough..

I guess I need to combine the two 16 bit values into one 32 bit value, then write that to the single register, which should extend to the second yeh?

ok sweet as, thanks for that I'll give it a go

So I emailed DSE from their website contact form for shits and giggles, not really expecting to hear back... A nice fella from the UK emailed back almost immediately with all the official docs on the thing. I thought that was awesome.. Anyway, here's a more explanatory version of what I had found originally...

So looking at that, I should be sending 35702 to 4104 and 29833 to 4105
:)
I'll give that a go..

OK, thanks Craig. I have a data point I made earlier which I will go back to and see what it does.
Thanks

Yeh the Mango instance is a few hundred ms away. It seems to work fine reading in voltages and RPM's and the like. Just been playing up a little today probably due to the weather.
Even when it was working fine the write function still didn't seem to be the correct syntax.

With a bloody big hammer.

Bugga, still same timeout message when network is responding better.

com.serotonin.modbus4j.exception.ModbusTransportException: java.net.SocketTimeoutException: connect timed out

If I interrogate a standard read point it works fine.