Looking forward to hearing from you! You can contact me via e-mail. If someone is intterested in the logs I made from the two busses, let me know and I can share them. If someone for example already has a CAN-BUS log of a Tesla Model S, I could do a playback and see what happens and eliminate rows from the playback to find out what CAN ID’s are inputs for the iBooster. If you have any ideas or input on how we can move forward, please drop me a line. Once I get my hands on such a log, I can do a playback to the booster and see whether we can get it to work on the bench. The vehicle CAN of the iBooster should be available on the diagnostics port. Think it would be beneficial to get CAN data from a driving Tesla. So what’s next? This is as much as I can do for now with my set of skills, tools and hardware. However from a deviation from IDLE position you do know the brake is being pressed.
Furthermore the value range will depend on the brake pad travel and will be different on every car. The only thing is that it does not tell us how hard someone it pressing the pedal. Potentially this value can be used to trigger regenerative braking. The output with the push-rod in IDLE position is 0x40 (so 64 decimal) and when fully pressed the value is 0xC0 (192 decimal). Jon has figured this out (it’s not only Byte 3). It looks like Byte 3 of message 0x38E represents the push rod position. While pushing in the rod on the YAW CAN-BUS I did get some consistent results. On the YAW CAN-BUS only two messages are being send, 0x38E and 0x38F.
Additionally it can be used to overrule any throttle input. You can immediately (gradually) increase regenerative braking and don’t have to wait for pressure buildup. The advantage of using a CAN input based on stroke is that it is faster.
That signal is then used in the vehicle control unit (VCU) to also activate regenerative braking.
Ibooster funciona driver#
Traditionally a pressure transducer is used to know the driver hits the brakes. This can be useful to improve regenerative braking in a conversion.
0 kommentar(er)
