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.

It can't find the method because the method takes a ResourceBundle parameter, so it looks for a method that takes no parameters, which doesn't exist.

I've added the appropriate resource bundle to the script context under the var "bundle". So, your script would be "events.get(0).message.getLocalizedMessage(bundle)". This will be available in the next release.

Do note though that the rendered events should appear in a warning rollover to the left of the component.

There can only be a single BACnet local device running on a particular port at a time. You probably have your data source running on 0xBAC0 when you try to run your discovery test. Local devices are not shared for technical reasons. Try stopping your data source and re-running your discovery test.

Hi Steve,

You should check out the Rhino documentation. The Java Scripting implementation of it into the JRE might get in the way of some stuff, but you should be able to access a lot of stuff directly within your javascript code. (I have not tested this to any great extent, but in theory it is possible.)

Also, Rhino does in fact compile scripts to Java for fast execution when the optimization level is properly set. This works in Mango Automation which uses Rhino directly, but M2M uses the Java Scripting impl via which there doesn't appear to be a public way to set the optimization level. Maybe a future version of M2M will use Rhino directly.

Thank’s for your advice, Joel. That way it is VERY easy. I think that so complicated. :oops:
Simply is beautifully….

BR
Antsu

Thanks, I'm impressed with how fast you guys put out new releases.

Thanks,
Joel.

No, there are no other settings. The "Settable override" box should be checked, as well as "Display controls". Otherwise, the point only needs to be settable itself. If you are still having problems, can you provide an export of the view?

Thanks, I'm running linux and always forget to check the permissions. I just needed to give the right read/write properties to the file and it works perfect.

Thanks,
Joel.

Great. I'm looking forward to it.

It sends a snapshot of all the points every 15 minutes.

You could create a scheduled event that fires when you want to send the tap, and then handle the event with a process handler which would run some script. Stuff like this will be easier in the new version.

It's a matter of clearing your cache. A quick ctrl+f5 usually does the trick.

It may be an issue for server-script component

I used the property "disabled" in a button and saved the view.
When I try to edit the view, this component is also disabled.
So I need to enable the button using the datapoint logic to enable the component editing on the view.

This appears to be a problem with *nix, although i don't know if it is widespread. It seems the request to the comm layer for the list of ports does not include those that are currently in use. There doesn't appear to be a good solution beyond oja's, but we'll keep looking.

thanks...

i find it helps to reset the browser cache (well at least on chrome).

keep up the great work!

Neil

Thanks a lot!
your help was very useful

I knew I was missing something obvious.

Thanks,
Joel.

I found that:

this step is not needed for Ubuntu Desktop 10.04 it is required for a simple installation of Ubuntu server 10.04

Another idea is to just use MySQL as Mango's database (either brand new or converting from an existing Derby instance). Then, other applications can directly access the pointValues/pointValueAnnotations tables.

The most efficient way would be for Mango to poll over Modbus I/P. But if the device needs to initiate the connections then, yes, posting an HTTP message will work just fine. Check the HTTP Receiver documentation for details.

System startup event happen when the web context is loaded, so the cause would be one of the following:

Tomcat is restarting the Mango context somehow. This should only happen when manually initiated. The O/S is restarting Mango. Can't comment on why this would be happening. A badly behaved script maybe. The UPS is shutting down the server.

Or anything else along these lines.