FWIW, I also tried linuxgpio using a Raspberry Pi Zero 2 using this gist. plus enabling -D HAVE_LINUXGPIO=ON, then connecting the pins to the RPi GPIO, but got this:
$ avrdude -c linuxgpio -p t1614 -v
avrdude: Version 6.99-20220211 (7b79b72)
Copyright (c) Brian Dean, http://www.bdmicro.com/
Copyright (c) Joerg Wunsch
System wide configuration file is "/usr/local/bin/../etc/avrdude.conf"
User configuration file is "/home/pi/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
avrdude: no port has been specified on the command line or in the config file
Specify a port using the -P option and try again
So some sort of multiplexing of shunts into a single INA228? Unfortunately this will interfere with the signal too much to make it reliable, the voltages being measured are tiny (like tens of mV).
Additionally, you also need to provide voltage isolation between the shunts to avoid short circuits.
What I did for programming the ATTiny1614 is use a generic USB<->UART cable (same that I used for programming Arduino Pro Mini boards) with a 4k7 R connecting RX and TX together as the UPDI pin and passing 5V / GND through as-is.
still waiting for 5 LM5009AMM to arrive (ordered in 21st Jan ) in the meantime I ordered and today received a PZEM-017 shunt (200A).
Tried to connect it in either of my setups (one is 8S 304 EVE, the other is a test rig with 4S2P 18650) with no luck.
I think I got the settings right:
I also added a 110Ohm (cannot easily make 120 with the bits I have here guess it’s no big deal…) on the 50cm long bus cable from controller to shunt, wired the rest I believe right, but I get no values whatsoever as can be seen on the lower left of the pic above. Stuart’s video shows proper values there.
Now, one controller as a blob of solder on the JP4, the other hasn’t (the only think I’m not quite sure if I need it or not.
Running latest code (as in two weeks)
obvs missing something, anyone kind enough to point me to the right direction?
Mind, if I hit the save basic settings at the bottom, I get a refresh of the screen with all cells filled OK bar the 200A and the 75mV on the top of the section. Bat capacity, fully charged v, tail current, charge efficiency (I understand they don’t work with this shunt) values stay. The only two that mater just disappear.
cheers
V.
PS. I’ve not taken apart the shunt box to check for soldering failures, maybe I should!
yes, got the blob, so that the 120Ohm is fine.
About to go to the local el.shop and get a few 120Ohm resistors for the box as multimeter currently shows 110Ohm (2X220Ohm I had around).
I find it hard to believe that two boards have both tiny leg chips (TCAs) working fine and the big bugger 8feet jobie failing… Unless it’s the wrong 485 chip!
maybe swapping A to B (I’ve followed your video so currently A goes to A and B to B)
will report back in an hour or so
You can find pymcuprog via pymcuprog · PyPI. This will require using Python and PIP (package installer for python). There are other options available but this is what I use as other options did not work correctly under Linux or did not support updi over uart.
) in the meantime I ordered and today received a PZEM-017 shunt (200A).
