hi all, yet another communicaion issue.
*V4, bought pre assembled
*being powered on the desk by a 12v power supply
*using a belkin USB/serial adapter, which has worked on the same laptop in conjunction with V3 software on my previous MJ instalation
*i have deleted phone synchronisation software from the laptop
*MJ will read the preinstalled map, but ONLY when the mj is powered, and the software is first opened.
*after that, i cannot write to the MJ, nor re-read from it. in each case i get the "timeout reading ignition cofiguration" message, or the "timeout writing ignition configuration" and then "timeout reading runtime data".
*both belkin adapter and MJ are set to use Com1
*i have verified that the hardware can communicate, using hyperterminal.
*MAP signal is working; as i dont have the installation finished, i cant say if the rpm signal is working.
so in a nutshell, the existing (preinstalled) map can only be read by the software when it first opens up. once open, i can neither read from, nor write to, the MJ.
any ideas, anyone?
regards
alexander.
V4 communications problem
Moderators: JeffC, rdoherty, stieg, brentp
hi brent, the belkin item is model F5U109.
this item worked successfully with the mj in my other car, using a V3 model MJ.
so, i know that it has worked on this laptop with another MJ.
i will add that i can see the RX and TX lights on the adapter doing their thing when the software if first opened.
when i try to read the existing configuration from the MJ, both TX and RX lights stop, implying that the belkin adapter has become frozen by that attempt. likewise if i try to upload a new map to the MJ.
regards
alexander.
this item worked successfully with the mj in my other car, using a V3 model MJ.
so, i know that it has worked on this laptop with another MJ.
i will add that i can see the RX and TX lights on the adapter doing their thing when the software if first opened.
when i try to read the existing configuration from the MJ, both TX and RX lights stop, implying that the belkin adapter has become frozen by that attempt. likewise if i try to upload a new map to the MJ.
regards
alexander.
What version of windows are you running? I have found the belkin adapters (or at least the drivers) are not the most stable.
V4 is running a different baud rate than V3 (38400 vs 4800); other than that, communications operate in the same way between controllers.
I would still recommend trying a different adapter- look for one based on a FTDI or prolific chipset. And of course, base-line functionality on a computer with an in-built serial port.
V4 is running a different baud rate than V3 (38400 vs 4800); other than that, communications operate in the same way between controllers.
I would still recommend trying a different adapter- look for one based on a FTDI or prolific chipset. And of course, base-line functionality on a computer with an in-built serial port.
i am using xp.
funnily enough, from memory, i thought i bought the belkin adapter because you said you use one!! in any case, i certainly solved the problems i had when setting up the V3 MJ in my other car.
i thought the prolific chip was the one to be avoided?, but perhaps i am confused from not having read through all that stuff recently.
if noone comes up with some genuius inspiraiton today, i might try a PCMCIA serial card.
regards
alexander.
funnily enough, from memory, i thought i bought the belkin adapter because you said you use one!! in any case, i certainly solved the problems i had when setting up the V3 MJ in my other car.
i thought the prolific chip was the one to be avoided?, but perhaps i am confused from not having read through all that stuff recently.
if noone comes up with some genuius inspiraiton today, i might try a PCMCIA serial card.
regards
alexander.
USB-Serial adapters have been the bane of my existence. Someday I will have a big bonfire with all of the adapters I've tested- I'll post it on youtube.
In any case, I'm glad you have it working. I do recall having instability issues with the Belkin drivers. For me, I was getting BSOD's within a few minutes of using the adapter!
In any case, I'm glad you have it working. I do recall having instability issues with the Belkin drivers. For me, I was getting BSOD's within a few minutes of using the adapter!
Bringing this back up from the dead BUT.
I have found a "fix" for the belkin adaptors. I found that there are two adaptors out there and that Belkin is pointing you to there most recent driver. Unfortunately this driver is not signed and makes XP take a hissy fit. I hunted the far reaches of the inter-web using my best "Google Fu" and found the older driver that actually matches my adaptor exactly and it is XP signed as well.
The adaptor #s are
F5U109 and F5U409
The 109 is the newer of the two.
Belkin wants you to use the 109 driver. But this driver is not signed and made my laptop that runs XP pro barf. When I got it loaded all kinds of weirdness with the adaptor started to occur. So I uninstalled it and installed the 409 driver (my unit is a F5U409). Now all is right with the world of XP and belkin. I have attached both drivers in the attached zip file since the 409 driver was a bit hard to find and belkin seems to to want us to use it.
It would be interesting to see if the 409 driver works with a 109 unit.
Anyway just passing along what I have learned tonight.
I have found a "fix" for the belkin adaptors. I found that there are two adaptors out there and that Belkin is pointing you to there most recent driver. Unfortunately this driver is not signed and makes XP take a hissy fit. I hunted the far reaches of the inter-web using my best "Google Fu" and found the older driver that actually matches my adaptor exactly and it is XP signed as well.
The adaptor #s are
F5U109 and F5U409
The 109 is the newer of the two.
Belkin wants you to use the 109 driver. But this driver is not signed and made my laptop that runs XP pro barf. When I got it loaded all kinds of weirdness with the adaptor started to occur. So I uninstalled it and installed the 409 driver (my unit is a F5U409). Now all is right with the world of XP and belkin. I have attached both drivers in the attached zip file since the 409 driver was a bit hard to find and belkin seems to to want us to use it.
It would be interesting to see if the 409 driver works with a 109 unit.
Anyway just passing along what I have learned tonight.
- Attachments
-
- F5UBELKIN_DRIVERS.zip
- (105.71 KiB) Downloaded 510 times
Respectfully
Dean
Dean