Back guys. Sorry about the firmware updating issues. 1.2.3 is available and should resolve the issue. Also, Thanks Russ for the logs that you sent, if anyone else could provide some logs making note on if bluetooth was enabled, satellite radio, etc, that would be great!!

For those interested in submitting a log file using the debugging firmware that I mentioned in post 160, I could use logs that do the following:

1. Alternate between C and F on the ambient temps

2. Turn blutooth on and off

3. Switch between FM and Satellite

Please do not do anything else so that we dont clutter the logs. Whichever test you choose to do, please do it a few times in the same log (i.e. go back and forth between C and F on the outside temp a few times)

This would be a big help!

Updated - logs sent. Still crashes on exit :(

Awesome, got the logs, you guys are a big help and i am definately seeing some stuff in these logs that i dont see on my car (since i dont have BT, etc).

Crash on exit? Now does this happen every time or only after a certain procedure (after updating firmware, after checking a box, etc)? Thanks!!

Paimon,

It looks like the average miles per gallon is aactual MPG. What I have found is that if after running the car for 30 miles and I come to a stop, it shows the average MPG at 0.00?

Also, I personally think it would be nice if the MPG and Average MPG updates were much slower. I think the MPG could be at 1 second and the average at maybe 10 seconds?

I'll be happy to report this in the bug database if needed.

Keep up the great work!

^^^WHS about the MPG - and *IF* possible, a "trip" MPG and "overall average" (resettable) - but I don't know if the RxD can "Store" anything in between times?

With the Console - I've just started and exited it - no "program stopped" dialog box (yet) but left with an unhealthy black box.

Yep got these from seanp as well, noted in my future changes ;). Thanks! Still waiting for logs from people using the test firmware if you guys get a chance. I think I may have figured out the bluetooth issue, would also love to see some info on how to change the units of the outside temp :D

Tried to get logs today. The latest 1.2.3 firmware crashes on my laptop (win7). I think it's because I don't get wifi in the garage 'cause I seems to work fine in the house...

You are right, found that out today at work. Update available now :) thanks!!

thanks! just e-mailed you the results.
The console still crashed on exit fyi.

Just replied to your email. I need the logs with the firmware discussed in Post 160 :( . Links are in the email.

Sorry, I'm not stock anymore so my logs won't help. Or, will they?

If you need something, you know how to get in touch with me..... I'm more than happy to help.

RxD Console 1.2.4 still leaves a black screen here; with or without RxD plugged into machine; connected or not connected. Wired network active (no WiFi). Windows 7 x64.

hrmm this is very interesting. I would like to do a join.me session with you tomorrow if that is ok. I am on EST so it is currently 10pm here. I am not sure what time works best for you, but I get out of work around 4pm EST

Also for those that are reporting that the Console crashes on exit, mind elaborating a bit? Does it crash with all firmware? (i.e. did it crash when you tried the debug firmware?)

Does it crash both ways of exit (exit button, clicking the X at the top)

Sorry for the delay, caught up rebuilding the computer.


Just sent you my logs with the debugger file.

Crashed with both the nightly/debugger. And also both the X and exit button.

no problem at all, your logs were amazing thanks! gunna study these but i think i see where the C/F change is done, gunna have to test it on my car tomorrow.

Anyone test out the latest version of the console? (1.2.5) few new features, like the "Break" point insert. This is great for anyone who wants to get me some more logs. They can click "break" and it will place a breakpoint in the console before they perform a task. For example you can do "break" then start toggling F and C and then press break again. Hope that makes sense.

Anyway, I also fixed the issue where the app would crash on exit. Please let me know how it works out. Btw thanks everyone for their logs, they were amazing and I am making some progress on deciphering the bluetooth issues. ;)

Works good for me. I'm on Nightly: 7/19, 6:04pm build.

I did notice that if I change the response time, it continues to show 62ms as the output. I currently have it set at 250ms

Printing Welcome Message
|RxDUINO||v1.02|
|RPM:|||
|RPM:|||
|RPM:|||
|RPM:|||
|RespTim||e|
|62||ms.|
|62||ms.|

That is actually another feature I disabled for the moment while we figure out the console display fighting. The only reason is because I didn't want people to toggle that setting yet and have it fight like crazy with the radio display :( sorry.

Thanks. I know this is a side project and time is tight but if you could produce a change log, that may help some of us. :-)

Good Idea. Expect a change log on future builds :)

Had to fix another wire on mine again. But it's working and will be testing the initial firmware today or tomorrow.

This time I fixed it for good though. I noticed the cable would pull on itself and break the solder points off the serial connector, so I ended up krazy gluing the crap out of the cable where it goes into the serial port.

I can lasso this thing now and it won't budge...lol. :)

Oh wow, are you pulling out the cable my tugging on the actual cord? lol. I installed relief grommets in the ends to counter this but looks like it isn't working that well...

Yeah lol. I guess I must've tugged on it early on and loosened the wires. It's freaking tight as hell now...lol