Otherwise you can use it to trigger a meta data point or scripting data source and use RuntimeManager.sleep(2000);
Between each data point supplied in the context to be changed to the desired values after each delay.
After much research, I realised Mango cannot subscribe to the AWS IoT. This is because the TLS version used by AWS requires to upload 3 certificates (private key, public key and private cert). Whereas the mqtt datasource only uses the private cert.
Hope this can be updated or are there any other alternatives?
I found the following info on the 65533 value/� symbol:
U+FFFD (decimal 65533) is the "replacement character". When a decoder encounters an invalid sequence of bytes, it may (depending on its configuration) substitute � for the corrupt sequence and continue.
One common reason for a "corrupt" sequence is that the wrong decoder has been applied.
@Ricardo thanks, that all looks ok to me. Basically what is happening is that Mango uses a pool of TCP/IP connections to the database and when choosing one to use it tests it first to ensure it is still connected. In this case Mango sees that the connection is broken and the database pool library (Hikari) is logging that.
For some reason the database connections that Mango is opening are being closed. This is not normal. From your log posting I can see that the delay is pretty close to 10 minutes, so I would be looking for any settings between Mango and your MySQL server that timeout at 10 minutes. It is possible you have a Proxy or Firewall between the 2 that is severing the connections at 10 minutes...
If none of that helps then I suggest you post the mango.properties for your database. The begin like this:
# MySQL database settings. Your MySQL instance must already be running and configured before this can be used.
Hi Everyone. As promised we have added Series 4 pricing to the radixiot.com website. You can find it under Products / Pricing. At this point, it is a direct PDF, but as we have eluded to we have a 100% new website coming out hopefully in the next month that merges all of the other websites into one resource, and this will include an interactive pricing page.
This device is a black box, and cannot connect to our IP:port, we have to open a socket to it and just listen to capture packets that it sends out. Based on your note, it sounds like using a Virtual Serial Client with a Serial data source won't work.
If that's the case, is the only real solution to create some middleware/applet that connects to the host and reads the data, then pass it along to Mango in a way it can read?
We thought that if the device passes data every 6 seconds, and we use a TCP/IP Data Source to poll it every 3 seconds, we'd be guaranteed to get all of the packets, but that actually made the results worse, and we got fewer packets than when we had it polling every 6.3 seconds. (Don't know why adding the 0.3 seconds makes a difference, but it definitely does.)