Yep, spent a lot of time in that today. Making some progress.
Some questions. For AFR, why does the megasquirt send two request packets if it's a 1-byte variable? If I enable "Fetch Innovate EGO Data via CAN", it sends two request packets - one to table 7, offset 252 (where I specified) and one to table 7, offset 260 (not expected).
Also, unless I'm not parsing this response correctly, the megasquirt is asking to store the response at table 7 (myvarblk), offsets 597 and 605 (myvaroffset)? Is this right? It doesn't seem to use this data if I make a response to that location.
If I broadcast a message to table 7, offset 252 I can see the result in tunerstudio... so what do I do with myvarblk and myvaroffset?
See attached raw messages from my megasquirt, requesting EGO data on table 7 offset 252.
Code: Select all
Type: 1 To: 10 Table: 7 Offset: 252
Data0: 111
Data1: 1001010
Data2: 10101000
Data3: 0
Data4: 0
Data5: 0
Data6: 0
Raw ID: 100000100001000010100111000
Type: 1 To: 10 Table: 7 Offset: 260
Data0: 111
Data1: 1001011
Data2: 10101000
Data3: 0
Data4: 0
Data5: 0
Data6: 0
Thanks!
Edit: I forced my response to table 7 offset 252 and
I got some nice smooth digital AFR goodness in my megasquirt. So I still need to figure out what the deal is with the myvarblk and myvaroffset, because this isn't an elegant solution. I took a quick cell phone video comparing analog vs digital in case anyone was wondering what the difference looks like.
https://www.youtube.com/watch?v=hXu9RfWrqsU
In the meantime, I'm going to work on requesting some data from the MS, since my firmware doesn't have the 11 bit broadcasting...
Edit 2: Well that was easy. Got it pretty much first try. Looks like I won't need that 11 bit broadcast after all, though it would be nice.