Troubleshooting Connection
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.
Troubleshooting Connection
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
Re: Troubleshooting Connection
- 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
Re: Troubleshooting Connection
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.
