I put the newly created mango.properties file in the mango root folder, just with the specific lines as above.
This worked
Posts made by hayden_AUS
-
RE: Editing mango.properties for Process Event
-
RE: Editing mango.properties for Process Event
Hi Terry,
Does the mango.properties file go in the overrides folder, or in the bin folder?
I can't even find it, so I will have to create it.H
-
Editing mango.properties for Process Event
Hi,
I need to run a Windows command script for a process event, specifically to disable/enable a COM port.
Mango returns:Process event handler is disabled, you must explicitly enabled it via mango.properties
I cannot find in the documentation what to put in the mango.properties file to enable this.
There is nothing obvious already in the file that is commented out?Thanks for any help.
-
RE: java.io.IOException: jssc.SerialPortException
@mwright Further to this, "restarting of Mango fixes the issue", without doing anything with Windows. Suggesting that if Windows did grab the COM port for some process, it re-released it
after.I'm not asking for anything, but future updates might include attempts to re-open the COM ports once this error is encountered, as this error just kills the data source.
-
RE: java.io.IOException: jssc.SerialPortException
@mwright Thanks for your response.
I will try updating the drivers, and/or the USB to 485 adapter, and ensure Windows UAC, or update isn't causing issues.
The weird thing is that it runs for weeks, then gets this error, and stops polling. It's almost
like Windows just grabs the port back for some test, like update or something. -
java.io.IOException: jssc.SerialPortException
Hi,
I'm hoping someone still monitors this forum!
I am running the latest version.
Windows 11, with a decent USB to 485 converter polling 5 sensors on COM3.Getting error, and stopping polling:
java.io.IOException: jssc.SerialPortException: Port name - COM3; Method name - setEventsMask(); Exception type - Can't set mask.
Can anyone help? I can find anything on this.
Hayden
-
RE: Modbus RS485: Acknowledge Event
So it's a standard Modbus response:
05 ACKNOWLEDGE
The slave has accepted the request
and is processing it, but a long duration
of time will be required to do so. This
response is returned to prevent a
timeout error from occurring in the
master. The master can next issue a
Poll Program Complete message to
determine if processing is completed -
Modbus RS485: Acknowledge Event
Hi,
I have a Modbus RTU Data source, and are getting the following error from most of the 5 Slaves on the BUS, but only from register 0:Urgent 'Modbus RS485': Cool Room Temperature — Modbus RS485: Acknowledge
The slaves only have two registers being polled, 0 and 1.
Update period: 30 seconds
Timeout: 1000ms
Contiguous batches onlyThe event lasts only 0 millseconds
Has anyone seen this before?
Hayden
-
RE: mango.properties file syntax
@joeamiraglia Thanks Joe. I am used to V3, which pulled its default values from the env.properties file. V5 must have it's default values embedded somewhere else then.
-
mango.properties file syntax
Hi,
This has to be a silly question, but every line in my V5 mango.properties file appears to be commented out:# The port at which Mango Automation will listen for browser connections #web.port=8080 # The host interface to which Mango Automation will bind and listen for new connections # 0.0.0.0 is the special interface that will force a bind to all available interfaces #web.host=0.0.0.0
Whereas the "Clean" mango.properties file in the Mango Docs doesn't even have hashtags for comments:
The port at which Mango Automation will listen for browser connections web.port=8080 The host interface to which Mango Automation will bind and listen for new connections 0.0.0.0 is the special interface that will force a bind to all available interfaces web.host=0.0.0.0
Can I assume that it is ignoring the hashtags?
-
RE: Can't create event detector for High Limit
If you save the event detector before setting the reset limit, it lets you then set the reset limit.
-
Can't create event detector for High Limit
Hi,
5.1.2
When creating a high limit event detector, when setting the Reset duration, the widget goes back to event detector. Then when I try again, is gets all messed up, half showing, unusable.
Chrome and Firefox.
Hayden -
RE: Disabling Event Handlers - User
@terrypacker Thanks, I will set them up using meta points as you suggest.
-
RE: Disabling Event Handlers - User
@MattFox Hi Matt, the application is a cold room used as a grow room.
The room has set-points for alarms and also automation to turn off grow lights, when the temp gets to high.
But we need to disable all the alarms and automation when they have the doors open for loading/unloading, using an easy method.I might try to setup the Event Handlers using external context points (maybe a virtual binary point,or physical switch) and scripts, if disabling the event handlers by a user is not possible.
...or just create another user with superadmin privileges.
Thanks anyway for looking at it...
-
Disabling Event Handlers - User
Hi,
I can't see how to give users permissions to Enable/disable event handlers, that have been created by admin.
I gave access to the Event Handlers menu item, which is there, but I can't see any options in the actual individual event handlers, which are not visible.Does anyone know?
(V3) -
RE: Denying access to Mango resource / to IP 52.26.90.15
Thanks for your reply guys, much appreciated!
(Must not have email post notifications setup, sorry for the delay in thanking you guys...)
-
Denying access to Mango resource / to IP 52.26.90.15
Hi,
Wow, not much happening on this Forum?I am getting what appears to be intrusion attempts. They have come in from various IP addresses.
Anyone else getting this?
My instance is running on port 8008WARN 2023-02-19T08:44:51,449 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource / to IP 52.213.21.176 WARN 2023-02-19T08:44:52,317 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /debug/default/view to IP 52.213.21.176 WARN 2023-02-19T08:44:53,160 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /tool/view/phpinfo.view.php to IP 52.213.21.176 WARN 2023-02-19T08:44:54,021 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /wp-config.php-backup to IP 52.213.21.176 WARN 2023-02-19T08:44:54,933 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /%C0 to IP 52.213.21.176 WARN 2023-02-19T08:44:55,810 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /debug/default/view.html to IP 52.213.21.176 WARN 2023-02-19T08:44:56,531 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /debug/default/view to IP 52.213.21.176 WARN 2023-02-19T08:44:57,344 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /frontend/web/debug/default/view to IP 52.213.21.176 WARN 2023-02-19T08:44:58,263 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /web/debug/default/view to IP 52.213.21.176 WARN 2023-02-19T08:44:59,179 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /sapi/debug/default/view to IP 52.213.21.176 WARN 2023-02-19T08:44:59,976 (com.serotonin.m2m2.web.mvc.spring.security.MangoAccessDeniedHandler.handle:53) - Denying access to Mango resource /debug/default/view to IP 52.213.21.176
-
RE: HTTP Sender - Publisher
Hi Craig,
I am not familiar with httpBuilder.
How does the "message" get updated in the script?From what I can see, httpBuilder method uses at least the point, an event detector, and a global script.
The easier way would have been the original way I tried to get it to work with the Meta
point getting published when the script changes. (which worked, apart from the delay I needed of 5 minutes)
That way for the limit value, I could have used another Virtual numeric point, so the limit can be
easily adjusted on the fly, from a dashboard.