10528 réponses à ce sujet

[pierre]

Si c'est moi

[arkansar]

Hooo lardon lardon!!! (Ça.fait longtemps Pierre)

[firened]

It seems the IP2312 is picky regarding input voltage. Datasheets states a current gradient depending on Vin, with
Vin: 4.5V = 0A charging and
Vin: 5V = 2.1A charging and
(Vin: 5.5V = 3A charging.(?))

The problem is, with the robot running and using ca 1.5A, the Vin is low enough that the IP2312 only charges with 0 - 0.3 A.

I had no other idea than to build a converter, with a PD decoy requesting 9V from the PD2.0 charger then a step-down to
first ca 5.5V = 3A charging, but the magnetic plug gets too hot.
then ca 5.3V = about 0.7 A charging, together with the robot's usage of 1.5A, results in a total Current of 2.2A, which gets the magnetic plug somewhat hot still....

I wish there was a better way, and think using a higher charge voltage like the geekworm v3 (9V or 12V) would be better. @Garfield2142

[garfield2142]

On the bottom of the new beta vigiups board, there is a solder bridge for Vusb, should I try bridging it to 9v or 12v?

[firened]

Is this to set the requested USB voltage @Mike118 ? If so then, that's dope AF.

"CH224K Low-cost USB-PD Sink Controller" <https://components10...-controller-ic>

Must be it!
Then yeah, probably 12V, that should fix the charge speed and magnetic plug temperature

[garfield2142]

Alright, I'll revive Pluto, then set Panther's vusb to 12v and see what happens!

[Mike118]

You can checked BQ25792RQMR datasheet.
For the new charger and yes it is a CH224A
@Garfield2142 this is the issue when charging :
05/08 18:59:17:257 | | Client | Reception of a text frame
05/08 18:59:17:282 | | Client | Reception of a text frame
05/08 18:59:17:316 | | Client | Reception of a text frame
05/08 18:59:17:349 | | Client | Reception of a text frame
05/08 18:59:17:382 | | Client | Reception of a text frame
05/08 18:59:17:740 | | Client | The eSpeak process is stopped after 487 milliseconds with the exit code 0
05/08 18:59:34:851 | | Client | Error: EIO, Input/output error
05/08 18:59:34:860 | | Client | at Bus.writeI2cBlockSync (/usr/local/vigiclient/node_modules/i2c-bus/i2c-bus.js:523:9)
05/08 18:59:34:860 | | Client | at Ina219.writeRegister (/usr/local/vigiclient/node_modules/ina219/ina219.js:159:12)
05/08 18:59:34:860 | | Client | at /usr/local/vigiclient/node_modules/ina219/ina219.js:374:9
05/08 18:59:34:860 | | Client | at Ina219.writeRegister (/usr/local/vigiclient/node_modules/ina219/ina219.js:160:2)
05/08 18:59:34:860 | | Client | at Ina219.calibrate32V2A (/usr/local/vigiclient/node_modules/ina219/ina219.js:364:7)
05/08 18:59:34:861 | | Client | at Timeout._onTimeout (/usr/local/vigiclient/clientrobotpi.js:1128:11)
05/08 18:59:34:861 | | Client | at ontimeout (timers.js:436:11)
05/08 18:59:34:861 | | Client | at tryOnTimeout (timers.js:300:5)
05/08 18:59:34:861 | | Client | at listOnTimeout (timers.js:263:5)
05/08 18:59:34:861 | | Client | at Timer.processTimers (timers.js:223:10)
05/08 18:59:34:861 | | Client | Following this uncaught exception, the Node.js process will be terminated automatically
05/08 18:59:35:932 | | Déconnexion du robot Socket.IO TbWmNPXVzKu5OoHIAkA1

[firened]

@Garfield2142 is your voltage meter script already running?

[garfield2142]

No, I didn't make one yet

[firened]

Did it crash this way before we added the current bar?

[Mike118]

This is not linked with adding current bar. There is this i2c error when charging and The charger is connected on the i2c bus.

[garfield2142]

The client crashes when using my 67W xiaomi charger, which can provide 12 volts. The INA219 shows 1.5A of charge, then the client crashes with the error above. Sometimes the client starts back up without any voltage or current sensing. But if using a regular 5v charger, it's stable.

[Mike118]

You can try to set 9v instead of 12v
This is the charge crash problem. But I still have no clue about the second kind of crash yet. Do you tested without your BMS ?

[garfield2142]

Check the captures I made. I connected a lab bench power supply directly to the battery terminal, and it still crashed when going at full speed. I suspect the cables though, so just to be 100% sure, I'll try to solder some manly thick cables directly from the power supply to the battery connector

[garfield2142]

1.75mm copper wires soldered directly to the battery terminal. No batteries. No BMS. Soldered banana plugs. Tried to go forward while holding down the robot to simulate an uphill ride or pushing something. Almost instantly crashed.

1754477254151_garfield2144_Panther.mp4   1,16 Mo

[firened]

A valid test Setup i think
Should have worked.

[Mike118]

I start to think that the issue is the resistor used for Ina. Can you try to short the ina resistor with a wire ? Current will not work anymore but I hope it will not crash anymore.

[garfield2142]

You mean this resistor?


Alright, it definitely behaves differently now. If I push it strong enough and at low enough voltage, I can shut off the entire UPS and I have to switch off and back on, but I guess I'm pushing it past what's normal now. I'll plug the battery back in, and stress test climbing some slopes

Unfortunately, setting VUSB to 9V made no difference to fast charging, the client still crashes.

[garfield2142]

After testing for a while, I can still easily crash the pi by just casually driving around

[Mike118]

Yes this one.
What battery are you using ? You have a second robot. Does it have the same motors? Can you crash it the same way ? Can you switch some hardware between both ?