wayne530
New Member
- Joined
- Mar 7, 2022
- Messages
- 117
Start = End = 00 is a special case to disable the timer. I have tested setting Start = End = another non-00 value and it does work as intended, exactly as you described.Did anbody test if setting Start & End time to identical values will allow to set a 1 hour period?
eg. will Start=16 and Stop =16 switch on at 16:00 and off at 16:59?
Or is this forbidden like Start = End = 00 as mentioned in the initial post?
My intuition about the behavior is derived from testing only so could very well be incorrect. I have no documentation or word from the vendor about the exact behavior, but my understanding is that there is a 24-slot table, corresponding to the hours 0-23. When you set the default charger source or output source priority, it simply writes that default into all 24 slots in the table. Then, when you set a timer, for say slots 16 and 17, it just overwrites the behavior with the desired new one. So rather than think about all the settings and trying to figure out how the device will behave, just think of it in terms of this table and the order of operations used to change slots in the table.If Setting "16" is set to "OSO" (only solar) and I want to change it to "SNU" ( Solar & Utility") e.g. from 16:00 to 17:59 is it then sufficient to just set the Charge Priority Timer for SNU to 16-17 or do I also have to set the Timer for OSO to 18-15?
Right now, I have my charger source priority default set to OSO. I've configured the timer to use SNU for hours 07-11 and it works as I'd expect: from the hours of 0700-1159, I get SNU, from 1200-2359 and 0000-0659 I get OSO.
This is my understanding as well. Whether it is correct remains difficult to sayIf I understood correct Setting 16 will set all the 24 slots in the table to "OSO"
The Timer settings for "SNU" will then overwrite the corresponding slots in the table, all the others will stay on "OSO".
So in my understanding it should not be necessary to in addition set the OSO-timer.
Is my understanding correct or did I miss something?
It is something very easy to test and is reasonably safe to test so you should just try it out and please let us (this thread) know if you experience some behavior that is different.
I don't have access to anything but an LV6548 so I can't comment on this.Did anybody check if the Command Tool and the described commands also work for Voltronic Axpert models (eg. VM IV)