-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random Invalid module response received #25
Comments
Yes, it's probably EMI. You're getting the proper number of bytes returned but not the proper CRC so chances are the data has been corrupted. If this only happens every so often you can essentially ignore it. The code knows to discard any traffic that was corrupted so it shouldn't mess anything up. It just means you aren't always getting the latest data. About all I can suggest is to keep your noisy wires away from the signal wires, if they have to cross it is better to do so perpendicularly, and perhaps shield and/or twist your noisy power wires. |
Thanks for responding, I am having the exact same issue where my 10 boards show up as 20 with different voltage levels. |
Im still dealing with this issue. The lf inverter mosfet switching is causing a ringing noise that get sent thru the battery cables to the modules slave bms. This gets to the UART wires. @collin80 how have you dealt with this before? |
Ah yes, a problem near and dear to all of our hearts. Inverter switching noise is a nasty thing to deal with. There are multiple layers at play here. The Model S modules regenerate traffic at every hop. So, comm becomes clean again at every module and is re-sent fresh to the next in line. This limits the amount of noise that can be coupled. So, the best advice for the wiring near the batteries is to keep it away from your power wires as much as possible. When they come near each other they should do so at right angles if possible. This should limit the amount of noise and every module refreshes the signal so noise is not cumulative. Long runs of wire would be best if you could shield them or shield the power wires. If at all possible they should not run beside each other parallel. If you have to do that then one or the other or both should be shielded. Ground the shield at one end only to make it into a big antenna to ground. Lastly, the modules run fine at 3.3v but if you can utilize 5v instead you will be better off. The higher the voltage differential between states, the harder it is to corrupt. The official EVTV boards all use 5V signaling down the lines. You can use 3.3v and people have. But, that will be a bit more noise prone. I believe the lowest voltage that works is around 2.7v. |
Im having these random errors. Errors are not module constant. Im trying to isolate the problem but Im out of Ideas at this point.
I tried changing comms from serial 1 to serial 2 but problem persists. Do you have any idea what could cause this? Here are some examples
2195768 - ERROR: Invalid module response received for module 9 len: 22 crc: 130 calc: 138
2198530 - ERROR: Invalid module response received for module 10 len: 22 crc: 166 calc: 205
2198551 - ERROR: Invalid module response received for module 1 len: 22 crc: 67 calc: 5
It happens more frequent when Im running my LF inverter, not sure if EMI might be the culprit.
Im using a arduino due with direct 3.3v connection, also tried 5v with an bi-directional logic level converter but still get random errors.
I added contactor for precharge and main. Contactors and arduino are powered with a 48v to 12v stepdown converter.
Thanks in advance for your asssitance.
The text was updated successfully, but these errors were encountered: