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.

You are that man! It asked for my password after I enetered "sudo ./ma.sh start"... Another fine JOB JOEL...

thanks for that I'll give it a go.

The point links solution still sounds good to me. You'll need an SSH data point for each RFID point I think. Then you can just hardcode the door number either into the pointlink or the ssh point. I would opt for the point like, and set the SSH point's value to something like "RFID# Door#" and stick with the ssh points' set commands being "key=$(/path/to/validation/script.sh VALUE)" as the string VALUE will be replace by our two arguments for the script. Each RFID point will have a point link to an SSH point (and all SSH points can be the same, but for the sake of event handlers (if Mango needs to track state beyond just issuing a single open to the doors). Door 1's pointlink may look like, return source.value + " D001" You may need to check for an empty source.value and such. You can use all the same control logic from my earlier posts, involving another chain of point links from the SSH points to their relays.

Well, Joe, I'm making a dashboard in DGLux, and one of the things I want to display there is the number of nonsilenced nonacknowledged alarms from mango, so the user could see that on the dashboard, and go to mango to acknowledge or silence them. Thx for the video and link.

@terrypacker Thanks for the update. Please keep in mind that this problem is not unique to my installation.

@terrypacker said in DNP3 Analog Data Point: Udara, I don't have a DNP3 Device with an Analog Output to test with, but I did find a bug in the DNP34J source code. I've made some changes that I hope will work. Here is a new module for you to test with. Can you confirm that it now works? You will probably have to rename the downloaded file as m2m2-dnp3-1.6.2.zip Thanks, Terry 0_1462484371554_m2m2-dnp3-1.6.2.zip Hi Terry, I tested the new DNP3 module on my Mango 2.7 installation on windows and it now works as intended. It lets me set multiple analog output points. I will test it on my Mango ES installation too. Thank you very much.

That's good to hear! I don't want to have to worry about this, or eventually forget and get caught off guard. In the meantime I changed Log level from debug to Error in the persistent publisher for now.

RIght now we have the login turned off. In the future the login will be for companies with support plans to issue private support tickets. For now you can just search and read the documentation and there is no need for an account.

That made it work. I double checked the values, by manually averaging some points in Excel and they are very close. I also attached a pretty picture as more proof =D .Thank you Phil. [image: Q14XtRA.png]

Thank you very much Phil. I am definitely going to set that a bit lower... :P

Glad you got it figured out!

It is released.

This should help: http://help.infiniteautomation.com/m/55730/l/519384-about-the-h2-database

Glad you got it working. I have done some dashboard work in the new angular framework and it is 10x easier and more powerful then before. The new angular directives really allow you to plug and play with mango web components and build out pretty complex dashboard with pretty much no javascript, just binding data between the mango components. Have fun

Hi Stefan, This information is not kept in the database, as the reliability of a point only exists in the runtime. This attribute's value is available in DGLux. When you bind a point, one of the options is 'status' which typically says 'ok'. If you wanted to have that supercede the coloring from the value, you will have to create that behavior either with logik attributes or by passing everything through a script.

Hi Brian, I think i may have not given you a complete answer last time. It slipped my mind that you need to set the sql point with a string like: ('2016-04-01 14:20:00.0') for yyyy-MM-dd HH:mm:ss.0 So, the values to replace the SQL statement need to be in parenthesis and with single quotes around certain types (including 'date and time' parameters, I believe).

Ah, yes. I understand.

Hey Phil, I did both of your suggestions and everything seems to be working well without any problems so far.