
Wont connect to datalogging on version 0.0.2.0r5
Moderator: Gaskleppie
- RoadXY
- Posts: 347
- http://phpbb3styles.net
- Joined: Mon Apr 16, 2007 10:06 am
- Location: Netherlands
- Contact:
i see im not the only one with the problem ( http://forum.ectune.com/viewtopic.php?t=599 ) my old logger had no problem connecting, but dont know if that was r4 or r5... anyone have the old version so i can try with that again?
Still an error:
The error trace:Zie het einde van dit bericht voor meer informatie over het aanroepen van JIT-foutopsporing (Just In Time) in plaats van dit dialoogvenster. ************** Tekst van uitzondering ************** System.NullReferenceException: De objectverwijzing is niet op een exemplaar van een object ingesteld. bij eCtune.Dal.Emulator.CheckEmulator(Boolean reportError) bij eCtune.Dal.Emulator.GetRom() bij eCtune.Dal.Datalogger.LogWOscan() bij eCtune.Dal.Datalogger.Log() bij eCtune.FrmMain.??????��?�(Object , EventArgs ) bij System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) bij System.Windows.Forms.ToolStripButton.OnClick(EventArgs e) bij System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) bij System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) bij System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) bij System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) bij System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bij System.Windows.Forms.Control.WndProc(Message& m) bij System.Windows.Forms.ScrollableControl.WndProc(Message& m) bij System.Windows.Forms.ToolStrip.WndProc(Message& m) bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
After disabling autoscan:DTL: Auto-Scan DTL: Ecu detection started DTL: baud: 115200 DTL: Cached port:12 DTL: Cached port: 12 open DTL: Ecu Replied E0 DTL: J12/J4 inplace detect DTL: Ecu Replied E0 DTL: J12/J4 inplace detect DTL: Ecu Replied E0 DTL: ECU-ISR not found on cached port: 12 DTL: Open port : 12 DTL: Ecu Replied E0 DTL: J12/J4 inplace detect DTL: Ecu Replied E0 DTL: J12/J4 inplace detect DTL: Ecu Replied E0 DTL: Port 12 is open and check ECU-ISR replied=False DTL: Open port : 13 DTL: Open port : 14 DTL: Open port : 15 DTL: Open port : 16 DTL: Open port : 17 DTL: Open port : 18 DTL: Open port : 19 DTL: Open port : 20 DTL: Open port : 21 DTL: Open port : 22 DTL: Open port : 23 DTL: Open port : 24 DTL: Open port : 25 DTL: Open port : 26 DTL: Open port : 27 DTL: Open port : 28 DTL: Open port : 29 DTL: Port Scan Failed at port 30
DTL: Ecu Replied E0 DTL: J12/J4 inplace detect DTL: Ecu Replied E0 DTL: J12/J4 inplace detect DTL: Ecu Replied E0 DTL: J12/J4 inplace detect DTL: Ecu Replied E0
- calvin
- <font color=gray>Site Admin</font><br><font color=green>eCtune Authorized Tuner</font>
- Posts: 4816
- Joined: Tue Apr 03, 2007 10:16 am
- Location: Paramaribo, Suriname
- Contact:
ecu is replying the wrong byte. Maddog20 has a know problem. But the ecu is replying bad info now what i can see here. 0xe0 is very wrong... Maybe wrong port? Wrong baud?
Regards, eCtune Team eCtune Authorized Tuner Location: Caribbean & Suriname aim:calvinPGMFI skype:ectune We remote connect to your laptop if you have problems. Best support in the world.
- integralactic
- Posts: 43
- Joined: Tue Apr 03, 2007 6:55 pm
- Location: Kamuela, Hawaii
- Gaskleppie
- <font color=gray>Site Admin</font><br><font color=green>eCtune Authorized Tuner</font>
- Posts: 1263
- Joined: Tue Apr 03, 2007 11:22 am
- Location: Netherlands
- Contact:
Yesterday I tested the latest r6 version. First time when I started datalogging, the datalog button seemed to go on and off a few times (about five times), very fast. The datalogging was starting anyway, but was very slow. (every 2 sec 1 reading) After restarting eCtune all worked like normal. It kept on working from then. Only the first time it was slow.