MicroSquirt.com read only forum (Jan.15,2018)

Hello , ive been jammed with this non communication for the last 10 hours and its getting me crazy !

i installed this brand new Microsquirt module, has 14V and grounds on the goood pins.

i installed my Prolific usb to rs232 drivers to the computer running Win7

i did specify the usb controller to run on com1 with the 115200 baud rate

i went into the mini terminal in Tuner Studio MS and shorted pins 2 and 3 and the loopback was successfull

but when i try to scan the ports with TS it just finds nothing....

when i go in communicatin settings and i "Test port" com1 and others it says the test fails... loopback works but the port test fails?


i was wondering maybe my cable is "crap" but i did use it with a previous megasquirt project but it was from a different computer...

i read somewhere that using a laptop plugged into the AC wall outlet could send a voltage into the usb port and fuss up with the usb rs232 controller but i cant be sure about it and test it because my laptop has a blown battery , does not work if n ot plugged in


im running out of ideas! maybe a newer cable would work but its a long wait to get delivered or its like 40$ locally.. anyone could help?

Thanks

Oliver

i went ahead and got a IOGEAR adapter , wich does nothing more... still echoes back what i write in the terminal but no connection , is there something i am missing out?

i tried to download the latest code to the ECU with the downloader and specified the port and baud rate and it told me this. tried a few different com ports

Detected MS-II (HCS12) code.
Entry point: 0xc000
Code range : 0x4000-0x3dbc40
File read successfully.

Opened comm port 5 at 115200.
ERROR: Timed out reading response, 0xE0
Elapsed time: 15.15 seconds

Hi peoplecanfly,

I've had this same problem, and got an RMA on a board. I've also just kept trying wiggling the connectors and eventually got lucky too.
However, you sometimes get this if the MicroSquirt isn't powered up, and if the 2.5mm jack plug has poor connections.
Another thing to look for is the Ampseal connections in the plug can be dodgy... as in this thread (solution at end)

Good luck
Mike

Woah how did you managed to check that!? You probed the header directly on the board? For sure i will check for loosesess in this area !!

One thing i noticed is that the ecu gets slightly warm to the touch after a few minutes turned on , tells me there power going to it, the pins going to the communication jack might be loose. I could just nudge them a little with a sharp pick if i dont have the tools to pull out the pins.

Hi peoplecanfly,
Not the header on the board, it's the 2.5mm jack plug, which you can unscrew the cover, and sometimes the wires get fatigued by all the flexing on the cable. The other bit was the Ampseal plug (or connector on the loom end, as sometimes the pins can be pushed back and make poor connections. I've heard folks mention crimping them slightly, but I've only had a couple of duff pins on the VR2 circuit. They have tangs that stop them moving back in the plug, but mine were distorted and not working.

One thing i noticed is that the ecu gets slightly warm to the touch after a few minutes turned on

Now that doesn't sound good at all, the ECU only uses small amounts of current, I don't think it should be getting warm at all. The voltage regulator to the 5V supply might, or your injector transistors might, but I don't think anything else should...anybody else seen this?

Mike

i dont have fuses yet on the coils and injector banks and i didnt asked the engine to turn yet so nothing is supposed to draw much power , just trying to get the communication right first. the fuel pump does not cycle when i turn the power ON (i back probed the power pin on the ECU and i have my 12V) , im not sure if its pre coded to cycle from the factory... gonna check the pins tomorrow its very late low hah

my IOGEAR cable adapter has a yellow LED on it but i never saw it light up is that normal?

Solved but at some good expense i didnt needed to spend ... 5 weeks off of my project waiting for the perfectly functioning controller to go back and forth to warranty, 2 usb adapters , a new old refurbished laptop to rule out the drivers and adapters possible issues...

Turned out the 2.5mm female communication jack was shorting the comms to ground internally... First time in my life i find a defect audio jack ... Replaced it , communication successfull .... Well ... Brand new pre made harness , you dont think about checking this in particular , troubleshooting pointed the controller .

well now it works but im having troubles getting my tach signal... VR isnt able to see all 36 teeth of my trigger , gonna try another sensor , teeth are very small on the 2.5" 36-1 trigger .

Setbacks , lots of them !!!