You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing that we could do is use an old fashioned miniprog instead of a kitprog and ensure that it does not attempt to power the device when programming; however in the past I've had trouble getting the modem to connect when the oscilloscope is attached to the charge controller ground line.
The text was updated successfully, but these errors were encountered:
Taking automated power consumption measurements is proving difficult. When the kitprog is attached, no power is drawn from the charge controller.
When power consumption measurements are taken directly off of the ground line of the kitprog, it has a 0.05 A offset and doesn't hit the expected peak of ~0.3 A:
http://ec2-13-58-145-29.us-east-2.compute.amazonaws.com:3000/dashboard/db/power-consumption?orgId=1&from=1504091159800&to=1504091442009
One thing that we could do is use an old fashioned miniprog instead of a kitprog and ensure that it does not attempt to power the device when programming; however in the past I've had trouble getting the modem to connect when the oscilloscope is attached to the charge controller ground line.
The text was updated successfully, but these errors were encountered: