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.

Hi uelojazz, I can't say for sure what the cause is, but I was able to get it resolved by adding a styling to the gridlines to remove their fill opacity, like, <style> .amcharts-axis-grid { fill-opacity:0 } </style>

Hi Ralf, Received persistent points, if created automatically, are set to log all data. This is the most typical, and probably correct, choice. However, you could do a different logging type, and I believe it would work, particularly if you did not save real time data (I think with many other logging types, you will not see the history sync work if there is newer data). So, simple answer: all data.

We've talked about and looked into having an easy to use integration with Let's Encrypt, but we haven't done so quite yet. If you do use it though, and you are restarting Mango every time you get a new certificate loaded into a JKS (which is what, every three months?) so that it presents the correct certificate, know that you can tell Mango to reload it's SSL settings, but you have to be using a JKS file in the same file location with the same credentials (but I don't think it matters if you replace the file or update the existing certificates in the existing JKS). After that's in place, you can run this in a script (and just validating the script is sufficient to make it happen) com.serotonin.provider.Providers.get(com.serotonin.m2m2.IMangoLifecycle.class).reloadSslContext(); You may need to close and open the browser to see the new certificate loaded, or clear your cached site data.

Certainly! Glad we got it figured out. I would wonder if a particular request took a lot longer than others (perhaps there's something like virtual registers the device is computing upon request?) if there was cause to go deeper.

It'll probably only work out of the box if the HTTPS connection has a valid certificate. A self-signed certificate would probably get bounced by the HTTP client's default configuration.

It is quite old topic but as every year I almost always forget the correct sequence on how to change my signed certificates in my used keystores I thought that maybe it would be nice to share a nice tutorial on how to do it with KeyStore browser. Maybe someone in here will be interested and thankful if it comes up in forums search. Download keystore browser here: http://keystore-explorer.org/downloads.html Code42 has nice tutorial for usage with self-signed : https://support.code42.com/Administrator/5/Configuring/Create_a_signed_keystore_with_the_KeyStore_Explorer#Build_the_keystore Existing certificates: https://support.code42.com/Administrator/5/Configuring/Create_a_signed_keystore_with_the_KeyStore_Explorer#Build_a_keystore_with_existing_key_materials Cheers! Thomas

@benaznbe said in Mango connect 4G device: @craigweb said in Mango connect 4G device: modbus master I want to know how to set up Mango as a bus master. @Jared-Wiltshire What are you suggesting? But my device is installed around the factory, which does not have the same network as the scada. I installed Mango on the cloud server. Mango has public IP. I think that 4g device connects to the mango.Make the mango as a modbus server and 4g device as a modbus slave. 4G device write data on mango because 4G device doesn't know ip address. Or is there a better way? Actually your way is not possible as per Modbus standards master asks slaves not the other way around. If you can customize (reprogram) your 4g device then the easiest would be to use a http receiver. If mango has public IP then the 4g device can send data to Mango without Mango even knowing the IP of your 4g devices. You can whitelist and blacklist IDs easily in the datasource configuration.

Nicely done. I would have suggested code but it's always hard to gauge someone's coding skill level. Best of luck with future projects.

To get the monitor point to show up correctly Mango must be able to connect to the Store and request if there are upgrades available. I will discuss a better way to handle this situation with our developers but setting the value to 0 on a failed request is not an option as it is misleading and Mango is not able to log a null value.

Thank @Jared-Wiltshire

Sorry Joel that was not the issue. it's set up to start on boot.. Somehow a file of different ownership than mango got inserted into our graphical views and when mango attempted to delete it on startup it was crashing out on a permission error and I thought it was because the filesystem was owned by root (not mango) since root owns the init.d startup file so it was starting for root on reboot but not mango from a terminal window.. Its fixed now. thanks for the quick response.

Tested with HTTP 3.4.1 and updated the log4j2.xml per your instruction. It is all good. Thanks.

@joelhaggar Thank you for your expertise on Mango! I will bring this info back to our folks. We might take up your offer if we still have questions. Thank you again! Jack

It may depend on your device. For the MangoES, which is a Linux ARM device, we're using the scripts in Idrive_ARM (which has the other directory inside it).

I don't think you can have two colors on the same series in a serial chart. So, I would think the easiest way would be storing the positive values in one point, and the negative values in the other. You would probably have to put zeros in the other point (whichever does receive the real value) so that there isn't linear interpolation by the chart that messes up the coloring. Or you could write a filter for turning all the negatives to 0, and another to turn all positives to 0 and negatives to positives, then use one one point's values filtered in two different ways

Yes thanks guys for the explanation and link.

Thanks guys

@jared-wiltshire Thank you, it is working now!

Thanks for that explanation as well I was getting duplicate entries for the snapshot.