V3 system (silver), 3.2.1 controller, windows 2000 pro
the UBS driver shows in device manager under COM section as COM PORT5. I've configured MJ to read COM5 in options. i followed the instructions on loading a new USB driver and after a few attempts, it worked fine and shows up under "add/remove programs"
I've done all the voltage tests and they were very very close (4.84v). does that matter they were not 5v?
This is what has me confused:
Everything is fine(passwed voltage test, controller installed and configured, USB to Serial adaptor installed) and when i plug in the serial side of the USB cable into the MJ v3 unit, the line item under COM section in device manager goes away.
"cannot open port"
I'm a software guy, so this whole hardware piece is new to me.
Any help would be greatly appreciated. I can take pictures, measure anything needed.
Timeout reading runtime data (was: USB to laptop problem)
Moderators: JeffC, rdoherty, stieg, brentp
Timeout reading runtime data (was: USB to laptop problem)
Last edited by paulc on Thu Jul 17, 2008 9:15 pm, edited 1 time in total.
Hi Paul,
I suppose the obligatory questions are in order:
- Does the USB-Serial Adapter work with other serial devices?
- Does the MJLJ work on a different computer, hopefully one with a standard serial port?
Is this a fresh kit build, or has the unit been otherwise running for some time now?
Thanks,
I suppose the obligatory questions are in order:
- Does the USB-Serial Adapter work with other serial devices?
- Does the MJLJ work on a different computer, hopefully one with a standard serial port?
Is this a fresh kit build, or has the unit been otherwise running for some time now?
Thanks,
thanks Brent,
the kit has never been run (built it last winter)
i do not know if the system runs on another computer as i do not have a serial to serial cable. I also am not sure if the serial cabole works with other devices. What other devices would use serial?
I just looked at my laptop and it's an old dell latitude, and it has a serial out on it.
would i save myself a headache and get a serial to serial cable? what about just a plug in adaptor from USB to serial (so i can use my existing cable?
the kit has never been run (built it last winter)
i do not know if the system runs on another computer as i do not have a serial to serial cable. I also am not sure if the serial cabole works with other devices. What other devices would use serial?
I just looked at my laptop and it's an old dell latitude, and it has a serial out on it.
would i save myself a headache and get a serial to serial cable? what about just a plug in adaptor from USB to serial (so i can use my existing cable?
If you just plug in the Serial to USB cable into the computer does anything come up now? After playing with drivers etc? In device manager under com ports, etc it should appear at some stage and indicate which port its running on
Then in the MJ software you need to make sure its running on the same port.
The USB -> Serial may have taken on a new COM port after drivers were touched...
Can you confirm that the ports match up?
If you have a laptop with serial to serial use that, much better imho... Serial to Serial cables are really really cheap now...
Cheers
Peter
Then in the MJ software you need to make sure its running on the same port.
The USB -> Serial may have taken on a new COM port after drivers were touched...
Can you confirm that the ports match up?
If you have a laptop with serial to serial use that, much better imho... Serial to Serial cables are really really cheap now...
Cheers
Peter
yes, the com port associated with the new driver/com port is 5. MJ unit is set to 5 as well.
when i plug in the cable when it is not attached to the unit, it shows up in device manager and recognizes it.
when i plug in cable (serial end) to the MJ unit, it is removed from the device manager view (under the COM ports. ?? is it supposed to?
i might just go and pick up a serial <-> serial cable. kind of a shame as i have already run the USB<->serial cable with my wiring harness.
any other ideas?
when i plug in the cable when it is not attached to the unit, it shows up in device manager and recognizes it.
when i plug in cable (serial end) to the MJ unit, it is removed from the device manager view (under the COM ports. ?? is it supposed to?
i might just go and pick up a serial <-> serial cable. kind of a shame as i have already run the USB<->serial cable with my wiring harness.
any other ideas?
It shouldnt dissapear from the Device Manager.
What USB -> Serial is it? What drivers does it use?
Have you got the baud rate, etc etc set correctly?
If you plug in the MJ into the USB, etc... with the MJ powered down (off) and then open up the MJ software, then turn on the MJ (ignition, etc but not engine) same thing happens? What if the engine is running?
Its interesting that it disappears.
If you get the serial to serial, thats a good test, if you cant then I guess.... You need to keep troubleshooting.
Peter.
What USB -> Serial is it? What drivers does it use?
Have you got the baud rate, etc etc set correctly?
If you plug in the MJ into the USB, etc... with the MJ powered down (off) and then open up the MJ software, then turn on the MJ (ignition, etc but not engine) same thing happens? What if the engine is running?
Its interesting that it disappears.
If you get the serial to serial, thats a good test, if you cant then I guess.... You need to keep troubleshooting.
Peter.
i tested the serial cable. Got past the port issue (COM1), but it now says Timeout reading runtime data
http://www.autosportlabs.net/MJLJ_V3_Operation_Guide
what next? Brent?
http://www.autosportlabs.net/MJLJ_V3_Operation_Guide
i check the MJ unit and it is getting switched 12v power. This seemed to be the only troubleshooting suggestion in the V3 operation guide.Timeout reading runtime data
The Configuration Software did not get a response from the MJLJ on the serial port you specified.
* Does the MJLJ have power, and connected to the computer with a standard serial cable or compatible USB-Serial adapter?
what next? Brent?
wanted to follow-up here as i started to PM/email with Brent and solved the problem (i think)
after going through a series of voltage tests it was decided to swap to a serial to serial cable instead of the usb to serial cable that required a driver.
So, the port got opened after switching to the serial cable - great - one problem solved.
Still getting the "Timeout reading runtime data". So, Brent asked that i snap some high resolution pictures of the solder joints. long storey short, i redid every single solder connection after wathcing this solid video:
http://www.curiousinventor.com/guides/How_To_Solder
Also did an upgrade from 3.0 to 3.2.1 (flashing the chip) and installing the right version of the controller app.
The online steps in the "HOW TO" are excellent, and all i needed.
turned out one of the joints was not very good. Cleaned them all up nicely and tested and it worked.
Now - to put wheels on the car.
after going through a series of voltage tests it was decided to swap to a serial to serial cable instead of the usb to serial cable that required a driver.
So, the port got opened after switching to the serial cable - great - one problem solved.
Still getting the "Timeout reading runtime data". So, Brent asked that i snap some high resolution pictures of the solder joints. long storey short, i redid every single solder connection after wathcing this solid video:
http://www.curiousinventor.com/guides/How_To_Solder
Also did an upgrade from 3.0 to 3.2.1 (flashing the chip) and installing the right version of the controller app.
The online steps in the "HOW TO" are excellent, and all i needed.
turned out one of the joints was not very good. Cleaned them all up nicely and tested and it worked.
Now - to put wheels on the car.
Glad you got it working, Paul.
In your case one or more of the oscillator related solder joints was not making a good connection.
The bootloader firmware on the chip (which helps load new firmware) is not dependent upon the oscillator- so when Paul was able to write firmware but not communicate with the configuration software, that was the smoking gun!
In your case one or more of the oscillator related solder joints was not making a good connection.
The bootloader firmware on the chip (which helps load new firmware) is not dependent upon the oscillator- so when Paul was able to write firmware but not communicate with the configuration software, that was the smoking gun!