Yep. We screwed up the software labeling somehow so it doesn't match the label. I've got patched software that I just need to verify matches the label and that all of the overcurrent stuff still works after the fix. I honestly had thought that this had been completed and that we were already shipping revised code until someone asked about it a week ago. A look in the code confirms a fix was applied but I can't confirm it was tested so that's where we stand.
Unfortunately, the workbench with all the relevant tools on it has been tied up this week with a project which was in the "a lot of pieces which are all wired together and impossible to move without wrecking everything" stage so I haven't been able to verify the fix. That project is finally in a more moveable format and I should be able to compete this testing this weekend. Unless something unexpected happens, look for a firmware release most likely late Sunday, with an email to everyone who purchased one shortly thereafter. On Jun 12, 2015 1:45 PM, "Adam Moffett" <[email protected]> wrote: > So I just set up two PDU's where the outputs on the label are in the exact > opposite order compared to the labels displayed in the web page. In other > words, where the stcker says "out1" the web page says "Output 5". > > It caused some confusion...and it's a good thing the circuit breakers work > :) > > If this is the way they're all going to be, I can just relabel them in the > web page and move on. If it's an error in assembly I'm worried that any > SNMP probes I'm making to track tripped ports are going to be opposite on > future units. Anybody know? >
