Page 1 of 4
Wont connect to datalogging on version 0.0.2.0r5
Posted: Wed Nov 28, 2007 11:07 pm
by integralactic
Updated to version 0.0.2.0r5 today. Ostrich v1 and Hulog Ostrich connected and put base rom& calibration KOEO clicked on connect datalog, nothing happens. used shortcutkeys to try to connect, nothing happens under settings datalog comm, click test, also nothing. no comm error popup switched to different USB ports, restarted laptop, made new basemap and put, still no response. Switched back to version 0.0.2.0r4 and datalogging connects and works fine. Went back to version 0.0.2.0r5 went through all steps again and no connection. Also I cannot verify rom and get rom with both versions. Ostrich v1 Firmware version: 19
Posted: Thu Nov 29, 2007 12:34 am
by calvin
no verify... i have to add an option for you. I guess i know what it is. But datalogging should work. Can you go to settings and try debug and paste the output
Posted: Thu Nov 29, 2007 2:19 am
by zex_cool
i had a similar problem with the r5. all i had to do tho was; settings>datalogging com>disable auto scan. when i tested it, it worked. went back to the datalog tab>connect and i was back in business.
Posted: Thu Nov 29, 2007 3:20 am
by integralactic
zex_cool wrote:i had a similar problem with the r5. all i had to do tho was; settings>datalogging com>disable auto scan. when i tested it, it worked. went back to the datalog tab>connect and i was back in business.
Thank you! That worked!
Posted: Thu Nov 29, 2007 3:29 am
by integralactic
calvin wrote:no verify... i have to add an option for you. I guess i know what it is. But datalogging should work. Can you go to settings and try debug and paste the output
This is what I get when I hit debug>test ISR with auto scan checked: DTL-Auto-Scan DTL-Ecu detection started I get this with auto scan unchecked: DTL-Ecu Replied 7F DTL-Ecu Replied 7F
Posted: Thu Nov 29, 2007 7:40 am
by calvin
ok 7F with the right port and baud? and with auto-scan connect it stops at 'DTL-Ecu detection started'? I had this too on my laptop i thought it was my laptop that was messed up. I'll look at it glad you got it to work
Posted: Thu Nov 29, 2007 8:11 am
by calvin
fixed
Posted: Sat Dec 01, 2007 2:52 pm
by RoadXY
Can't connect. When I hit ctrl-alt-d to connect I don't get a message. Disable auto-scan en select the right port en test: Finds ECU. Hit connect en shoots me an error message (in Dutch):
Code: Select all
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.ConnectWOScan() bij eCtune.Dal.Emulator.Connect() 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.ToolStripMenuItem.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.ToolStripDropDown.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.ToolStripDropDown.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) ************** Geladen assembly's ************** mscorlib Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.832 (QFE.050727-8300) CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- eCtune Assembly-versie: 0.0.2.0 Win32-versie: 0.0.2.0 CodeBase: file:///C:/Program%20Files/eCtune/eCtune.EXE ---------------------------------------- System Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.832 (QFE.050727-8300) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Windows.Forms Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.832 (QFE.050727-8300) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.832 (QFE.050727-8300) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- startup_lib_net_2_0 Assembly-versie: 2.0.0.0 Win32-versie: 0.0.2.0 CodeBase: file:///C:/Program%20Files/eCtune/eCtune.EXE ---------------------------------------- mscorlib.resources Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.832 (QFE.050727-8300) CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- System.Management Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.832 (QFE.050727-8300) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll ---------------------------------------- System.Windows.Forms.resources Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_nl_b77a5c561934e089/System.Windows.Forms.resources.dll ---------------------------------------- Accessibility Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- System.Configuration Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.832 (QFE.050727-8300) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.832 (QFE.050727-8300) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Web.Services Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll ---------------------------------------- System.Deployment Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.832 (QFE.050727-8300) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll ---------------------------------------- System.Deployment.resources Assembly-versie: 2.0.0.0 Win32-versie: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Deployment.resources/2.0.0.0_nl_b03f5f7f11d50a3a/System.Deployment.resources.dll ---------------------------------------- ************** JIT-foutopsporing ************** Als u JIT-foutopsporing wilt inschakelen, moet in het configuratiebestand voor deze toepassing of computer (machine.config) de waarde jitDebugging in het gedeelte system.windows.forms zijn ingesteld. De toepassing moet ook zijn gecompileerd terwijl foutopsporing was ingeschakeld. Bijvoorbeeld: <configuration> <system.windows.forms jitDebugging=\"true\" /> </configuration> Wanneer JIT-foutopsporing is ingeschakeld, worden onverwerkte uitzonderingen naar het JIT-foutopsporingsprogramma gestuurd dat op de computer is geregistreerd en worden niet door dit dialoogvenster verwerkt.
Posted: Sat Dec 01, 2007 2:57 pm
by calvin
no idea what that is. i have to check back home.
Posted: Sun Dec 02, 2007 11:48 am
by RoadXY
Any thing I have to test for you to make things clearer?
Posted: Sun Dec 02, 2007 9:42 pm
by calvin
no i'll test the datalogger version back home again will go through the function again see what can cause the error
Posted: Mon Dec 03, 2007 8:27 am
by RoadXY
Ok, thanx.
Posted: Mon Dec 03, 2007 8:21 pm
by calvin
i have to test. I don't see why it trhows this error.
Posted: Tue Dec 04, 2007 1:32 am
by JaredKaragen
try loading the calibration before connecting.....
Posted: Tue Dec 04, 2007 7:30 am
by calvin
JaredKaragen wrote:try loading the calibration before connecting.....
did you ever work with the datalogger version? i guess not