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.

Thanks phildunlap. That solved my problem.

Hi Chris, I'm not sure I understand what you're saying about your setup. This is one Modbus data source talking to four devices, or four Modbus data sources? Serial or IP? Regardless, the answer probably is in your timeout and retries settings. The actual maximum time waited is the number of requests, multiplied by the number of retries, multiplied by the timeout. A "poll aborted because Task Currently Running" means exactly that, the previous poll is still running. To see your poll times, you can check the "Runtime status" above the data source in question. [image: E7bZx2d.png] I believe "Latest aborted poll times" should only show up if you've already made the move to 2.8, but the "Latest poll times" should be there.

@craig, One would think one should be able to daisy chain some devices, no? Certainly in our deployments we have daisy chained RS485 modbus devices and not encountered this. I don't dispute that your description sure does sound like it would eliminate any possibility of getting the issue, but it doesn't seem like it should be necessary. I do agree that it'll be the fastest, easiest path to resolution, though, since no more investigation would be called for. @Devin-Homan41 I edited out Ed's email address. Partially because I don't know what Ed would like an Email about, and partially because I don't know Ed would like emails from anyone who wanders by. I wonder if you're seeing two registers on the same slave ID cross, two slaves cross in the same register, or two different registers from two different slaves cross? Judging from your configuration alone, nothing seems too unusual. My first question is if your serial data source reset logic would fire three times for this data source should the data source stop polling (I think it would, to hopefully no effect, but quite interesting). I may also try things like lowering retries to 1, lowering max read registers to 1 (for 2 byte data types, 2 for 4, 4 for 8) and unchecking contiguous batches Enabling data source alarms at a higher level than None, such that you notice if there's an ongoing error in polling. (For the version of Mango you're on, likely the only place you could see None level events is by directly querying the database's events table) I may try to reference times your reset script had fired against moments of crossed data, also, because that script seems unusual to me.

Thank both of you. It is true, the solution is to change the attribute "point": <ma-point-values point="point1" by the attribute "point-xid" with the XID of the data point you want to draw: <ma-point-values point-xid="myXID" Could be a good idea to add an example to the "Mango Dashboard Examples" with this option to draw a chart. Thanks.

OK, cool, I will try that as well...Thanks!

@przemom We have released Mango 2.8.0 for testing which supports much better and easier localization, Mango will automatically detect your locale from the OS and use this for translations and date formatting (in the dashboards). All you need to do is place your translations file in overrides/properties as described above. If for some reason Mango is not using your OS locale or you want to override it, you can start Mango with java command line options such as -Duser.country=PL -Duser.language=pl See here for the Mango 2.8 download link - http://infiniteautomation.com/forum/topic/2549/mango-2-8-0-ready-for-beta-testing If you want to wait there will be a 2.8 release in the store soon for automatic upgrades.

Glad to hear it!

I recently raised a support ticket for this - please disregard the Support Ticket - we applied this fix to the enterprise mango and the problem seems to have gone . We also applied this to the maintenance events table. I think during our upgrade from H2 -> MySQL this problem occurred. Thankyou for your help and suggestions for getting this problem fixed. [image: NgDyWE4.png]

Just to update this... I had a maintenance window out of hours and updates packages with apt, then rebooted, and now its working.. I don't think updating the packages is what did it, more likely it was the reboot that fixed it. Weird. Hope this helps someone else if they see similar behaviour. Cheers! -Shaun

I think there could be a issue between our email systems. I sent you another email on November 1st with no response from you. Please try responding to the original ticket you set to the IAS support email. If that doesn't work we can use Skype of google hangout.

Hi Phil, Thanks for the info... I'll check it out. Cheers!

it is MA 2.7 on windows XP.

Thank you Joel I got it to work. The only thing I had to change was the Bit rate back to 9600, which is what our modbus network runs at.

Thanks, Phil, that's very useful. It was also insightful of you to note that narrowing down by device name is the most logical way to select the source points to be moved, as renaming the Device Name was probably the first step done by an admin looking to group points within a source that already has many points.

Yes. You can set a home page for each user on the users page, which is where they will be directed at login. You can use permissions groups to restrict access to pages and points, if necessary. These are also set on the Users page, but access controls are dispersed around, with core pages being governed by permissions on the System Settings page, data points have permissions which can be set individually in their editor or in bulk in the "Bulk Permissions" section of the Users page, and dashboard restrictions are in the permissions field of the page editor.

Hi Phil, I have these two scripts in my global scripts so I can call them out in the datapoints. Note, after every if clause there is a return. I am calling them out in the datapoints like this Damperstate(p538,p537,p539,p540,p592,p594); So the function should work then. I am sure the scripts have to work because I am using the exact same function on my other MangoES instance and everything works fine. I will look into the github issue as the problem maybe because of the disable/re-enabling. But I cannot see the bugfix there? As I can only see the description and that the problem has been closed and fixed. Thomas Edit - The first issue about updating has been fixed with adding DNS servers. Thanks. The problems with meta are still open. Note: By adding return in front of the function as you suggested seems to give me a different result. Will keep you updated if the result is correct! It seems all the problems have been resolved hopefully. Will test the system for a day and post the result at the end of the day. It seems that you can say that I had "return blindness" in coding. Sorry for the trouble. Many thanks to you Phil.

I installed your modbus module, and it seems to be working as expected. Thank you very much for addressing this so quickly. I really hope that the next release discards extreme values when setting points.

All, Thanks for the help. After starting ma-bat in terminal we saw that the upgrade was not complete. We backed out and did the upgrade manually and all is well now. Thanks again for the help. Larry

Hi, Thanks for answer. Problem solved...proxy server blocked OPTIONS reguests.

@phildunlap Great thank you! That makes sense, I do remember messing with those settings trying to get the custom dashboard to reload properly which I had help fixing in another topic.