0

I am developing a mobile app to do some OBD2 tests and monitoring via bluetooth and i want to write some OBD2 commands inside a for loop, in a interval of a second (1000ms) or even less. Is there some chance of damage the ECU of my car or some limitation (number of written commands to x ammout of time) in the way the ECU could answer to my commands?

Cœur
  • 37,241
  • 25
  • 195
  • 267
Cristiano Beviláqua
  • 3
  • 1

1 Answers1

2

You’re not gonna do damage, if it’s too much it will more than likely just stop replying.

When programming an ecu it communicates about about 1 message per millisecond. So I’m sure a few messages every second will be nothing.

Damon Earl
  • 324
  • 2
  • 8
  • Thanks! By this way, 1 message per millisecond is very good for what i'm planning to do. – Cristiano Beviláqua Apr 12 '18 at 19:00
  • In newer cars it can be up to 0.1 ms per message. All depends on what you're working on. But the way all protocols are built, you'll be waiting on the car not waiting on the computer. – Damon Earl Apr 13 '18 at 03:54
  • OBD is pretty safe in these cases. You can send how frequent you like but at the end the controller decides to response or not...... As a brainstorm, What would happen if we overload the controller with messages like what the hackers do to make a website down. – mohsen_og Apr 13 '18 at 11:40
  • Usually these automotive modules are programmed to have a priority of operations. For instance if you log freeze frame data too fast on cars, it will not kill engine operations it will just stop communicating or delay the comms. – Damon Earl Apr 13 '18 at 21:28