still cant connect,

[enohand]

i dont know what the issue is, but i cannot connect with either of the latest versions...no more errors about no USB drivers, but i have the port set to auto & my cable/serial to usb adapter is using com 3, i see nistune tries to connect to it, but never does.

I have no problem loading ecu talk or the calumsault GUI, but nistune wont connect......are there any logs i can post to try to figure this out.?

i haven't been able to connect to it for quite some time now...its getting annoying`

[Matt]

File-Configuration-Debug logging

Enable this and then restart, try the connect and let me know

Also COM3 is normally the laptop imbuillt modem. What port is your consult cable reporting to device manager?

[enohand]

File-Configuration-Debug logging

Enable this and then restart, try the connect and let me know

Also COM3 is normally the laptop imbuillt modem. What port is your consult cable reporting to device manager?

no modem in the laptop, its been removed...

Device manager shows com3, i can change it if you rather have me do that



ill do a debug log & post it

[Matt]

okay thats fine. COM3 is the port found for consult then which is half good

why its not connecting, will need the log now to determine the reason

[enohand]

hey matt here is the log


NISTUNE LOG Jul 25 2010 23:55 0.9.14.10b
21:53:32.206 CNistuneDoc - usb disconnected
21:53:32.222 CImageSelPanelView
21:53:32.222 ConsultMain()
21:53:32.222 CConsultSM::CConsultSM
21:53:32.222 SetConsultMode(): From 14 to 0
21:53:32.222 CImageSelPanelView
21:53:32.222 CRomulatorSM::CRomulatorSM()
21:53:32.222 RomulatorMain()
21:53:32.222 ProcessRomualtorQueue(0) - Entering thread
21:53:32.222 TriggerRomulatorEventTask(1) - Entering thread
21:53:32.222 CImageSelPanelView
21:53:32.222 CRomulatorSM::CRomulatorSM()
21:53:32.222 RomulatorMain()
21:53:32.222 ProcessRomualtorQueue(0) - Entering thread
21:53:32.222 TriggerRomulatorEventTask(2) - Entering thread
21:53:32.222 CImageSelPanelView
21:53:32.222 USBMain
21:53:32.222 InitialiseRegisters
21:53:32.222 CNIStuneDoc(): Zeroising target AFR table
21:53:32.222 CNIStuneDoc(): Initilising sensor record table
21:53:32.238 CNIStuneDoc(): Initilising RPM AFR trace table
21:53:32.238 CNIStuneDoc(): Initilising consult
21:53:32.238 ConsultGetActiveSelections()
21:53:32.238 Unable to load afr1.csv lookup table - empty file
21:53:32.238 Unable to load afr2.csv lookup table - empty file
21:53:32.238 Unable to load aux1.csv lookup table - empty file
21:53:32.238 Unable to load aux2.csv lookup table - empty file
21:53:32.238 Unable to load aux3.csv lookup table - empty file
21:53:32.238 Unable to load aux4.csv lookup table - empty file
21:53:32.238 Unable to load aux5.csv lookup table - empty file
21:53:32.238 Unable to load aux6.csv lookup table - empty file
21:53:32.238 CImageSelPanelView
21:53:32.253 CImageSelPanelView::OnInitialUpdate
21:53:32.253 About to create MTS controls...
21:53:32.253 MTS Control OCX creation successful within this view
21:53:32.253 UpdateAllCombinationLists()
21:53:34.624 finished
21:53:34.624 ~CParser
21:53:34.624 Opening B14_SR20DE_512_E_95.adr
21:53:34.624 ~CParser
21:53:34.624 NTLOOKUPID is 71
21:53:34.624 ConsultGetActiveSelections()
21:53:34.624 ~CParser
21:53:37.214 ConsultGetActiveSelections()
21:53:37.214 AutoFindConsult
21:53:37.214 AutoFindConsult(): Attempting connection
21:53:37.406 COM3 found
21:53:37.406 statusbar: AttemptConnect(): Connecting to COM3 attempt 1
21:53:37.406 ConsultSM(): Connect(): Consult: Connecting to COM3
21:53:37.551 ConsultSM(): Connect(): GetCommState
21:53:37.551 ConsultSM(): Connect(): SetCommState
21:53:37.551 ConsultSM(): Connect(): SetCommMask
21:53:37.551 ConsultSM(): Connect(): SetupComm
21:53:37.551 ConsultSM(): Connect(): SetCommTimeouts
21:53:37.551 ConsultSM::Connect() - Initialised. Starting ConsultSerialLoop thread
21:53:37.551 SetConsultState(): From 1 to 1
21:53:37.551 SetConsultMode(): From 0 to 0
21:53:37.551 SetupPollCheck(): Send stop stream byte
21:53:37.551 TerminateStream() - Stopping previous stream
21:53:37.551 TX:30
21:53:37.551 ConsultSerialReadLoop() start
21:53:37.551 ConsultSerialReadLoop() - Entering thread
21:53:37.551 ConsultSerialReadLoop(): state=1, read=0, status=0
21:53:37.566 sendBufferArray: 1 bytes sent
21:53:37.596 SetupPollCheck(): Clearing RX buffer
21:53:37.596 DumpData() - bytes dumped = 0
21:53:37.596 DumpData() - byte dump completed
21:53:37.596 OnSelConsultInitialise(): Queueing CONSULT_EVENT_INITIALISE
21:53:37.596 QueueEvent: Added 0
21:53:37.651 ConsultSerialReadLoop...
21:53:37.651 ConsultSerialReadLoop(): state=1, read=0, status=0
21:53:37.651 ConsultSerialReadLoop(): Consult queue: 1 deep
21:53:37.651 GetQueuedEvent: Event 0 Index 0
21:53:37.651 ConsultSerialReadLoop(): Queue 0 (P1=0000, P2=0000, P3=17D48B0)
21:53:37.651 ConsultSerialReadLoop() - Reset IDLE event
21:53:37.651 EventManager: CONSULT_EVENT_INITIALISE
21:53:37.651 SetConsultState(): From 1 to 1
21:53:37.651 TX:FF FF EF
21:53:37.652 sendBufferArray: 3 bytes sent
21:53:37.652 SetConsultState(): From 1 to 0
21:53:37.652 ConsultSerialReadLoop(): Get status
21:53:37.652 ConsultSerialReadLoop(): Status Buffer available bytes: 3 (Errors = 0)
21:53:37.652 ConsultSerialReadLoop(): Pending wait on status
21:53:37.652 ConsultSerialReadLoop(): Get read
21:53:37.652 ConsultSerialReadLoop(): Buffer available bytes: 3 (Errors = 0)
21:53:37.652 ConsultSerialReadLoop(): Waiting for 3 bytes, stored 0 bytes, reading 3 bytes
21:53:37.652 ConsultSerialReadLoop(): Read 3 reclen bytes immediately
21:53:37.652 RX:FF FF EF
21:53:37.652 addArray RX bytes: FF FF EF [FF FF EF ]
21:53:37.652 CConsultSM:: StreamStateMachine
21:53:37.652 StateMachine: CONSULT_STATE_INITIALISE_CMD_RESP (buffer: 3/3 bytes)
21:53:37.652 getConsultArray(len=3)
21:53:37.652 getArray RX bytes: FF FF EF []
21:53:37.652 SetConsultState(): From 0 to 0
21:53:37.652 Reinitialisation check error FF:FF:EF
21:53:37.652 SetConsultState(): From 0 to 35
21:53:37.652 *1 ConsultCallBack(consult_state=35, pollcheck=1)
21:53:37.652 ConsultCallBack: Check error - Attempt reconnect
21:53:37.652 SetConsultState(): From 35 to 1
21:53:37.652 AttemptConnect(): Comms error
21:53:37.652 Consult ConsultCallBack() - Set initialisation IDLE event
21:53:37.652 CConsultSM::CloseConnection
21:53:37.652 ConsultSerialReadLoop...
21:53:37.652 ConsultSM::CloseConnection(): Terminating thread
21:53:37.652 ConsultSerialReadLoop(): state=1, read=0, status=1

[Matt]

whatever you are sending the device on COM3 is returning the exact thing back

FF FF EF should respond with 00 00 01

however above I am seeing FF FF EF response

Does COM3 show up still if you remove the consult connector?

What COM port is ECU talk etc connecting to?

Looks like TX/RX lines are shorted together from the above log

[enohand]

now i changed the com to 10,


ecutalk connects to 10 fine,


in nistune i have it set to auto, & tried com 3 like 3 times, & then com 10 once.....


i then changed the com port to 10 & it tried connecting once, but didnt




how should the port be setup in reg. to flow control & speed & stuff?

right now its:

19200 (i think)
8
none
1
none

[Matt]

now i changed the com to 10,
ecutalk connects to 10 fine,

in nistune i have it set to auto, & tried com 3 like 3 times, & then com 10 once.....

- what did it display when 'auto' was selected?
- so COM3 and COM10 were available for selection?
- why did you try COM3 when you had changed the device to COM10 inside device manager?

i then changed the com port to 10 & it tried connecting once, but didnt

could you please redo the logging, set the port to COM1 inside Device Manager. Manually set COM1 in the list (please confirm it displays COM1) then attempt connect four times

Please attach the log here afterwards. Nistune works fine with all cables that I'm aware of, so not sure why other apps work with this cable and not Nistune

However the same data coming back is a concern, shouldnt do that

[enohand]

ok will do, this cable used to work fine....i had some minor issues with previous releases picking the 1996 ODB2 file & then it would complain about USB drivers. but when selecting the 1995 adr file it would connect fine & i was able to tune.

However with the last 2-3 new builds i have not been able to connect. in the log i see that it gives the USB error again....so i dont know what the issue is...


& on the comment about using com3 when it was set via device manager to 10.

I had nistune set to auto, but @ the bottom you would see it try to connect to com3 3 times, then try com10 1 times & then say com10 spare...or somthing like that

[Matt]

I'll have a look through the releases (what release worked? 0.9.14.2?) since similar issue raised this week by someone else

[Matt]

Is this still an issue?

[bachig24u]

Is this still an issue?

I've had similar issue today with HCR32 type 2. ver:0.10.5
I found that "com port scan timeout" default of 4 needed to be moved to value of 6.

I was experimenting on a type 1 with belkin usb-serial adpater when I noticed it couldn't connect to WB.
anything less than vaue of 4 seemed to cause innovate LC-1 to not be recognized via the Belkin usb-serial adapter also.
is this a related issue?

[Matt]

Not related to this particular issue, but the timeout is related to how long it takes for your device to respond. Setting to 0 will make it wait indefinately. I might bump up the default a bit since some hardware out there takes longer than it should to respond unfortunately

[bachig24u]

wouldn't hurt, plus if ms-windows is busy with a malware scan, maybe software will timeout.

I was using the plms cable too!! getting power but 'no connection' in software.

no rx/tx lights on cable. just red power led.

second I bumped it up it worked. that was after i tried reconnecting usb-plms, then restart nistune also. short of rolling back to 0.9.x again. a little light bulb went off.

[Matt]

Interesting, must be slower PCs then if that cable (!)

I've increased to 7 seconds default