ts now constantly dropping com connection.

[weeblebiker]

started dropping connection when I upgraded firmware to the last stable release and upgraded ts and started running cops. tried 2 different laptops, swapped the old prolific pl2303 adapter to a 3ft length shielded FTDI adapter, still dropping connection. happens randomly when running. doesn't appear to happen with the engine off.
I haven't been able to get a data log yet.
my first suspicion is I have noise induced drop out either in the box directly with the comm ic or a firmware /software issue.
once I get the grayed screen and not connected message, testing port always fails.
still fails if I disconnect the usb and re connect and try to test port.
it comes back up and connects once I shut ts down and restart it. will reconnect without disconnecting the usb while the engine is running.


any way to look at the the usb communications line and see whats going on??

[LT401Vette]

Have you tried running D2XX or JSSC drivers under the USB And Wireless menu?

I don't know if that will fix it, but worth a shot.

After that I may need a Comm Debug log.

[weeblebiker]

where is comm debug log?

[LT401Vette]

It is the regular TunerStudioAppDebut.txt but captured while Comm Debug is turned on under the Communications menu..

[weeblebiker]

Driver is Usb and Wireless
connection type FTDI-D2XX driver
Device serial # is Auto
Baud rate 115200

Data Rate is bulleted as 15 reads per second

found the Debug Log Comm checkbox. I have it checked now
Ill run it next time

Thanks

[LT401Vette]

Also give JSSC a try.

[weeblebiker]

sorry for the delay, left the tuning laptop at work.
I went out at lunch and got a drop out with the debug log comm box checked, where do I find the debug .txt file?
and how would be best to get it to you?
Thanks!

my suspicion is its noise from the tc4427 drivers above the com ic

[LT401Vette]

and started running cops.

That piece from the original post just caught my attention. This would most likely be related to the problem.

So I would tend to agree with:

my suspicion is its noise from the tc4427 drivers above the com ic

The TunerStudioAppDebug.txt would be in the TunerStudioProjects folder.

[weeblebiker]

debug file 2288 kb. can I email it to you or clip it down ?

I've been having this random pfft noise I thought was a valve sticking open and have black exhaust residue back up the intake runners aon #2 and #3 cylinders. just changed the long block and still doing it.

now I wonder if if it's the vag coils cross talking and igniting when the intake valves are open.

Thanks!

[LT401Vette]

Sure.
Send it to support at efiAnalytics. Com

[LT401Vette]

I did get the AppDebug log, but there was no Comm Debug info in it.

It does show it trying to connect repeatedly but is not finding any FTDI devices connected.

[prof315]

I've been having this random pfft noise I thought was a valve sticking open and have black exhaust residue back up the intake runners aon #2 and #3 cylinders. just changed the long block and still doing it.

now I wonder if if it's the vag coils cross talking and igniting when the intake valves are open.

Thanks!

Given that VAG coils seem to vary so much in how they operate vs. revision #, I would say that's a real possibility. There's also the possibility that you have exceeded the limits of the V2.2 board's ability to maintain clean signals, it's not nearly as robust as a v3.0/v3.57 board and you are truly pushing yours to the max with all of the features you are using.

[weeblebiker]

so comparing my ts com settings to my usb adapter double checked I have an FTDI chip set selected and thats whats showing up in windows
I have a baud rate in ts of 115200
I have a pits per second rate on the com port setting of 9600

should they be the same??
would this cause the drops?
what should the rates be with the FTDI chip set?

the data logs look clean accept for a random dropout of the mat sensor and corresponding little jump in the injector pw. dunno whats causing the mat dropout

I made a Mylar sheathed copper foil ground plane and placed between the ICs. I may go back in and run the jbperf driver board ground all the way back by the main connector. or put a decoupling cap across the com ic

besides the annoying com drop out, the main concern is the random pfft noise. ruled out the long block by swapping it. pretty sure its not the bov, by swapping from an 8 lb spring to a 5 lb. the current theory is ignition with the intake valves open.

[weeblebiker]

just traced where i'm pulling vcc for the jbperf driver board.
u6 comm ic is between the jbperf board and vcc.

what do ya'll think about putting a 0.1uf decoupling cap across u6 pos and neg and something like a 1 or 10uf cap across the entire jbperf board pos and neg? maybe a 10 ohm resistor inline between ground and the decoupling cap and ic for each also?

part of the fun is making this box work with all the mods. learning how to overcome bad circuit design(not this design) is why I'm doing this project like this.

once I get this running well, I'll probably just jump to ms3

[LT401Vette]

I have a baud rate in ts of 115200
I have a pits per second rate on the com port setting of 9600

should they be the same??
would this cause the drops?
what should the rates be with the FTDI chip set?

The baud in the windows port setting doesn't matter, it is just the default baud for that port. TS sets the baud on the port to what you have set in TS.
The drops on your MAT look like a wiring issue, not a communications problem. It is what the ECU is seeing, hence the reaction in pw.

[weeblebiker]

I'll check the mat sensor. last time I disconnected it I noticed the connector plug was wiggly.

going to put in a 10uf decoupling cap on u6 and a 10 ohm resistor between vcc and the tc4427 gates and gate decoupling caps.

[weeblebiker]

so ran a 10uf and a 0.1uf caps across u6 and the 10 ohm resister on the jbperf board pos. drove and only had 1 dropout in 30 minutes. not sure if it was my laptop trying to go to sleep.

will test tomorrow with a charger hooked up and laptop to never shut down

[weeblebiker]

it's still dropping connection.
TS goes offline while the car is running
when I go to communications and click settings I get a hour glass only over the communications index drop down menu, the mouse arrow re appears across the rest of the screen and the computer works otherwise and I can close TS by clicking the red X. but stays an hour glass over the pop up.
the usb port is still showing in the microsoft hardware manager
until I unplug the usb, then communications settings pop up window appears.
when I plug the usb back in the computer, sometimes ts will reconnect when I test the connection, sometimes ts wont.

however it seems to be happening randomly less often.
maybe a set of decoupling capacitors on the db9 connector?

I am running wasted cop, meaning if it is noise induced by the coils or drivers, I can half the instances of noise generation by getting off my duff and phasing my cam signal correctly B#1TDC instead of a#1tdc

[weeblebiker]

apparently the metal braiding in the clear jacket of the adapter cable is not connected so the cable is not shielded. i assumed it was

while running if I move a loop of the serial/usb adapter cable next to the laptop power supply transformer ts disconnects every time.
but only while the engine is running and somewhere above idle.

it does re connect by unplugging and plugging in the usb if the wire is not near the power supply.

so
my theory is switching to cop instead of wasted cop and getting a adapter that states it is shielded instead of just a pretty jacket should take care of the issues.

[weeblebiker]

switching to sequential ignition did not help. a