In my option it would be best practice to set the Slave ID of a replacement Modbus device the same as the one it's replacing.

Also, it's really easy to change the slave ID of a set of points be either exporting all the points as JSON or csv. Making the change with a find and replace or in Excel and then importing them on the Configuration Import / Export page.

it is MA 2.7 on windows XP.

Thomas is exactly right with the exception that we don't support Derby anymore as the main Mango database. The SQL data source is very flexible and can be used to pull or insert data from a MS SQL database but Mango does not currently support MS SQL as the main database. Mango could certainly be made to with MS SQL as the main database but it means that every new release then needs to be tested on it as well. When you are using the NoSQL module with Mango there is a lot less load on the database so most people are very happy with using MySQL combined with the MangoNoSQL (Time Series Database).

Hi Mebius,

The error is as described, there is a mismatch in point type. Either this is in your code in the data source definition class you didn't define a unique data source type, or (more likely) you used another tab to browse either a data source or data point, which due to some state saved on the server in the user's session, then tried to perform an action which had relied on the state being another way. Eventually, it is our intention to remove a lot of this state tracking, but lots of pages use DWR so it is not a small effort.

To know if that is it, you would just have to edit the point again (click the pencil) and try to make your changes and save it again.

@phildunlap

Hi phildunlap,

I use the code from zip file instead of cloning code from git, module build works fine now with the same steps.

Thank you very much for your kind help.

@phildunlap

I used wrong API as case-2. It works fine now. Thank you very much!

Hi Mebius,

I've given some information on the message formatting in this thread: http://infiniteautomation.com/forum/topic/2187/how-to-use-publishers-http-sender/3

This is what is sent from the publisher which complements the receiver.

Hi mebius,

The trick is to capture an empty group, refer to that group as the point identifier index, then have a point with an empty point identifier.

I gave an example configuration for this purpose in the first half of my first response in this thread: http://infiniteautomation.com/forum/topic/2274/serial-data-source-trouble-to-show-value-from-com-port/2

Hi Mebius,

I do not believe so. I believe only the GET type is sent during polling

Hi Mebius,

I looked at your logs, and a few things were interesting. Some of your polls, especially for your SQL data source, are extremely long. Even some of the PLC polls were up to twenty minutes it looked like, which is way too long. Do you have long timeouts with many retries? The SQL source has a poll that looks like it lasts 4 hours, which is also much too long. What kind of query is it running?

Do you have data in Mango during the times in which DGLux seems unresponsive?

Hi, thanks for the information.

We have identified some improvements in the serial data source. Take a look at this thread: http://forum.infiniteautomation.com/forum/posts/list/15/1813.page there is an updated serial module you can download and test at the bottom of the thread. If you could also send your scripts we can take a look at those but I think upgrading the serial data source would be a good first step.

Thanks,
Joel.

Mebius,

Do you have a single data source that is getting points from the BACnet device, or do you have multiple? If the latter, you might have multiple simultaneous requests going to the device, which it may not be able to handle, causing timeouts and the appearance of a slowdown.

I know at least that even the BACnet MS/TP is capable of polling for thousands of points without problems, subject to the speed of the connection. (I know you are using I/P, which should be much faster than MS/TP.)

H2 is now the default database rather than Derby. If you where reading alarms before I'm guessing you had Mango configured for a MySQL database. You can still switch to MySQL in the /classes/env.properties file.

it seems like the your modbus slave's problem,if you use the modscan32 to test the datasource 'stability use the same configuration on mango.

What's the meaning of 'send regular snapshot' in a HTTP publisher?

If it's disable, what's the impact on publishing the data?

Thanks.

Attachment: download link

This has been resolved in the latest release along with several other improvements to the alarm page.

Got it. I will feedback to you after I testing the new core. thanks.

I uploaded a new version of the module, you can get it here: http://store.infiniteautomation.com/module/opcda

Please let me know how this works for you.

Joel.

An unexpected failure leads to that sensors connecting to COM8 can't be reached.

Turning off power and turn on then, those sensors can be reached again.

thanks Joel.

I found a strange thing.

this error will not occur under a user account but always occur under account of admin.

that occurred in a same browser instance.