We used to put in what looked like sheets of plasticized steel wool to cancel noise reflected along slab faced metal cansPutting the IPU cover back on caused my OBDIIC&C to keep resetting due to interference on the H Line.
Noise really bounces around in there with the cover on..
Anyway I cured it by adding a tiny 10nf ceramic cap between the HLine and GND at the OBDIIC&C pcb.
I have seen this sort of thing before with mods in the back involving re-routed and extended HV wiring..
I pushed these batteries hard this weekend... I didn't feel anything noticeably warm, but note that I haven't programmed LiBCM's QTY17 temperature sensors yet... so it's hard to tell what the actual pack temperature is. It's on my list, but right now the beta testers are running blind as far as pack temperature.Peter, are you seeing much heat from long pulls? I have a hard time going through one charge before thermal throttle takes over and I upgraded my fan again and this was in roughly 75 degree weather (22?c)
Whoa, that's really bad! First I've heard of that happening. How do you fix it? Key off and on?In regards to noise in the IMA bay, I did notice that my Pegasus was acting up... a couple times my instrument panel froze up. It's possible we'll need to add some ferrite cores after all. I'm considering putting them on the BMS leads, so that the voltage stops jumping around. Not sure if that'll work, but I'll be testing it out next time I take out the pack (probably next month when LiBCM RevC arrives).
Changing SoC, in my experience, has been way more reliable (100% so far) at controlling regen. If SoC is 60 you're getting background regen. If it's 72 you're not. I feel like SoC is the magical lever to push.-With the existing algorithm the background charge tends to keep the pack topped off... Even when I hit the assist hard, within half an hour the pack is full again. I get that this background regen isn't ideal for hypermiling, but on the other hand it does allow the pack to stay charged during long trips.
-Based on my anecdotal observations, the MCM will continue charging the pack until it rises above a certain voltage (TBD)... even with the "disable regen" flag set. For example, when I was driving down a 9% grade for more than 1000', the MCM was still charging the pack even though the regen_disable flag was set. I just used Calpod... but certainly something we need to adjust with the firmware.
I haven't reported it yet, because I haven't looked into the root cause. Yeah, basically the entire instrument panel freezes (speedometer, etc), and doesn't unfreeze until I keyOFF/ON... the Pegasus joystick is non-responsive.Whoa, that's really bad! First I've heard of that happening. How do you fix it? Key off and on?
Any other symptoms?
If you can reliably reproduce it, try with the OBDII connector unplugged. Wondering if noise on the H-Line is doing something funky, or if the ground loop might be putting too much noise into the board.I haven't reported it yet, because I haven't looked into the root cause. Yeah, basically the entire instrument panel freezes (speedometer, etc), and doesn't unfreeze until I keyOFF/ON... the Pegasus joystick is non-responsive.
I'll let you know more when I research it more (later). The problem is almost certainly on my end. I don't actually think it's a noise issue, because I was able to reproduce it with Calpod on.
I wouldn't worry too much about it. We'll cross that bridge when we get to integration hell (again) in a few weeks.
Much appreciated.-Latching, right angle ribbon cable connectors
-QTY3 new temperature sensor to directly monitor each battery
Pegasus works just fine with the OBDII connector unplugged. Note that the H-Line isn't connected to LiBCM (at the moment, although technically it is supported if the H-Line is routed to the LiBCM PCB). I can reliably reproduce the hang whenever Pegasus is plugged in... it wasn't always like this (with LiBCM), so I'm wondering if the data I'm sending on BATTSCI is 'good enough' to keep the MCM happy, but not properly formatted for whatever Pegasus is expecting?If you can reliably reproduce it, try with the OBDII connector unplugged. Wondering if noise on the H-Line is doing something funky, or if the ground loop might be putting too much noise into the board.
I'm pretty confident this won't be an issue on the new version (it's all-around better designed, and with isolated OBDII communication, so no ground loops), but it would be good to narrow down what is happening.
And the firmware will have a watchdog, the prototype firmware doesn't.