\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\
Current Console Version: 1.1.0
Current Firmware Version: 1.01 (Nightlies Available)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\

================================================== ======
NOTICE: Please update your firmware to version 1.01 if you have not already to resolve a few issues with the RxDuino rebooting randomly on some cars. I am currently working on firmware 1.02 which will fix issues with the console commands not communicating with the RxDuino.

BUG TRACKING: http://www.therxduino.com/bug-report/my_view_page.php

NIGHTLY BUILDS: www.therxduino.com/nightly SEE FAQ FOR INFORMATION

================================================== ======

================================================== ======
Using The Bug Tracker
Using the bug tracker will be very valuable to notifying me and the community of issues that you the user are experiencing. Everyone that purchased an RxDuino was given a username and a password (temp password) so that they are able to access the system. To access the bug tracker, please visit the link at the top of this post, http://www.therxduino.com/bug-report/my_view_page.php.

Logging Into The Bug Tracker
The first time you open the bug tracker you will be given the option to log in or to log in Anonymously. If you do not have an account, or would like to view bugs without logging in, you can click "Log In Anonymously" at the right of the login page



Reporting a Bug
To report a bug, you must first be logged into the bug tracker. If you are having trouble logging in or need a password reset, please contact me and I will be more than happy to help you out. Once logged in, you can click on "Report Issue" on the top menu bar



Users should have the option of choosing what product you would like to submit a bug for, either the RxDuino, or the RxDuino console. For this tutorial, we will select the RxDuino to report a bug on. Simply select RxDuino from the drop down box, and click "Select Project"



You will now be taken to the bug details page where you can fill out information about the bug you are looking to report. The most important fields are the required fields (appended with a *)



At the moment there is only one Category, and one person that you can assign to, so there should be no confusion there. Severity and Priority can be used at your own judgement, but please note that they may be edited if the ticket finds itself at less of a priority than another pending ticket. Please feel free to select the target version as the latest available version, but you can leave that blank if you prefer as it is not a required field.

The most important field is the "Description" field. Please try to be concise so that I can easily reproduce the error.
================================================== ======

Original OP
Just wanted to create a thread here that is separate from the development thread and the group buy thread. Basically wanted to start this off first by letting everyone know that a firmware update is available for the device: (copied from group buy thread)

To Update To The Latest Firmware, first download the latest console:

http://therxduino.com/rxduino-console/

then firmware version 1.01 from:

http://therxduino.com/firmware/

And follow the instructions on pages 9 and 10 of :

http://therxduino.com/wp-content/upl...he-RxDuino.pdf


Edit: I am working on a newer version of the console that will alert you as soon as a firmware update is available. (http://www.therxduino.com/bug-report/view.php?id=5)

Frequenty Asked Questions::::::

1Q: My Device Isn't Connecting To The Console!
1A: Looks like a few people are having this issue. I am suspecting that you are missing drivers on your machine or the cable is inserted incorrectly (see 7Q). Before we assume that, lets download the zip file at the bottom to test. To run the manual update, download the zip, and unzip the file to your desktop. Open the folder that was created, and run runme.bat. ( Note: depending on your security configurations on your PC, you may need to run the application with administrative rights. If you run runme.bat and the flash is failing, right click on "runme.bat" and click RUN AS ADMINISTRATOR). The file will display the current devices connected to your USB ports. One of them should say FTDI. For example, on my machine COM7 is the number of the FTDI device. (Note: if your maching doesn't show anything with 'FTDI', please move to 3Q) I would then enter "COM7" (without quotes, make sure that you dont just put the number, but but the word COM as well) and press Enter. The program will now try to update your RxDuino and will log all information to "batch.log". Please email this log to me.

http://www.normalexception.net/appli...nualUpdate.zip

If the update goes well, you can use this same process to update to the latest nightly. Please check FAQ 4Q.

2Q: Starting the console gives me a message about the application being in Beta, is this normal?
2A: Perfectly normal. The console will be in "Beta" until I can confirm that it is working on everyone's machine.

3Q: Using the Manual Update, I do not see any FTDI descriptions or, I do not see any COM ports at all even though the RxDuino is connected. What gives?!
3A: The cable that connects the RxDuino to the PC is called an FTDI cable. FTDI drivers are supposed to be included in later versions of Windows, but it seems that a few people aren't finding that to be the case with their systems. You can download these drivers from the following

http://www.ftdichip.com/Drivers/CDM/CDM20824_Setup.exe

These are Windows Certified drivers.

4Q: How do I use the nightly build?
4A: Click on the link above and you will be taken to the nightly build repository. Once you find the build you want to download, right and click "Save Link As..". Save the file into the same directory as the Manual Update files, and be sure to save it as RxDuino.hex. You will more than likely get a message that you are about to overwrite a file, you can accept as you are just overwriting the firmware that I shipped the Manual Updater with. Once that is done, you can now run "runme.bat" to update your RxDuino

5Q: What is the best way that we can have a chat session to resolve issues?
5A: A few members and I have already had a chat session and it was a fast and easy way to resolve issues! We were able to create a session on http://join.me and quickly connect to eachother. It allowed me to debug their issues and fix whatever problems they were having. If you would like to start up a chat session, just shoot me a PM and we can start a join.me session.

6Q: What are the best times to contact you?
6A: My goal is to be available as much as I can to get the first batch of users going while we iron out the random bugs and issues that are appearing. I try to be home by 4pm EST, so feel free to contact me via PM for chat sessions around those times. At work I also am lurking on the forums so feel free to ask question, just know that I won't be able to do any join.me sessions during work hours. My smartphone is also connected to my email, which gets PM notifications from the forums, so I will always get your messages one way or another.

7Q: How do I orient the FTDI cable?
7A: I will get images out asap and update the instructions, but the FTDI cable is inserted pin side down. You will notice that the FTDI cable has two sides, one being solid black, and one being solid black with some pins visible. There is no harm to the device should you insert incorrectly.

 

Awesome. I'll look into this when I get outta work today. Thanks Paimon.

 

So... I did all of these but still cannot get the console to do anything. The console opens but the page is blank. I try to choose an option or two and I get an error about running beta version. Sorry if I'm just doing something wrong. This technical computer stuff confuses me.

 

Moved this to the correct discussion area. I'll try to delete from the other one. Missed the new thread creation note.

I received mine today. I plugged into vehicle but nothing displays. I can see a red LED lit inside. (edit) I forgot to mention I have a completely unmolested 2011 RX8 Sport, no mods to anything, i.e. factory radio.

Took in the house, plugged into my PC, started console program, nothing displayed. I can see a red LED lit inside.

Took everything to car including laptop. All plugged in. Start console and see:
Parsing Message
GetGenericMessage::responsePid 12
GetGenericMessage::value3339
Parsing Message
... over and over

Nothing is displayed on the RX-8 display.

Type RST and submit into console, get the following intermingled with the earlier messages on the PC console:
Initializing...
Current Monitor Pid: 12
Byte Count 2
Current Monitor Text: RPM:
Current Mode Text: ECU Monitor
Display Text: Rotary Power
Customer Delay: 100
HSCAN Initialized
MSCAN Initialized
Printing Welcome Message
Parsing Message
GetGenericMessage::responsePid 12
...

I bring back into the house. Disconnect everything, take top off. Plug in USB. I see a bright red LED and a more dim green LED on inside. Start Console App. Get no messages.

Press Reset button in corner. Green LED flashes brightly then goes dim. On the console I now get:
Initializing...
Current Monitor Pid: 12
Byte Count: 2
Current Monitor Text: RPM:
Current Mode Text: ECU Monitor
Display Text: Rotary Power
Custom Delay: 100
HSCAN Initialized
MSCAN Initialized
Printing Welcome Message

Always shows above messages if reset button is pushed. I tried typing RST now and console message is also generated. I never get a version number as shown in the Console PDF even waiting many minutes.

I tried to update the firmware but it just flashes up a windows console screen very briefly and I can't see what occurs. Does not seem to update the device but I can't verify since the device does not send a version number on startup. The windows console flashes up way too quick to have done anything but probably error out. I have tried it on both my XP Pro (SP3) machine and my Win 7 laptop. If you can send the command line that the updater uses I can put it in manually to see the results.

Also, ran the DUMP command in the console, here are results:
Current Monitor Pid: 12
Byte Count: 2
Current Monitor Text: RPM:
Current Mode Text: ECU Monitor
Display Text: Rotary Power
Custom Delay: 100
Failures: 0

Failures will grow the longer it is on, assuming this is non communication to the vehicle OBDII. Also, I can use the NEXT command and see the DUMP results change to other items.

Let me know if you have any suggestions,

russ

 

Yea this was reported by amdhunter. I have resolved this and will be In the next firmware.

 

Russ, this sounds like the the firmware is in debug mode which is weird. Can you please download the new firmware , that should resolve the issue

 

Ah just realized you said it failed to update. I am not at home tonight but will send you the command line tomorrow to update and we will see if that helps

 

Note: To all, please keep this thread for "Technical Discussion for Rx-Duino Owners ONLY".

Non related banter will be removed by me.

If new Series 2 owners/others have questions related to a Rx-Duino purchase/inquiry please use the other threads that Paimon has given links to...or look in 'Group Buy' Sub Forum...or just PM Paimon.

Also, as said before, Paimon's Rx-Duino is only suitable for Series 2 (2009-2012) RX-8's at this stage.

 

Got mine today and I'm having a similar issue. Windows recognizes a USB plugged in, but nothing is available in the drop-down for the COM port. Refreshing, re-plugging in different ports won't get it detected by the software. It's on; I can see the red/green LED in the enclosure.

Also tried plugging it in to the car (GT 2011, stock radio), seeing the similar issue of the stock unit fighting with the RxDuino for display. Another thing I noticed is that the alarm LED on the tach flashes while the unit is plugged in.

 

Alright folks, sorry about my delay in responses, mini crisis at work yesterday. So what I would like to set up is a live chat so that I can help those who are having issues getting the console working like ZUnlimited, and Russ. I will set up a little chat system on my server and give you guys the link. I figure it will be faster if we can talk real-time. Sound ok?

 

Original post was updated with a tool to check to see if a manual update will work for users. This utility comes with Firmware 1.01. Please follow "1A" in the OP.

 

Just tried the tool - finds my device, but when I put the com port and press enter it flashes a command prompt and fails.

I am going to enable the user "administrator" on my machine and try it from that account, just to see if it's a permissions problem.

 

So I just connecteed to 'amdhunter' and was able to get him going. I apologize for not making my OP more clear, but please make sure to enter the com port on the manual flash utility as:

COM[the number]

For example:

COM2

or

COM7

etc.

 

I was able to update the firmware with the manual updater. I connect to the console and it now displays the version number (v1.0) on its boot up. It also continues to print attempts to display RPM on the console.

I connect it to my car and there is still no display. I have tried with the radio off and on. I will take out my laptop to see if it detects input from the cruise control buttons.

 

Update, with the laptop connected the RXDuino sees the input from the cruise control. I can see it change the output on my PC console display. Unfortunately it is not updating to the car display with the radio on or off.

I tried to use the 1.01 firmware update by taking the generated hex file and moving to the manual firmware updater. It installs it but the PC console still indicates it is version 1.0 when started or reset.

I will look for the chat program to send you a message. I'll also email you my update logs but the update did work so I don't know if it will tell you much.

 

When I did this all I got was:

Com1 - (Standard port types) - ACPI\PNP0501\1

Then it looks like your note in quotes.

This was the same with the RxDuino plugged into the usb and unplugged.

 

The console would print 1.0 as the version because it only has only one precision point. I will fix that so that it would have an extra precision point thus showing 1.0x. Have you tried it in the car since updating to 1.01?

amdhunter and I had great success with join.me . That may be a good tool that we can all use as it would give me a chance to not only watch your computer screen, but also can request control to guide you.

Very interesting, it looks like the FTDI drivers are not installed on your machine. What version of windows are you using? I believe that the FTDI drivers are standard on Windows 7 but maybe not. Nonetheless, you can download them from : http://www.ftdichip.com/Drivers/CDM/CDM20824_Setup.exe

I will be sure to include this in the next update for the RxDuino Console. I will also make note of this in the OP.

 

My XP (SP3) and Win 7 home premium machine found the FTDI drivers. The system works except for the console app firmware update and the display on the RX-8, the system is capturing the data and responding to the cruise control inputs.

I'm not seeing the "display fighting" that others see, it's a flat out loss on mine by the RxDuino. :-) No hint of display updates that I can see (in daylight). May be some flicker in the dark I can perceive and will try later tonight and give an update.

Everything is coming along as I expected so far. Dealing, not only with differences in cars and OEM equipment but also drastic differences in PC environments is not trivial. Paimon is doing GREAT. Thank goodness this isn't just a job for him but rather a personal favorite hobby!

russ

 

Russ, I just replied to your email. Could you check if you have a moment. Thanks!

 

Folks. I have updated the OP to show "nightly" builds. This build isn't a full version yet (i.e. the next version is 1.02, but think of this as between 1.01 and 1.02). This build though will have the fixes that are new in the bug tracker. For instance:

Nightly Build Update
- Incorporates fixes #7, #9, #10, #11 in bug tracker

Please right click and save the hex file, and use the manual updater to update the RxDuino

 

Can anyone take a picture of their duino?

I do not have an LED or reset button as mentioned in an earlier post.

"Press Reset button in corner. Green LED flashes brightly then goes dim. On the console I now get:"

Also - when editing the text "Rotary Power" every time I change it and plug it back in it defaults to Rotary Power. Any fixes?

 

The people that are reporting LEDs are reset buttons are either looking inside one of the 'holes' to see the leds, or opening the RxDuino box to access the reset button. The text should be saving, I will double check mine to see if that is no longer the case for some reason. Thanks for reporting that.

Edit: interesting, mine isn't retaining value either. Let me enter this into the bug tracker and try to fix that now.

 

Perhaps that is my problem then. I am running XP Home. Ill look into the link. Thanks.

Edit- Still no luck. The link was just a blank white screen. I think Ill try to start the process all over on the wife's laptop. She has windows 7

I don't know whats worse, My embarrassingly sparse lack of computer knowledge, Or you having to deal with me because of it. All this talk of coms, and drivers, and hex files is like Chinese to me. Sorry Paimon.

 

Just sent you my batch info after running the manual update. It's interesting in my cmd window it shows it as COM3 but in the batch log it says COM7.

Should I tell it to use COM7?

 

This issue is fixed, will be in version 1.02 but you can get this fix in the latest Nightly in the OP.