I had feared this was coming — Lacroix Underwater

[Evwan]

I have new motors coming in for my D100s board, will need to reprogram. Guide will be made then.

[Shadowfax]

@DougM

I would love to see this guide! Mine’s a D100S.

@Evwan

Guide will be made then.

I made some notes when I set up my 4wd d100s’s

@Shadowfax

Adding some notes here on 4wd setup for d100s.

• make sure to never plug in or unplug a d100s while can is connected. Can chips will explode.
• Detection wizard sets bad (very low) absolute max current values. After running wizard, set to 250a per side. (believe this is the setting that hitting default value provides).
• master side (switch side) = off after 30 min
• slave side = always on
• on off shit resets after input wizard. Check on/off settings after doing input.
• known d100s bug - bad low speed brakes. Solution - run full current mode with reverse erpm limit to -10k erpm.
• fault time to 80ms
• only one esc should be set to “current control”, other escs need to be set to “off”

4wd setup (after both escs are plugged in)

• connect can h and can l between d100s’s
• run switch, ground, 5v from momentary button to ESC 1
• split switch wire and run only that that to ESC 2.
• remember not to unplug one of these while can is connected or you’ll blow up the ESC. @YUTW123 please fix this.

One more known bug for 4wd

• long power button press (0.5s) is required to turn on both escs. A short press will only turn on one of the escs. Only a short press is required to turn one or both of them off.

[Dinnye]

One more thing to add. Empty out both uart ports while you do motor detection because it messes with the values. And even if the values calculated might seem consistent or normal, it doesn’t guarantee that they are the right values.

I had 180A set per motor with bad detection values and whatever I was doing it didn’t go over 140A. Redid detection without anything in the uarts and suddenly the current can actually reach 180A. Bad detection values can also cause overcurrent errors and other issues, so this is important.

[jack.luis]

@Dinnye

One more thing to add. Empty out both uart ports while you do motor detection because it messes with the values. And even if the values calculated might seem consistent or normal, it doesn’t guarantee that they are the right values

Does anyone know why this happens? Seems like a design oversight

[Dinnye]

I don’t know the reason for it but it definitely does happen. I didn’t have an issue with this on my DV6 or first batch DV4S, or at least didn’t see a sign suggesting something is bad. But David from makerx said that it happens on all his escs. I have a newer DV4S too but I have yet to set that one up, will be interesting to see if it also does this.