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.

Thanks I worked it out POINT LINKS..thank you

Thank you so much it works like a treat. :-)

You could try the Discard Extreme values option on the logging setting and return a high value when you don't want to log any data. So rather than throw no value through 999999 and have the data point set to discard any value over 1000.

There is the help (?) within Mango for the Point Links and there are a couple examples around the forum: http://infiniteautomation.com/forum/search/"point link"?in=titlesposts&sortBy=timestamp&sortDirection=desc&showAs=posts

Ah you're right I didn't catch that. The day was off +1. Thanks!

Ah, gotcha. You'll probably want to switch the sign in my return statement, then. The reset is that now.getMinutes() and now.getHours() will return 0 at midnight, and any past(PERIOD, 0) call will have an empty data set (I should confirm this, it could have a single data point if there's a value at that millisecond), and the sum of an empty data set is 0, so it'll be 0 - 0 = 0

Thanks Phil, I will be doing the totalization within the controller as your correct in stating the accuracy will be better and the load on the mangoES will stay normal. Thanks

By "the string" do you mean the Alias? No, it is not possible. Using state detectors, it doesn't make sense to me to have to do that. Point event detectors are on a per-point basis already, so the data point that it applies to is known. Similarly, for a State detector (but not a regex state detector) the state is unchanging. So, I don't know why you would want to do that. It does make some sense for a Regex state detector, though, but isn't possible at the moment. Mango has existed for quite a while, so there have been a few contributors. Of absolute noteworthiness are Matthew Lohbiler, who wrote Mango M2M, and Terry Packer, who is our senior developer. But, if you peruse our opensource Github repositories you may find others, such as myself, who have made contributions. A great many of the modules are written by contributors. Most classes do have an author documented at the top, but this is not always updated to reflect everyone who touched a class.

@phildunlap Thank You very much. That helped a lot.

sent

I am looking into this at this very moment. One thing Terry mentioned to me in relation to this was that the JavaScript engine was changed out from Rhino to Nashorn by the Java people as they moved to 8, but I couldn't find anybody talking about casting working differently. What's your Java? Can you run it up against the other? There was a time we were looking into moving to building against Java 8, but I do not believe that made it into the store ever. Perhaps someone else knows more. We definitely still run it in Java 8 often. The other problem I'm having here is I cannot replicate. I have run up Mango 2.5.2 against Javas 7_79 and 8_65 and Mango 2.7.2 against Java 7 and 8 as compiled against 7 and 8 and when my script does.... print( typeof( p.lastValue(1).value )); print( typeof( p.value )); print( p.value - p.lastValue(1).value); print( p.lastValue(0).value - p.lastValue(1).value) I get results like... object number -1.7822553715030978 -1.7822553715030978 So I guess I've surprised myself a little here. The only differences I've observed between 7 and 8 is that println became print and 7's print disappeared. That you say 2.7.3 concerns me a little, as I am unaware of such a version as of yet.

Units should cycle weekly (i.e. unit 1 transforms in to unit 2, unit 2 in to unit 3, unit 3 in to unit 1) If the reason you want to cycle the units is to keep the operating hours similar between units, if you're tracking their total runtime hours, then rather than starting the "next" unit, you could start the unit with the lowest runtime. If you want the unit to be offline for a week for maintenance, then of course only check the runtime weekly.

Phil That last script worked like a charm. thank you for all your help my friend.

@sprokkie Are you referring to the Data File Data Source? If you only want the last row, you'll either want to know how many rows there are and generate the list of import points on then, or create a new 'parsedPoints' list at each row. The abstract "importRow" method will give you one line of Strings split by commas. Loop over the values in the array, and for each one this.parsedPoints.add(new AlphanumericImportPoint( "Point number: " + n, data[n] , now.getTime() )); You can find a good example in the module's folder inside your Mango. Mango/web/modules/dataFile/web/CompilingGrounds/CSV

You should have 4 tariffs called - Peak, Off-Peak, Normal, Valley (1=Peak 2=Off-Peak 3=Normal 4=Valley) - Then you should have 14x 24hour Schedules 1-14. Each schedule you can link to a season for example you have 2 seasons one from September - May the other from June - August. Let assume weekend are not charged at at different rate for now. In the software you would link the season to a schedule something like this (DD-MM scheduleNumber) 01-06 1 (1 June uses Schedule number 1), 01-09 2 (1 September uses Schedule number 2) Let assume the Schedule for season 1 look like this [image: 7we9nY3.jpg] Schedule number 1 (linked to Season 1 above): It should have 14 time slots (HH:MM ID=Tariff to uses 1-4) slot1: 00:00 2 slot2: 05:00 1 slot3: 07:00 4 slot4: 12:00 1 slot5: 17:00 4 slot:6 20:00 1 slot7: 21:00 2 (time slot 8-14 not used) Let assume the Schedule for season 2 look like this [image: hnb8Crl.jpg] Schedule number 2 (linked to Season 2 above): It should have 14 time slots (HH:MM ID=Tariff to uses 1-4) slot1: 00:00 2 slot2: 06:00 1 slot3: 08:00 4 slot4: 13:00 1 slot5: 18:00 4 slot6: 21:00 1 slot7: 21:00 2 (time slot 8-14 not used) [image: wARdRve.jpg] It should be possible to active the weekend scheduler for Sunday, Saturday or Both separately. e.g Saturday and Sunday is active you should be able to link Saturday to one of the schedules 1-14 and link Sunday to one of the schedules 1-14 similar to the above. If holiday scheduling is enabled then this should also be linked to a schedule 1-14 similar to the above. When you run this on a kWh point it should give you the totals for the current month or any past month for kWh consumed in Peak, Off-Peak, Normal and Valley time periods. Does this make sense?

If you still can't make sense of it just send me the strings you used for both formats, I can check them against my test Mango.

Here are some screen shots that might help. First is a watch list containing the point containing the script (Time_Stamp) and the alarm that it is connected to (mal_cp_ol). They have the same time stamp: [image: 7cAVMWy.png] Here is the script. Perhaps I am not using it correctly: [image: ER46GuD.png]

Hello Bryan, I can tell from the screenshot you are running a Beta 2.6.0. I just tried to duplicate your issue on Mango core 2.6.0 build 353 and was not able to reproduce your failure. If you are running a build older than 353 can you update to see if this fixes your issue. Thank you, -WoodyB