IChip parameter loading code locks up

[collin80]

There seems to be two ways to lock up the initial parameter setting. The first one is to try to change the logging level while the ichip is active. The second is to not be in loglevel=0 when the system starts up. Both are big problems. This happens with the code in the ArduinoDue branch.

[neuweiler]

Does this have to do something with my recent changes ? I can not
remember to have experienced these problems but will test again.

On 06.05.2014 21:54, Collin Kidder wrote:

There seems to be two ways to lock up the initial parameter setting.
The first one is to try to change the logging level while the ichip is
active. The second is to not be in loglevel=0 when the system starts
up. Both are big problems. This happens with the code in the
ArduinoDue branch.

—
Reply to this email directly or view it on GitHub
#61.

[collin80]

No, I think it had to do work all of the extra stuff I added for elm327 emulation. Also, it could be just me.

On May 6, 2014 4:28:08 PM EDT, Michael Neuweiler [email protected] wrote:

Does this have to do something with my recent changes ? I can not
remember to have experienced these problems but will test again.

On 06.05.2014 21:54, Collin Kidder wrote:

There seems to be two ways to lock up the initial parameter setting.
The first one is to try to change the logging level while the ichip
is
active. The second is to not be in loglevel=0 when the system starts
up. Both are big problems. This happens with the code in the
ArduinoDue branch.

—
Reply to this email directly or view it on GitHub
#61.

---

Reply to this email directly or view it on GitHub:
#61 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[neuweiler]

Yep, you're right. If I comment out the elm327 stuff in createObjects()
and in loop() of GEVCU.ino, then there's no freeze. Even with 1.5.6.

On 07.05.2014 01:03, Collin Kidder wrote:

No, I think it had to do work all of the extra stuff I added for
elm327 emulation. Also, it could be just me.

On May 6, 2014 4:28:08 PM EDT, Michael Neuweiler
[email protected] wrote:

Does this have to do something with my recent changes ? I can not
remember to have experienced these problems but will test again.

On 06.05.2014 21:54, Collin Kidder wrote:

There seems to be two ways to lock up the initial parameter setting.
The first one is to try to change the logging level while the ichip
is
active. The second is to not be in loglevel=0 when the system starts
up. Both are big problems. This happens with the code in the
ArduinoDue branch.

—
Reply to this email directly or view it on GitHub
#61.

---

Reply to this email directly or view it on GitHub:
#61 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

—
Reply to this email directly or view it on GitHub
#61 (comment).

[neuweiler]

check out the code on my pull request of today. I invested a lot of work/debugging to get the ichip communication ironed out. It also differentiates between WebSocket or ELM-Sockets and would support multiple open sockets and adds a watch-dog which resets the ichip in case it crashes (due to high traffic on websockets)