arachnidlabs/reload-pro

Schematics and code for the Re:load Pro

reload-pro's Issues

Add "reset to 0" menu item

I think it would be useful if a menu item would be "reset to 0" and take the currently adjusted setting to 0.
Alternatively, the "reset totals" could be extended to do this on top of what it currently does. It's tedious to go to 0 from 2A for example

Undervolt condition reported as OVERTEMP

FW 1.7

The "undervolt" event is reported as "overtemp" in the serial protocol.
Should be "undervolt".

More than 2A current is drawn during calibration.

The manual says that the power supply used for calibration must be capable of supplying 2A DC. Mine starts to limit at about 2200mA, so meets this requirement. During the final step of calibration, where the load is pulsing on and off, the last few pulses cause the power supply to go into current limiting. i.e. more than 2A is being drawn.

I don't know if this is affecting the quality of calibration (I have a current error of about 6mA, whereas the specification suggests 2mA).

Firmware is 1.9.

Maybe related to issue #15?

Send unsolicited 'set' over serial when user adjusts the setpoint

Find a good solution for cable egress for fan kit

switch on load when asking to set voltage in calibration steps

this is basically a power supply issue or leads voltage drop)

when the voltage is asked no load is applied,
if in the voltage is then set to the 'no load value" and for the second step the actual voltage drops then it seams the "low" values for the load (20 mA etc) are less accurate and "catch up" when going to higher loads (if you test the RE:load after calibration)

the 1.9 firmware solves this to a degree but not completely

sugestion : activate the load to 2 amp when asking 'set voltage'
( added value: if you have only one decent multimeter handy you can better check the voltage the ps gives at the RE:load binding posts and that then takes also into account lead loss , then pull it out and set it in series to check the amp in the next step)

Bigger steps when rotating the encoder while pressed

Would be useful if the steps for (in|de)crementing the set value would be bigger if the rotation is performed with the encoder switch pressed.
As it is, it is tedious to move from ie. 0 to 2A load and back.
Related to #27

Left display corrupted

FW 1.7

Left display is corrupted when power is displayed in right display

Explicitly initialize global variables

Apparently that shirks used flash as compared to implicit initialization.

suggestion for better usability: add load on/off menu item as first line

i suggest to add instead a "turn load off" / "turn load on" item as first item (while keeping the set value)
idealy this will need some kind of icon/indication on the screen to show the load is on/off (aldo one would noitce it with the amp reading normally)

that allows you to set a load, hit the button, choose the first line setting the load off (item is then "load off) , should return to main screen

so you have a "preset" , you can then connect the re:load without it pulling amps

then hit button , first item is then "load on" (because it's off :) ) , select it, load is then on, should return to main screen

Load On/Off Menu Item

One suggestion would be to add a Load On/Off menu Item.

Calibration step hangs at last point

It seems like the calibration wizard hangs at what I think is the last point.

The steps I followed

• Remove all leads, press next
• Set voltage to 9.95V on multimeter, and set that value as well in RP
• Power supply goes into short circuit current limiting mode, delivering 3.15A on multimeter. Set that value on RP.
• Calibration. Please wait...
  • First, the RP seems to add various kinds of loads/currents, as multimeter readout goes up and down.
  • After a minute or so, the current goes to zero, the voltage as I configured before.
  • Stays on this screen

Stable display reading

To get a more stable display reading, I would suggest to decouple the display update from the locked loop - maybe via a config parameter?

Calibration: Unable to adjust current

While in calibration mode the voltage can be adjusted, the current can not.
Rotating the encoder has no effect.

Test & tune transient response

Enable alternative current calibrations

Many bench power supplies can not provide 2amp CC.
Please enable lower(and possibly higher?) amperage calibrations.

For example:
My bench meter supplies 1.50amps CC, if I calibrate with this as my amperage, my readings are off by ~300-500ma. The Reload Pro even shows a 320ma load with the probes unplugged.

Thank you!

monitor command overflow?

Issuing a monitor command via terminal, with 10000, or 60000 (10 seconds, or 60 seconds) results in a monitor value of 1 (or so) being set (terminal quickly overflows). monitor 9999' does not cause this same overflow.

Update manual, unit description

Describe what the blue input (output?) is for.

Four digit mAh value display is wrapped.

When displaying mAh, it only has room for three digits, so values of the form xx.x cause it to wrap, displaying the 'h' on the left side of the screen.

Adjust front panel vertical position to match PCB

display bug in menu

Look into better reverse polarity protection

Rework display interface for 3.3v logic

Remove backlight control pin

Duplicate "h" in mAh display

After running for a while, I got a second "h" that showed up for mAh. Guessing this is related to #17

Knob debouncing needs improvement

... which makes menu navigation quite an adventure

Add back entry to all menus

Nix the dots on the zero

Prefer slashs over dots.

Cough ... Cough... I feel light headed ;(

USB Interface Commands

"set 100" results in 100mA to be displayed, serial console returns "set 100"
"set 1000" results in 1.00A to be displayed, serial console returns "set 1000"
"set 10000" results in 10.0A to be displayed, serial console returns "set 10000"
"set 100000" results in 100A to be displayed, serial console returns "set 100000"
"set 1000000" results in 1.00A to be displayed, serial console returns "set 1000000"
"set 10000000" results in 1.41A to be displayed, serial console returns "set 1410065"
"set x" results in 0.00mA to be displayed, serial console returns "set 0"
"set 3x" results in 3.00mA to be displayed, serial console returns "set 3"
"set 36366363" results in 2.00A to be displayed, serial console returns "set 2006624"
and after trying some other values I have managed to bring the unit in an unresponsive state, not reacting to serial commands or knob presses/rotation.

After reboot of the unit everything works again. So trying "set 36366363" again shows 2.00A in the display and returns "set 2006624" over serial. Rotating the knob does not change the display, it remains at "2.00A", but "set" returns different values (increasing/decreasing) when turning the knob.

I would like to see errors returned when "set x" or other non-valid characters are sent to the unit.
Too long commands make the unit "crash" so that it needs a reboot.

Always calibrate from factory settings

Presently, the current calibration values are used as initial values for some calibration steps, which causes weird issues for users when their current calibration is a long way from correct. We should always start from factory settings, instead.

Always return \r\n terminations in serial responses

Specifically, debug currently returns lines terminated only with \n.

Changing set current over a wide range is too slow

The encoder needs acceleration, so that it increments faster if you turn faster.
As it is, it is cumbersome to change from 20mA to 1.5A.

I've implemented acceleration in my encoder Library: https://github.com/0xpit/encoder Maybe you can reuse some of my code.

Send board temperature over the serial bus.

This won't give the temperature of the heat sink, but would still be useful as a way to warn of over-temp conditions inside the Re:load Pro.

Implement lower voltage limit in software

Software feedback loop induces oscillation

In some conditions, the software feedback loop intended to keep set and actual current in agreement can cause oscillations in the set current. Usually these are small, but sometimes they can be a lot more pronounced.

Support setting/clearing UVLO over serial

Implement constant power mode

Current not set correctly when monitoring

When setting the actual current via serial ("set XXX") or via the encoder while monitoring the values (via "monitor XXX" or a thread that calls "read" frequently), the actual current is sometimes set to 0.

When the actual values are requested every 10 ms, more than 50% of the set commands fail, resulting with a set current of 0 mA.
Even with a interval of 500 ms the current is sometimes set to 0.

I think (gut feeling) that the problem is worse when using the monitor command.

ATM I'm writing a client application for the RLP, but this problem makes it hard to graph/monitor the actual values.

Implement pinout for status/trigger/external-input port

Current not 0 after undervolt cutoff

FW 1.7

When the undervolt condition occurs, there is still a current of abt. 1mA or 2mA.
After RESET via CLI, the power is really 0mA.

Widen current traces

After low voltage cutoff power should be displayed

When the low voltage message appears, the currently drawn power (mAh) should be also displayed.

With this feature, I can use the RLP to measure the capacity of batteries.

//Dietmar

Implement constant resistance mode

Serial Headers

It would be very helpful to have a serial port header to traditional TTL or RS232 ports for industrial control without the need of a computer.

Having a 0.1" header for bypassing the USB would help a lot. Solder-jumpers to disable the USB would also be needed.

Update expansion slot with more signals for external power/batter power

Add "quit" to the serial interface

Would be very useful for automation.
Right now, I could use it to put the R:LP in bootloader mode and upload a new firmware in one step.

Measured voltage decreases with current

For some reason the measured voltage decreases with current in line with the value of the shunt resistor. We should fix this in software.

Display goes blank at cutoff voltage

FW 1.7

With enabled voltage cutoff and reducing the input voltage below the level, sometime the display clears and did not show the low voltage message.

When display is cleared, only replugging the USB connectors helps.

When low voltage message is shown, reset sets the current to 0mA. One tick on the rotary restores to the previous level. I would prefer, that the current is immediately restored to the previous level.

linux firmware update (ubuntu/linux mint etc) steps

cyflash needs sudo

$ sudo python -m pip install cyflash

download firmware (for example to /home/user/Downloads/reload/Reload Pro
v1.9.cyacd )

-> connect Re:load Pro usb cable

to find out tty port :

$ dmesg

output
[15561.315782] usb 2-7: Number of endpoints 2
[15561.315786] usb 2-7: Endpoint 1 MaxPacketSize 64
[15561.315790] usb 2-7: Endpoint 2 MaxPacketSize 64
[15561.315794] usb 2-7: Setting MaxPacketSize 64
[15561.316072] usb 2-7: FTDI USB Serial Device converter now attached to
ttyUSB0 <<<--- this is the serial

issue:

$ sudo python -m cyflash --serial /dev/ttyUSB0
"/home/user/Downloads/reload/Reload Pro v1.9.cyacd"

with /dev/ttyUSB0 the value of dmesg output

Tag firmware releases in git

When you update the firmware release in
firmware/Reload Pro.cydsn/Generated_Source/PSoC4/cymetadata.c
could you please tag the git commit with something like firmware 1.5

This will allow end users to view the differences in code between versions and decide if they want to run the risk of performing an upgrade.

Thank you!