kerregan Looking at the attached schedule and the log, it seems that at 2.30 a command was issued to hold the charge at the then current level (67%) rather than continuing to charge and hold to 100%. Thoughts? terrible-guidance
admin kerregan Looks like this is related to the continuous block, and doesn't get re-evaluated at the beginning on the new Agile Charge window because of this. We'll work on a fix.