[DeeEmm]

Ok, still trying to get this to work. Would be pulling my hair out if I had any.

In miniterm I can pretty reliably get a tooth log response by sending the 'T' command, however, when using the com debug log in TS,it can be seen that the request times out...

Code: Select all

x54                                                                   T

29/08/18 3:28:09 PM :Info: Logger Processor stopped.
29/08/18 3:28:10 PM :Error: Unable to read Logger data. Timeout of 2000 ms. exceeded. time:4012
29/08/18 3:28:10 PM :Warning: Caught Exception Notifying LoggerDataListener, continuing
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
	at java.util.ArrayList.rangeCheck(ArrayList.java:653)
	at java.util.ArrayList.get(ArrayList.java:429)
	at com.efiAnalytics.tunerStudio.panels.TriggerLoggerPanel.e(Unknown Source)
	at com.efiAnalytics.tunerStudio.panels.TriggerLoggerPanel.d(Unknown Source)
	at com.efiAnalytics.tunerStudio.panels.TriggerLoggerPanel.i(Unknown Source)
	at com.efiAnalytics.tunerStudio.panels.TriggerLoggerPanel.b(Unknown Source)
	at aH.c.b(Unknown Source)
	at aH.c.e(Unknown Source)
	at aH.i.run(Unknown Source)
29/08/18 3:28:10 PM :Debug: Time:335.351s. All processing complete for 

The data is literally sent right after...

Code: Select all

29/08/18 3:28:10 PM :Time: 5:35.360: READ 256 bytes, 256 bytes
xD1 x44 xD3 xBC xD4 xB4 xDC x80 xEE xF4 xFC x40 x81 x88 xAC xE8       .D.........@....
xEF x8C x52 x70 xBC x90 x61 x30 x33 xDC x68 x98 x91 x1C x03 xB4       ..Rp..a03.h.....
x8B x14 x24 xB4 x59 xF8 xFE xC0 xE5 x3C xC9 x54 xBF x4C xB6 x04       ..$.Y....<.T.L..
xA8 xB8 xAB x4C x9D xEC x94 x94 x8B x40 x84 x28 x80 xFC x79 x20       ...L.....@.(..y.
x70 xF8 x75 x24 x73 x38 x77 xE8 x76 x98 x75 xA4 x76 xEC x7B x68       p.u$s8w.v.u.v.{h
x7A x98 x7A xD8 x7E xD0 x77 x34 x79 xF8 x73 x60 x73 x80 x6F xE8       z.z.~.w4y.s`s.o.
x6E x04 x64 xC8 x65 xE4 xC0 x10 x72 x2C x6B x24 x5B xB0 x62 x38       n.d.e...r,k$[.b8
x61 x24 x60 xCC x5B x14 x5B x20 x59 x1C x58 x10 x52 xE8 x51 x8C       a$`.[.[.Y.X.R.Q.
x51 xA4 x51 x68 x4C x64 x4B xA8 x4C xC0 x49 xC4 x4B x98 x49 x4C       Q.QhLdK.L.I.K.IL
x47 x10 x48 xC4 x48 x50 x49 x00 x49 x20 x49 x44 x47 x70 x48 x60       G.H.HPI.I.IDGpH`
x46 xC0 x46 x48 x44 xEC x49 x1C x41 x64 x42 x64 x7B xBC x49 xD4       F.FHD.I.AdBd{.I.
x47 x34 x38 x8C x3B xE8 x3D x74 x3A x88 x3B x84 x38 xA4 x3A xB4       G48.;.=t:.;.8.:.
x38 x44 x38 x38 x36 x74 x36 x50 x37 xC0 x35 x48 x33 xEC x36 x6C       8D886t6P7.5H3.6l
x34 x4C x36 xD4 x35 xD4 x34 xC4 x35 xEC x35 x60 x36 x04 x35 xE8       4L6.5.4.5.5`6.5.
x35 xD0 x36 x2C x35 x84 x34 xF4 x35 x00 x33 x90 x36 x18 x32 x58       5.6,5.4.5.3.6.2X
x32 xB4 x5F x30 x39 x90 x38 x38 x2B xCC x31 x14 x30 x00 x30 xB4       2._09.88+.1.0.0.

I want to extend the timeout to test this, but cannot find where it is set / defined.

The ini file timeout is set at 15,000 ms, which is clearly not what it's actually set to

Code: Select all

dataReadTimeout = 15000 ; time in ms

The greyed out drop down box in TS says 1000ms - obviously not that either - although having this enabled would obviously be the easiest way to change the timeout.

I've searched through the code and could not find anything

If anyone has some pointers on where this timeout is set it would be very much appreciated

TIA

[PSIG]

Have you tried clipping the tooth logger short? If I START it, I can wait only a moment after the STOP button un-grays to stop it, and it will display what it got so far. Perhaps that will avoid hitting a timeout?

David

[DeeEmm]

Have you tried clipping the tooth logger short? If I START it, I can wait only a moment after the STOP button un-grays to stop it, and it will display what it got so far. Perhaps that will avoid hitting a timeout?

David

Will give it a go.

[DeeEmm]

Actually just found this in the ini... (funny what a bit of sleep can achieve)

Code: Select all

blockReadTimeout = 2000

The value is the same. Will have a play.

Fingers crossed

[DeeEmm]

unfortunately neither has made a difference.

Timeout is not the right one as I'm still getting timeout value of 2000ms recorded in comms log

Code: Select all

x54                                                                   T

30/08/18 10:40:35 AM :Error: Unable to read Logger data. Timeout of 2000 ms. exceeded. time:4009

Will keep looking I guess

[DeeEmm]

Haven't really looked at this any more but have been playing with a different ECU the past few days (V0.4.2 board). This was the same board that tooth logging originally worked on for me. Unfortunately I did not test before I updated the firmware but found that the tooth logging is also not working on this board.

[theonewithin]

Bootcamp it.

[panpan]

Not a bad shout, I used "bootcamp" in my early B&G MSII days, and then VM's like Parallels. You sometimes still get comms issues, but generally VMs work alright. I have a 3D scanner using Windows 8.1 on a 2013 iMac with a Thunderbolt HDMI adaptor, which isn't the recommended set up.
I've been following this, as I have a couple of NO2C units, and got macOS, but I'm not ready to hook them up yet.

[noisymime]

What's the pulses you're feeding into the trigger?

The way it's currently set is that the trigger pulse data isn't sent to TS until there are 128 data points available. If you're sending a low res signal or one that is very 'slow', it's possible that TS is timing out before these 128 readings are available.

[DeeEmm]

Bootcamp it.

Yeah might have to, I'm now at the trying to get it running stage and not being able to diagnose properly is a big PITA.

What's the pulses you're feeding into the trigger?

The way it's currently set is that the trigger pulse data isn't sent to TS until there are 128 data points available. If you're sending a low res signal or one that is very 'slow', it's possible that TS is timing out before these 128 readings are available.

I bought a new scope. I've tried the 1khz square wave output which should fill the buffer pretty quickly but tooth logger still not working, I suspect that the buffer is not the issue. I have also got the ECU installed on a running car, nothing there either and I would expect to see the tooth logger working at idle.

I'd wager it's a TS <> OSX issue but as it's not running a megasquirt ECU I doubt that I will get any further help from EFI Analytics.

I'll give a VM a whirl. I have virtualbox installed on the desktop, been a while since I've used it as I always prefer to run natively. I'll see if I get a tooth log on that.

I have actually managed to diagnose a little of my original issue from my datalog, I'm getting random rpm spikes up to 12,000rpm, which is causing massive advance / ignition cut and very bad running as a result. I've tried bypassing the loom with a dedicated screened cable run direct to the ECU from the crank trigger and also tried the various levels of trigger filtering as well as running 12v / GND direct to the crank sensor from the battery (supply specs for sensor are 4.5v - 14.5v) but to no avail. I've tried a new crank sensor, issue is same.

I'm using a hall sensor with the 1k pullup jumpered on the board.

I'm beginning to suspect a fault on the ECU. Might change out C25 and see if it's an issue there. I am seeing some minor background noise on the scope at the input pin when set up on the desktop, but nowhere near high enough voltage to be seen as a positive pulse

I have also seen the issue even when on the bench with no tach pulse at all - My fuel pump relay chattered - unplugging the crank sensor stopped the issue. Unfortunately I did not have the scope hooked up at the time. I figure that it can only be the sensor or the ECU causing the problem and I'm pretty confident it's not the sensor as if I view the output on my scope it's as clean as you would expect from a hall sensor. The attached trace is from the sensor output

If anyone has any ideas... I'm all ears