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.

hello Patriator,

another user from france is willing to help with the translation.
post in french:

http://www.scadabr.org.br/?q=node/127

(we use the same translation files from mango)

would you be interested in joining efforts? this could be put into mango´s main release.

best regards

Not currently in M2M, but this would be possible in M2M2.

Can you use some kind of O/S-level semaphore? lockfile() maybe?

Solution:

In Debian/Ubuntu the serial ports are in group 'dialout.' However, user tomcat6 is not a member of group dialout, and consequently could not see the ports.

$ ls -l /dev/ttyS*
crw-rw---- 1 root dialout 4, 64 2011-03-23 20:42 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 2011-03-03 10:28 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 2011-03-03 10:28 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 2011-03-03 10:28 /dev/ttyS3

To fix the problem, user tomcat6 must be added to group dialout:
root@ubuntuserver# usermod -G dialout tomcat6

Now Tomcat6 can see the serial ports, but Mango will not report them until it is restarted.
To restart Mango:
root@ubuntuserver# /etc/init.d/tomcat6 restart

Stopping Tomcat servlet engine tomcat6 [ OK ] Starting Tomcat servlet engine tomcat6

Now Mango shows the serial ports in the pulldown menu

When I searched for this in the forum, I had searched for 'NMEA.' Once I noticed the same 'missing ports' problem was also on the 'Modbus serial' data source page, I narrowed it to a serial port problem, and searched the forum for 'rxtx' and found out that [url=http://mango.serotoninsoftware.com/forum/posts/list/0/189.page#1362]'a reboot was mandatory,' so I restarted Tomcat.

[solved]

It would be useful to have a Mango wiki so that these issues can be organized and updated in a more structured manner than what a forum can support.

Hello,

Mango runnee fine V10.0 for a few months.
Last night a powerfailure, restarting the mango server i got this strange error

"OneWireContainer10-Error reading CRC8 from device"
None of th eone wire devices is read out by mango.
this message occurs when going to datapoints one wire and do a scan

I upgraded to V 12.2, still the same problem
i run mango on a ubuntu laptop V10.04LTS

any help will be appriciated

That kind of message usually means you've compiled the classes with a Java version higher than what you're running them in. I.e. compiled in 1.7, running in 1.5.

A process timeout in seconds has been added to both the active and inactive fields. This has however been implemented in M2M2 only.

Thanks.

Ah. There isn't a way to get that via an AJAX update, but there should be a way to it if you draw it in JSP. I've never had to do it, so i'm not sure.

Ok, I am attaching it as one ZIP.

Attachment: download link

Works fine for me.

Sadness. It looks like the uploads were lost during the upgrade/move.

Hi Mathew,

I've developed a sms alarm service with some scripting (OS side) and the recipient number is dervied from a text file within the host, and i was hoping to to make this adjustable from within the scada.

We recently upgraded the forum software and a reindex was necessary, but apparently not documented as so. In any case it is done now.

Re test data, check out the virtual data source. More arbitrary things can be done with the meta data source too.

here you have same modbus rs485 units
if you have problems with conection you cen contact us at http://www.a2s.pl/en/kontakt.php and we'll help you

Yeah, the timer has a limit of 500 threads. It's an artificial limit, but is usually suitable. Your system is adding more than 10 new high priority tasks every 10 seconds, which is definitely bad (but only if it can't clear them out). I'll go ahead an assume that these are database write behind tasks, which would mean that Derby is insufficient for the scale of your system.

If it works from some browsers but not others, it's likely a browser thing, not Apache or Mango.

Luke, what happens if you increase the timeout?

You might tail the <tomcat>/logs/catalina.out file for messages.

Talking about "Http Sender", I have developed an OPC Server able to accept incomming HTTP messages from various Mango stations and make those values available to other SCADA systems.
If you want more info please send me a PM.