Troubleshooting Connection

Forum for discussing how to install MicroSquirt(TM), choose and troubleshoot sensors, wiring, and communications for MicroSquirt (TM) and MicroSquirt Module(TM).
Forum rules
Read the manual to see if your question is answered there before posting. If you have questions about MS1/Extra or MS2/Extra or other non-B&G code configuration or tuning, please post them at http://www.msextra.com The full forum rules are here: Forum Rules, be sure to read them all regularly.
Post Reply
uofu_fsae
MegaSquirt Newbie
Posts: 13
Joined: Mon Aug 30, 2010 7:17 pm

Troubleshooting Connection

Post by uofu_fsae »

Alright, so at this point I feel like we've tried everything. We had problems getting the microS to connect and start talking with the computer however after hours of research and settings tampering it "magically" started communicating. While setting up our parameters it stopped communicating. Cant get it to communicate again. I've read every help and forum I could find and tried what they've said. The computer recognizes the serial. Does anyone have any suggestion on what to try in order to get the microS and computer talking to each other. seems to me we should at least be connecting. We'd sure appreciate any advice we can get. Thanks!

1.) The board is powered with 12V
2.) Megatune is downloaded, latest version 2.25 p3
3.) If I open megatune and open the communications menu and select the appropriate comm port it will not connect(done at 115200)
4.)If I use port checker it will give me three ports available
5.) I have the port # correct for the USB-serial cable and straight serial, and have
tried all the ports
6.) Ive fiddled with all sorts of settings trying to establish a connection.
7.) device manager shows the serial is connected when its in each available COMM
8.) tried a USB adapter and the onboard serial.(we first had it connected with serial, havent been able to get it to connect with the prolific USB-serial)
9.) Ive checked the connections at both ends and they are tight.

our microsquirt is running a Honda 600 F3 rigged with fuel injection. (does anyone know of any maps similar to this to get us eventually started on the tuning process?)
Matt Cramer
Super Squirter
Posts: 910
Joined: Sat Jul 03, 2004 11:35 am

Re: Troubleshooting Connection

Post by Matt Cramer »

Please post a screen shot of the results you get from the port check.
Matt Cramer at DIY Autotune
Image
uofu_fsae
MegaSquirt Newbie
Posts: 13
Joined: Mon Aug 30, 2010 7:17 pm

Re: Troubleshooting Connection

Post by uofu_fsae »

We have attached a screen shot of the port checker it wouldn't let us just copy the text.
Attachments
portcheckerscreenshot.rtf
screen shot of port checker.
(787.13 KiB) Downloaded 60 times
Matt Cramer
Super Squirter
Posts: 910
Joined: Sat Jul 03, 2004 11:35 am

Re: Troubleshooting Connection

Post by Matt Cramer »

Ok, at this point, I'd try reloading firmware. What results do you get if you try that?
Matt Cramer at DIY Autotune
Image
uofu_fsae
MegaSquirt Newbie
Posts: 13
Joined: Mon Aug 30, 2010 7:17 pm

Re: Troubleshooting Connection

Post by uofu_fsae »

Thanks for your replies. We downloaded the latest .ini files (3.4.3) as well as the .s19 file to go with it. Using the MS-II download program we seemed to be successful in updating the firmware on the MicroSquirt. It now comes up in the port checker under the appropriate baud rate. However, we get a bunch of errors when starting up MegaTune 2.25.

WARNING:MegaSquirt-II.ini:0084-Unexpected or unsupported token "[Reference Tables]"
WARNING:MegaSquirt-II.ini:0086-Unexpected or unsupported token "[tableWriteCommand]"

There are at least 10 other similar errors as well as
WARNING:-Submenu entry references dialog id 'mafTableBurner,' which cannot be found.

We can click through all the errors and eventually we get to MegaTune and it seems to communicate. We are currently troubleshooting this error. Please advise further if possible.
grippo
MegaSquirt Guru
Posts: 921
Joined: Mon Feb 16, 2004 6:55 pm

Re: Troubleshooting Connection

Post by grippo »

By loading the the latest 3.430 code you can't run this on MT, only TunerStudio. At this point there is nothing to be gained by this - reload 2.890 or 2.891 code with MT and get your connection problem solved. Most of the changes in the new code are for the upcoming sequencer and for operation with CAN GPIO devices.
Post Reply