Fuel Pressure guage

[jsmcortina]

I don't know how that is possible, unless the tuning data isn't getting sent to your ECU. It works for me and I can swap between "Raw" and "Linear" and watch the "Sensor 04" gauge change from ADC counts to volts.

James

[mr_minnis]

I don't know how that is possible, unless the tuning data isn't getting sent to your ECU. It works for me and I can swap between "Raw" and "Linear" and watch the "Sensor 04" gauge change from ADC counts to volts.

James

only strange thing I see with sending data to the ECU is sometimes I get a message when "burn" is hit. The message is "Turn off engine before sending local tune" there is a "yes" and "No" option. I'm not sure exactly when this started, but was about 6 months ago.

Could the ADC to PSI formula for the generic sensors be corrupted ? That would only be true if there was a formula for each section of devices in the firmware.
Or maybe it is something with tuner studio on my laptop, (not sending the data right for some reason).

I have tuner studio installed on my desktop. I will configure the fuel pressure gauge and see what happens.

if that doesn't work,is it worth a shot to reload firmware?

[jsmcortina]

only strange thing I see with sending data to the ECU is sometimes I get a message when "burn" is hit. The message is "Turn off engine before sending local tune" there is a "yes" and "No" option. I'm not sure exactly when this started, but was about 6 months ago.

That's a question for the TunerStudio guys.

Could the ADC to PSI formula for the generic sensors be corrupted ?

Very unlikely.

if that doesn't work,is it worth a shot to reload firmware?

Very unlikely.

Please see this video: http://youtu.be/HNKA539h7v4

James

[mr_minnis]

only strange thing I see with sending data to the ECU is sometimes I get a message when "burn" is hit. The message is "Turn off engine before sending local tune" there is a "yes" and "No" option. I'm not sure exactly when this started, but was about 6 months ago.

That's a question for the TunerStudio guys.

Could the ADC to PSI formula for the generic sensors be corrupted ?

Very unlikely.

if that doesn't work,is it worth a shot to reload firmware?

Very unlikely.

Please see this video: http://youtu.be/HNKA539h7v4

James

I connected the ms3 to my other computer Fuel pressure gauge has same result (still showing in raw format).
you were correct on the firmware, it didn't do anything.
I verified the ms3x connector for the board is seeing the same voltage as i am putting into it
I agree with your video, it worked like it was supposed to at one time.

do you have anything left for me to try (hardware or software) ?
I'll email efi analytics for information about the one error.

[jsmcortina]

"same result" means that it works or doesn't work?

If you are seeing something different, please post an equivalent video showing what's happening.

James

[mr_minnis]

"same result" means that it works or doesn't work?

If you are seeing something different, please post an equivalent video showing what's happening.

James

same result means it is doing the same on both computers (sorry about being vague). It still shows ADC It is like the unit is stuck in raw and can't convert to the linear scale that is setup. I also have purchased shadow dash and it shows incorrectly on it also.

[mr_minnis]

Video showing issue
https://youtu.be/X5yBTTNk7zc

[jsmcortina]

One thing I notice right away - your MSQ isn't (wasn't) configured to do anything with Fuel Pressure 2 - that's the DUAL FUEL pressure. You need to be looking at Fuel Pressure 1.

Can you try the exact same test as I did with Sensor 04 please.

James

[mr_minnis]

I have configured it like You did in your video and it doesn't matter what the transformation is set to, it only displays as ADC.
It seem to be stuck in RAW.

https://www.youtube.com/watch?v=Io4_L7q ... CEFz9HwWDQ

[jsmcortina]

Until you posted the video, I would have said that was impossible. Now I'm just baffled.

As a third test, please could you do the following.
Close TunerStudio.
Find and delete the file ..../TunerStudioProjects/TunerStudioAppDebug.txt
Turn off the Megasquirt.
Open TunerStudio
Tick Communications->Debug Log Comm
Turn on the Megasquirt.
Go through the same steps in the second video (no need to record it.)
Close TunerStudio
Find the file ..../TunerStudioProjects/TunerStudioAppDebug.txt
Zip it up and upload it here.

James

[mr_minnis]

Until you posted the video, I would have said that was impossible. Now I'm just baffled.

As a third test, please could you do the following.
Close TunerStudio.
Find and delete the file ..../TunerStudioProjects/TunerStudioAppDebug.txt
Turn off the Megasquirt.
Open TunerStudio
Tick Communications->Debug Log Comm
Turn on the Megasquirt.
Go through the same steps in the second video (no need to record it.)
Close TunerStudio
Find the file ..../TunerStudioProjects/TunerStudioAppDebug.txt
Zip it up and upload it here.

James

here ya go. For the first set of changes I didn't have the dc power supply on. For the second it was set to 2.0 volts. Changed sensor 4 to several different transformations

[jsmcortina]

That log DOES explain it!

The explanation is rather technical, but in brief it is an unexpected interaction between the data TunerStudio is sending and the way the firmware reads it.

You _may_ be able to resolve that problem by:
- SaveTuneAs your MSQ
- reloading the same firmware
- make sure you DO NOT preserve the MSQ when the loader asks
- open up TunerStudio and load in your MSQ

The next pre-1.3.3 beta code will have a fix to ignore unexpected data like this.

James

[mr_minnis]

That log DOES explain it!

The explanation is rather technical, but in brief it is an unexpected interaction between the data TunerStudio is sending and the way the firmware reads it.

You _may_ be able to resolve that problem by:
- SaveTuneAs your MSQ
- reloading the same firmware
- make sure you DO NOT preserve the MSQ when the loader asks
- open up TunerStudio and load in your MSQ

The next pre-1.3.3 beta code will have a fix to ignore unexpected data like this.

James

I will try that when I get home from work and report back.
Thanks for working on the problem.

[mr_minnis]

James,

thanks for all your help firmware 1.3.2a took care of the issue.