P38A Nanocom Evolution can't take record GEMS live data??

This site contains affiliate links for which LandyZone may be compensated if you make a purchase.

MrGorsky

Well-Known Member
Full Member
Posts
1,527
Location
Buckinghamshire.
Morning All,

MY1998 P38 4.6 Petrol GEMS. Nanocom Evolution running latest 1.35 firmware. 8gb SD card.

I'm trying to take a live trace of the GEMS fuelling inputs to see if I can deduce anything about my rough running issues. I can take a trace from the EAS module no problem, and I can take a trace from the Instruments module no problem, but when I try and take a trace from the fuelling module it fails every time.

I connect up the Nanocom, start the car, go to the GEMS fuelling module, press the floppy disc icon, give it a file a name, press ok, press ok again. The Nanocom confirms it's recording live data and then immediately stops again. Looking at the .csv file it creates all the headings for the various systems are there, but there isn't any actual data.

Like this...

Screenshot 2020-04-22 at 12.50.40.png

Whereas the instruments one works perfectly like this...

Screenshot 2020-04-22 at 12.51.28.png

Any idea what I'm doing wrong? Anyone done this before? @wammers you're good at this sort of thing aren't you? Help!
 
Morning All,

MY1998 P38 4.6 Petrol GEMS. Nanocom Evolution running latest 1.35 firmware. 8gb SD card.

I'm trying to take a live trace of the GEMS fuelling inputs to see if I can deduce anything about my rough running issues. I can take a trace from the EAS module no problem, and I can take a trace from the Instruments module no problem, but when I try and take a trace from the fuelling module it fails every time.

I connect up the Nanocom, start the car, go to the GEMS fuelling module, press the floppy disc icon, give it a file a name, press ok, press ok again. The Nanocom confirms it's recording live data and then immediately stops again. Looking at the .csv file it creates all the headings for the various systems are there, but there isn't any actual data.

Like this...

View attachment 206403

Whereas the instruments one works perfectly like this...

View attachment 206404

Any idea what I'm doing wrong? Anyone done this before? @wammers you're good at this sort of thing aren't you? Help!
Assuming that it's not a Nanocom problem, it's possible that the data rate is too fast for your SD card, what is the data recording speed of the card?
 
I can't see anything much else. I can try another card though, I've got a few fast ones for my camera, I can try one of them.

Surely there can't be that much data from a mid 90's engine ECU can there?
 
I can't see anything much else. I can try another card though, I've got a few fast ones for my camera, I can try one of them.

Surely there can't be that much data from a mid 90's engine ECU can there?
Depends what it's trying to record, CPS? ignition for each cylinder? injection for each cylinder? even at 800rpm idling, with 8 cylinders that amounts to quite a lot of data to be stored.
 
Sample rate for writing is pretty much once per second on the modules I have used. I don't think the Nano can go much faster. It does mean you can miss stuff but it is better than nothing. I am not sure what the system itself can handle.

If all modules apart from GEMS live data work then I suspect a bug with Nanocom.
 
And the answer is..... FAT.

I tried a 1gb card from an old camera I have. Formatted it using the Black Box card formatting app. It formats the card with a FAT file system. Not FAT 32!

Put it in the Nanocom to do a trace and it all records perfectly for as long as you want.

I'll let the tech nerds argue over why that might be, but I did read a post somewhere saying that Nanocom only supports FAT file systems and that seems to be true. The problem is you can't easily buy small capacity HD cards anymore, and FAT only supports up to 4gb doesn't it?
 
Back
Top