Maybe I'm not updating it correctly. I thought all I had to do was delete that text and right in new text?

When I submit the PING command it says serial communications "OK".

You should be able to type the following into the console:

TXT Love Rotor

and it would update the stored text to "Love Rotor"

Or in the car, you could hold cancel on text mode so that it switches to "Edit Text" mode, then use "up" or "down" to cycle through the letters, and press "Cancel" to go to the next position. To save your text, hold down Cancel. If you still have trouble let me know and we can do a chat session!

That's what I thought but it didn't work. On a another note - hooked it up in the car and the default display text didn't come up. Started right at RPM's.

Got time for a chat session?

sure! emailing you now

mine is working now! Great on-line support!

Appreciate the help in the join.me session! - I'm seeing the display battles as well but as others have said...not every time.

Thanks Russ and Are-Ex-Eight, appreciate the kind words.

I am working now to resolve the fighting text issue some of you are seeing. Once I fix that i will release 1.02

I took my car out for a test drive, all works well, all displays work and in fact stop fighting after a couple minutes with the build-in radio. I will update with a few more on/off cycles and try to give better timings. Even with radio on, I only ever see the RxDuino output after it settled down. The radio seemed to lose out every time. The only other display feedback I have is for the wheel-speed indicator. It seems to have a very infrequent update and basically goes blank most of the time. Other readings display well.

I'm sure the sluggish input will be perfected soon. thanks,

russ

Updated nightly posted. For those who downloaded the previous nightly you will notice that units are not displayed. I have fixed this in the latest nightly, it will be part of 1.02 as well.

Went out to do some timings on when the display clears up. After ~ 5 minutes the RxDuino wins all the time on my car. At the beginning sometimes it is very difficult to read but that smooths out quickly. I will try on a few start stops tomorrow. This is factory radio on or off.

got it working with the FDTI drivers and updated to the current nightly. I'll put it in tomorrow morning and see how it goes.

Thanks for the update. I will add a note to the bug report to reflect this. I basically have a 50ms hardware delay after sending information to the screen. I can reduce that delay and see if that helps out.

Good to know, keep me posted! I will be sure to add the FTDI driver download to the console to make that easier for others.

I'm looking through the bug tracker, and I am having most of those issues myself. I'll wait to check future firmware.

On a side note, the odbII plug is a little too long for my fat leg...lol. While I can drive fine with it, I am scared I'll hit it if I leave or enter the car. I'll figure it out I guess. :)

Paimon take a look at the miles per gallon stuff. The numbers seem really low. I'm getting less than 10 on the highway.

Also is engine temp in deg C and cat temp in F?

Paimon,

For the display updates, if you can send more frequently during the initial 5 minutes or so and then back off to the current display update frequency I think you'll have it made. I don't have any interference problems after that time.

russ

Hey there, so here is the equation that I am using for MPG:

MPG = 710.7 * ((VSS) / (MAF))

That is actually how the scangauge does it. I will have to double check my numbers to make sure I am doing the conversions in the right order of magnitude. Thanks for bringing that to my attention.

If anyone has a scangauge could you chime in and let me know if it shows instantaneous MPG? The RxDuino shows me @ 20 someodd mpg when coasting to a stop, and down to about 9mpg when I am accelerating.

Also, all temps are in *F

Seriously my engine temp is 125 deg F with WOT?

Seems very cold.

Hrmm, i will check on that. Is that the only temp for you that seems off?

Btw, new Nightly has been posted that increases the display rate. Please let me know if this makes the "Fighting" worse or better.

New nightly should also have a more accurate MPG (haven't tested on the car, just arbitrary debug data)

tried out the new nightly (7/2), still having some issues.

-can't scroll UP through the monitors. Once at the bottom of the list, it's stuck until I unplug/turn it off.

-opposite of russ' problem, the texts fight, but the stock radio wins in the end.

-Engine temp is also strange ~120F after 20 minutes of highway.

anyone else having the scroll up issue?

I am working on the display issue right now, hope to have a fix real soon!

And the engine temp is something I will look into as well, lower in priority compared to the other 2 issues so it may take a bit before you see that fixed.

Ok so I updated the OP and FAQ. I am now linking to the nightly repository. The nightlies are now dated, and will print their date in the console just so we dont forget which nightly we are using. I have also posted up a new nightly that greatly reduces response times and should help out a lot more for those of you who are having issues with the delayed responses of the cruise buttons.

RxDuino_7_2_2012_10_15_pm.hex is the name of the file

As mentioned in the FAQ in the first thread, go to http://www.therxduino.com/nightly and right click on the nightly you wish to download, and Save As into the directory of runme.bat (The manual updater). Make sure when you save the file you save it as RxDuino.hex

I started keeping versions here. The 10:15 version you sent me definitely works the best as you can see in the video. Scrolling up is not as smooth as down but much improved over earlier ones which were VERY slow. Definitely moving in the right direction!

edit:

Some feedback on temperatures: IAT and Engine temp showed 71 and 72 degrees F respectively. The ambient temp shown on the outside temp display was 86 at the time. The car had been off for a while. May be normal but seems off. I will compare IAT when running tomorrow. I did notice when engine was hot that temp said 118 on earlier firmware version but may have been centigrade which puts it in the ball park.

I plan on downloading the console to the wife's comp on Wednesday to update my RxDuino. Will all of your current updates automatically install into the box or will I have to do them manually one by one?

Thanks for all of your testing russ, much appreciated. Good news that the latest nightly improved response times, in fact i believe it puts us close to a resolution with the display fighting (right now the messages i send to the lcd screen are on a 10ms timeout, which seems like it is in line with the frequency that the radio and rxduino are fighting with eachother. I will reduce that timeout today after work and hopefully that will help put this issue to bed)

You wont have to do them one by one, but I suggest you get the latest nightly as it has a lot of fixes over the shipped firmware. To update you will need to download the "Manual Updater" i linked in the first post. Check out "4Q" in the FAQ in the OP for instructions.

Mine didn't scroll up or down when I tried. Not going to be home until later, but I'll try everything again tonight with the updated nightly.