View unanswered posts | View active topics It is currently Mon Jan 25, 2021 10:33 am



Reply to topic  [ 5 posts ] 
Full Decoder Setup In Tunix? 
Author Message
Moderator
User avatar

Joined: Tue Jan 15, 2008 2:31 pm
Posts: 15376
Location: Home sweet home!
I came across these screen shots of some app watching the BMW 60-2 pattern and noticed that it actually recognises the pattern in the code on the PC. I thought that that is a nice feature. You could setup the Listener decoder on an engine, take a recording using the yet-to-be-written log type here and then run a set of algorithms over it and TELL the user which pattern they have and which firmware they need. Taken one step further you could load that firmware type for them, by name and allow the truly stupid to wire up an engine and not have to think. Personally I think that last step is a TERRIBLE idea, but it could be done.

Image

Image

You could actually take it a step further than this and report that it is in fact a 60 minus 2 but wired backwards as it is possible to determine that from the log. I intend to report a "wiring backwards" error from the decoder in real time too, however identifying it from a log while away from the car would be nice. And decoder could would be ULTRA easy to write in a PC app with no real time pressures and floating point math.

Ben Fenner actually suggested doing this sort of black magic in the firmware, but if done thoroughly for a large number of possible patterns and connections it would be unfeasible in a real time context, and regardless of that, it's a bad idea to assume what the user has. That should definitely be explicitly provided to the device as a setup parameter.

This thread could equally go in the OLV section. If no one else steps up, I may write a utility to do it at some point.

I would probably not give an answer, but rather a full listing with colourised results such that if there was any ambiguity it was clearly shown. The list could be sorted by result rather than name, and sub sorted by name.

Fred.

_________________
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!


Sat Oct 01, 2011 12:44 pm
Profile WWW
LQFP144 - On Top Of The Game
User avatar

Joined: Wed Jul 09, 2008 3:15 pm
Posts: 360
If the firmware isn't going to do it, it would be pretty baller to be able to at least log the engine cranking, and then have the log application (or something else) parse the data and (at least) suggest the type of trigger wheel/situation you're dealing with. Along with things like "your wires are likely hooked up backwards" and such as you've mentioned.

Not high on my list of desires. Just one of those "this would make FreeEMS better than such and such EMS".

_________________
BenFenner's 1994 Black SE-R
BenFenner's 2000 Black M-Coupe


Wed Oct 05, 2011 4:36 pm
Profile
Moderator
User avatar

Joined: Tue Jan 15, 2008 2:31 pm
Posts: 15376
Location: Home sweet home!
The firmware definitely is NOT going to do this, but yeah, a PC app absolutely could, and not at all hard to do, either! :-)

_________________
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!


Wed Oct 05, 2011 7:19 pm
Profile WWW
Moderator
User avatar

Joined: Tue Jan 15, 2008 2:31 pm
Posts: 15376
Location: Home sweet home!
A few more variations on the above:

  • Run each decoder over the data with different time tolerance levels N times
  • Run each decoder over the data with the pin state inverted and not inverted
  • List the number of times sync was gained/lost
  • 1 gain and 0 or 1 losses = "perfect match"
  • gains == losses && gains !=1 = "no match, bulk noise or multiple sequences in one recording"
  • number of iterations between losses = some large number = "good match"
  • If inverted signal matches, give advice to fix circuitry
  • Give advice on tolerance levels with the caveat that it depends what sort of data was fed in (cranking, revving, noise, etc)

etc.

_________________
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!


Fri Oct 07, 2011 12:33 pm
Profile WWW
Moderator
User avatar

Joined: Tue Jan 15, 2008 2:31 pm
Posts: 15376
Location: Home sweet home!
For reference, Ben's original thread on doing this in firmware: viewtopic.php?f=41&t=1148

_________________
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!


Thu Oct 20, 2011 10:10 am
Profile WWW
Display posts from previous:  Sort by  
Reply to topic   [ 5 posts ] 

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software for PTF. ColorizeIt.