New here, comm error from dead board? (can't access MSQ)
Moderators: jsmcortina, muythaibxr
New here, comm error from dead board? (can't access MSQ)
Hi, I'm installing Microsquirt on my Mercedes 190E. I bought this setup from a friend who decided to go another direction with his car but had it running before I bought the system. Unfortunately, he didn't do the best job with documentation and he lives across the country so I've had issues figuring out how to get everything set up. I spent a week deciphering the wiring he did then another few days sorting out his power-on circuit. Now, I am trying to set up the microsquirt controller with my computer but I'm having issues. I am somewhat afraid I could have fried the board while doing all of my testing so I need to figure that out now.
I was using a UGreen RS232 Serial to USB cable with the Prolific chipset and was only able to communicate with the board one time out of about 20 attempts and could not replicate it. I then found a friend with an XP computer and was able to have a bit more success. It would consistently give me this error message:
When using Miniterminal, entering "S" would give me "{" or something similar. If I understand the manual correctly, I should get the firmware version from typing "S"?
So I'm perplexed as to what the issue is. I am hoping to rule out that the board is bad. I do think that my USB converter doesn't work properly, though I'm not 100% sure I've set that up correctly. I just had it coming from pins that come straight off the board to a serial board I could secure the wires to then used the USB adapter.
Sorry for not attaching the MSQ, I haven't gotten that far yet.
I was using a UGreen RS232 Serial to USB cable with the Prolific chipset and was only able to communicate with the board one time out of about 20 attempts and could not replicate it. I then found a friend with an XP computer and was able to have a bit more success. It would consistently give me this error message:
When using Miniterminal, entering "S" would give me "{" or something similar. If I understand the manual correctly, I should get the firmware version from typing "S"?
So I'm perplexed as to what the issue is. I am hoping to rule out that the board is bad. I do think that my USB converter doesn't work properly, though I'm not 100% sure I've set that up correctly. I just had it coming from pins that come straight off the board to a serial board I could secure the wires to then used the USB adapter.
Sorry for not attaching the MSQ, I haven't gotten that far yet.
Re: New here, comm error from dead board? (can't access MSQ
Prolific adapters are not recommended because of exactly the issues you are having.M103EFI wrote:...I was using a UGreen RS232 Serial to USB cable with the Prolific chipset and was only able to communicate with the board one time out of about 20 attempts and could not replicate it....
You want the FTD adapter.
1988 Mustang GT, 59k miles, Orig Owner
ProCharger 600B I/C, 12psi, FRP Hdrs, Flwmstr F2, 3G Alt, Contour Fan & DCC, 3.55's, Prog Sprg, Subfms, UCA, LCA, FCA, Tokico 5's, Bridgestone RE-71R 245/40R17, Crane HI-6, Kirban FPR, MS2, DIYPNPF60, Spartan 2, C&L76mm blo-thru MAF, 47lb FRP-LU47
ProCharger 600B I/C, 12psi, FRP Hdrs, Flwmstr F2, 3G Alt, Contour Fan & DCC, 3.55's, Prog Sprg, Subfms, UCA, LCA, FCA, Tokico 5's, Bridgestone RE-71R 245/40R17, Crane HI-6, Kirban FPR, MS2, DIYPNPF60, Spartan 2, C&L76mm blo-thru MAF, 47lb FRP-LU47
Re: New here, comm error from dead board? (can't access MSQ
This MicroSquirt?
Correctly identify your MS ecu here
Read the Do's and Don'ts to avoid the common pitfalls before starting your install or asking for help
Use only these manuals other manuals may cause brain damage or worse.
Read the Do's and Don'ts to avoid the common pitfalls before starting your install or asking for help
Use only these manuals other manuals may cause brain damage or worse.
-
- Site Admin
- Posts: 39614
- Joined: Mon May 03, 2004 1:34 am
- Location: Birmingham, UK
- Contact:
Re: New here, comm error from dead board? (can't access MSQ
I've tested one USB-serial adapter that clearly did not comply with RS232, lazy designers had used the wrong voltages. It didn't work with the Microsquirt.
James
James
I can repair or upgrade Megasquirts in UK. http://www.jamesmurrayengineering.co.uk
My Success story: http://www.msextra.com/forums/viewtopic ... 04&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
New users, please read the "Forum Help Page".
My Success story: http://www.msextra.com/forums/viewtopic ... 04&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
New users, please read the "Forum Help Page".
Re: New here, comm error from dead board? (can't access MSQ
Might have been a counterfeit serial chip, they don't support all of the protocol.
Correctly identify your MS ecu here
Read the Do's and Don'ts to avoid the common pitfalls before starting your install or asking for help
Use only these manuals other manuals may cause brain damage or worse.
Read the Do's and Don'ts to avoid the common pitfalls before starting your install or asking for help
Use only these manuals other manuals may cause brain damage or worse.
-
- Super MS/Extra'er
- Posts: 9130
- Joined: Sun May 02, 2004 6:51 am
- Location: Quebec, Canada
- Contact:
Re: New here, comm error from dead board? (can't access MSQ
I have posted this before: all the cheap chinese USB-serial adapters based on the CH340 chipset will not work with the Microsquirt (cased or module). This is not a one-off thing. And almost all the very cheap adapter are based on that chipset. If the chipset is not mentioned, stay clear as it's likely that one.rickb794 wrote:Might have been a counterfeit serial chip, they don't support all of the protocol.
Jean
Re: New here, comm error from dead board? (can't access MSQ
Sorry, should have mentioned, it's V2.2 stuffed into the original ECU case.rickb794 wrote:This MicroSquirt?
I'm going to order a FTDI cable to see if that changes anything. Pretty sure my other cord was legitimate Prolific but when I ordered it, I didn't know that there could be an issue using that chipset.
I've borrowed an XP machine with a serial port coming off the motherboard, is there something I need to do to correct the error code I was getting?