Messages posted by: craig

Hi Matt,
There is only 1 zip file I can find to download on the sourceforge modbus4j website and it only has .class files in it and not .java files.

I suppose knowing that BatchRead makes separate requests if there are non contiguous addresses I could insert the missing addresses in at the top of ModbusDataSource.doPoll() to get BatchRead to read bigger batches.

Cheers
Craig

Hi,
I've been reading some devices with mango via modbus IP over satellite. Apart from the high latency we also have a bandwidth limit and ridiculous charges for data used beyond our limit.

I've noticed that if the addresses being read are contiguous they get read all at once with the 'read multiple registers' modbus command whereas if they are not strictly contiguous a seperate read request is issued for each register or group of contiguous registers.

Each read register request is about 50 bytes regardless of how many registers are read. Likewise there is an overhead of about 50 bytes per reply, regardless of how many registers are in the reply.

It takes mango 3 seconds per request-response cycle with these satellites. Cutting down the number of requests is going to allow us to increase the refresh rate and save on bandwidth charges on the satellite.

Temporarily I could add points to make the addresses contiguous but then I have all the unused points cluttering & confusing the instance.

Is the source for the com.serotonin.modbus4j package available so I could take a crack at getting the number of modbus requests we're making down?

Cheers
Craig

I think this may stem from the 'headless' mode in java.

Before headless mode some libraries (swing, awt?) would balk if there was no display.

Maybe java is detecting your display and letting libs know that they can use it?

cyberoblivion are your alarm conditions detected and raised in your PLC or in mango? I thought you wanted the mango event detectors to be able t o use high/low warning values that came from PLC points as per http://mango.serotoninsoftware.com/forum/posts/list/139.page. That led me to believe you were doing alarm condition detection in the PLC and using the PLC to raise an alarm.

I'm set up so that the alarms are generated in the PLC and mango sends out emails etc when the alarm bit goes high because that is how our legacy system worked.

how are you displaying an alarm on a graphical view?

Good idea!

What's a push button?

a rectangle with some word(s) on it that performs an action when clicked.

I think he wants to set a binary value by clicking a button in a graphical view.

cyberoblivion wrote:
Can you make push buttons on the view screens to set binary point values?

No, but this is something I'd like to see as well.

I put the spaces there too! The appropriate value for minutes is in the ${dataSource.updatePeriods} variable. I

I added the periods around the 2. When I paste this HTML I am removing many empty lines. I don't know if that is relevant.

The sst=true is present in the editModus.jsp file. The select tag in the browser is:

editModbus.jsp in CVS is different from the commercial version so I don't think there is much debugging I can do short of sending you a copy of the database without any pointdata.

Thanks for the help,
craig

I deleted the webapps/ROOT directory and extracted the 1.4.1 archive and I'm still seeing the same behaviour.

Could it be caused by an incomplete upgrade?

I've upgraded a mango installation from 1.2.3 to 1.4.0 and then to 1.4.1.

When I load up the data source edit page for a modbus_ip datasource it shows the update period as 15 seconds instead of 15 minutes. If I save it as 15 minutes, and then reload the page it still shows 15 seconds. However the update period must be saved correctly as the source is only updated every 15 minutes. When I view source on the select box there is no SELECTED attribute on any of the option tags.

This problem is not confined to the datasource edit page. I've observed the same behaviour while switching points over to interval logging.

I do not have this problem on a fresh 1.4.1 installation.

I created a new datasource on the upgraded 1.4.1 installation and was unable to set the update period properly on the new ds, so the problem isn't confined to pre-existing datasources either.

Can I delete and re-install the webapps/ROOT directory or is there some way of investigating how the upgrade is botched? I have remote access to the server and eclipse is installed so remote debugging is an option.

Thanks
Craig

I had to enable logging on the data point edit page and all is working properly now. Thanks

Hi

mango on windows+tomcat creates the filedata directory under WEB-INF but the directory stays empty. Mango on linux doesn't seem to create the filedata directory as I can't find it anywhere on the filesystem. Couldn't find anything in the logs about an exception being thrown when creating the directory failed. I'm hoping filedata is where images from HttpImage datasource are meant to be saved. Is this correct?

Flipbook, thumbnails in the watchlist and the choice of scaling images at retrieval and on the graphical view are all real polished features! Once I sort out how and where the images are stored I'll be set.

If I restart tomcat the flipbook starts from empty. Also in the history box all the values are "img-1.jpg".

Thanks,
Craig