Not real sure where to post this but I am trying to understand burstmode.
I am using MSII v2.33 and megatune 2.25.
I am trying to setup a piece of logging software(not ms related) to decode the MSII data stream so I can add some MS data to the master log. Looking at the comm.log of megatune I see the gauges are using burst mode. I think I have all the data needed to complete my project just a lack of understanding.
I'm sending a oo 06 to MS and receiving a 112 byte block back. So far so good.
I'm trying to extract-
RPM
MAP
AFR
CTS
TPS
spark advance
From the Megatune v2.33 ini file I see the information I need, but I am a little confused.
Example-
rpm = scalar, U16, 6, "RPM", 1.000, 0.0
advance = scalar, S16, 8, "deg", 0.100, 0.0
RPM = scaler??
U16 = unsigned 16bit int
6 = byte 6 MSB
byte 7 LSB
1.000??
0.0??
bytes 6,7 * 1.000 - 0.0 == RPM??
advance = scalar??
S16 = signed 16bit int
8 = byte 8 MSB
byte 9 LSB
bytes 8,9 * .100 - 0.0 == ignition advance??
I've searched the archives several time and found much data on the vaious comm strings but still don't have a great understanding of the different datablocks. I use megatune for most of my tuning, works great.
I am just trying to combine MS data with some chassis stuff.
All comments welcome, thanks to anyone willing-
Joe
Understanding burstmode
Forum rules
Read the manual to see if your question is answered there before posting. If you have questions about MS1/Extra or MS2/Extra or other non-B&G code configuration or tuning, please post them at http://www.msextra.com The full forum rules are here: Forum Rules, be sure to read them all regularly.
Read the manual to see if your question is answered there before posting. If you have questions about MS1/Extra or MS2/Extra or other non-B&G code configuration or tuning, please post them at http://www.msextra.com The full forum rules are here: Forum Rules, be sure to read them all regularly.
Ok,
I have my array decoding sorted out, turns out I had an off by 1 error.
Anybody know what 'Purge' does before the block request.
Pulled from the comm log. I can guess It purges something, just curious if this is a command sent to MS or for megatune use?
After about 600 seconds my data stops, I have to restart my MSII to get it to communicate again. I notice it when my "Seconds" stop. I have tried different delay settings in my program but for some reason my Megasquirt communication locks up. Works great in Megatune. I just find it odd I have to restart MegaSquirt not my PC.
Any suggestions?
Thanks,
Joe
MSII v2.33
I have my array decoding sorted out, turns out I had an off by 1 error.
Anybody know what 'Purge' does before the block request.
Pulled from the comm log. I can guess It purges something, just curious if this is a command sent to MS or for megatune use?
After about 600 seconds my data stops, I have to restart my MSII to get it to communicate again. I notice it when my "Seconds" stop. I have tried different delay settings in my program but for some reason my Megasquirt communication locks up. Works great in Megatune. I just find it odd I have to restart MegaSquirt not my PC.
Any suggestions?
Thanks,
Joe
MSII v2.33
OK,
A bit more information-
I am using Dynomax 2000. I am trying to add a custom board(MSII) to my dyno log. That way my log will have HP, torque, and some actual MS data. I am trying to use the MS datastream instead of having two of each sensor. Dynomax has a fuel mapping feature that runs an engine through the fuel map. It can be configured to log AFR at different rpm's and load.
I am hoping to integrate the MSII datastream. I drop comm with the MSII after about 600 seconds, consistantly. Restarting my MS restores comm with dynomax. Anybody think a newer version of MSII firmware might fix this??(I'm using 2.33)
Thoughts??
600 seconds is actually plenty for what I want to do but it bothers me that I have a comm problem.
Thanks for any input-
Joe
A bit more information-
I am using Dynomax 2000. I am trying to add a custom board(MSII) to my dyno log. That way my log will have HP, torque, and some actual MS data. I am trying to use the MS datastream instead of having two of each sensor. Dynomax has a fuel mapping feature that runs an engine through the fuel map. It can be configured to log AFR at different rpm's and load.
I am hoping to integrate the MSII datastream. I drop comm with the MSII after about 600 seconds, consistantly. Restarting my MS restores comm with dynomax. Anybody think a newer version of MSII firmware might fix this??(I'm using 2.33)
Thoughts??
600 seconds is actually plenty for what I want to do but it bothers me that I have a comm problem.
Thanks for any input-
Joe