ITT We discuss Megasquirt Firmware Releases
#1
ITT We discuss Megasquirt Firmware Releases
I thought of this thread while doing some research on updating my MS3 Basic from it's current firmware release of 1.3.4 to the new 1.4.X firmware. I figured it might be nice to have a thread here to discuss firmware updates.
The idea would be similar to the seat mounting thread or aero thread. It's always impossible to get posters to re-use a template for each post but we'll try it anyway.
MS Model: (MS3 Basic, DIY, MSpnpPro)
MS Unique/Special Specifics:
Current/Previous Firmware Version:
New Firmware Version:
Impressions of new firmware:
Issues:
Maybe this is a dumb idea... maybe it isn't. I wouldn't mind seeing some firmware discussions from those that I've leached, lurked and learned from.
The idea would be similar to the seat mounting thread or aero thread. It's always impossible to get posters to re-use a template for each post but we'll try it anyway.
MS Model: (MS3 Basic, DIY, MSpnpPro)
MS Unique/Special Specifics:
Current/Previous Firmware Version:
New Firmware Version:
Impressions of new firmware:
Issues:
Maybe this is a dumb idea... maybe it isn't. I wouldn't mind seeing some firmware discussions from those that I've leached, lurked and learned from.
#2
SADFab Destructive Testing Engineer
iTrader: (5)
Join Date: Apr 2014
Location: Beaverton, USA
Posts: 18,642
Total Cats: 1,866
MS Model: MS3/3x DIY
Previous: 1.4 Release
New: 1.5 alpha
Impressions: Nothing new to report. Dome boost control is being implemented, along with engine states, but I don't have a dual solenoid setup to test dome control, and the engine states are currently just for logging and testing.
Issues: None
Previous: 1.4 Release
New: 1.5 alpha
Impressions: Nothing new to report. Dome boost control is being implemented, along with engine states, but I don't have a dual solenoid setup to test dome control, and the engine states are currently just for logging and testing.
Issues: None
#6
I of course realize that msextra is the first stop. However i've found that on this side of the MS universe we do a few things that aren't quite as common (can wb02 module). When I'm reading on msextra I often find myself wondering if a feature that's listed in a firmware update applies to our cars. Yes I know,
For example, in the 1.4 firmware release thread (at this link) it lists...
Under features:
-CAN Broadcasting - two new options
Holset HE351VE VGT turbo - this broadcasts 'boost duty' with a 29bit CAN identifier specific to the turbo.
-User defined testing - allows custom CAN packets to be broadcast
-CAN Realtime Data Broadcasting - this is a major enhancement allowing all of the engine parameters to be broadcast to the CAN using standard 11bit identifiers which can then be received and displayed by suitable 3rd party dashes or dash loggers.
-CAN Receiving - another major enhancement is the ability to receive and process standard 11bit CAN messages. These can be used to collect remote sensor data or wheel speed from ABS
And under known issues:
"can_in" polling setting corrupts "can_out". See Megasquirt Support Forum (MSEXTRA) ? Bug: 1.4 Firmware and IO Extender (View topic)
CAN passthrough may have issues with some older IO-x firmwares.
Boost by speed scaling issue.
After doing a lot of looking on msextra, it seems that per capita of ms users, this forum has a lot more people gravitating to the CAN functionality. Seeing those as part of the new firmware made me wonder if anyone here had insight on the new firmware. That's really what made this idea pop into my head. I find more succinct answers here that are easier to apply to my MS life on this forum then over there.
TL;DR I am a
Also, for the record... using CAN or even "can bus" as a search term sucks.
For example, in the 1.4 firmware release thread (at this link) it lists...
Under features:
-CAN Broadcasting - two new options
Holset HE351VE VGT turbo - this broadcasts 'boost duty' with a 29bit CAN identifier specific to the turbo.
-User defined testing - allows custom CAN packets to be broadcast
-CAN Realtime Data Broadcasting - this is a major enhancement allowing all of the engine parameters to be broadcast to the CAN using standard 11bit identifiers which can then be received and displayed by suitable 3rd party dashes or dash loggers.
-CAN Receiving - another major enhancement is the ability to receive and process standard 11bit CAN messages. These can be used to collect remote sensor data or wheel speed from ABS
And under known issues:
"can_in" polling setting corrupts "can_out". See Megasquirt Support Forum (MSEXTRA) ? Bug: 1.4 Firmware and IO Extender (View topic)
CAN passthrough may have issues with some older IO-x firmwares.
Boost by speed scaling issue.
After doing a lot of looking on msextra, it seems that per capita of ms users, this forum has a lot more people gravitating to the CAN functionality. Seeing those as part of the new firmware made me wonder if anyone here had insight on the new firmware. That's really what made this idea pop into my head. I find more succinct answers here that are easier to apply to my MS life on this forum then over there.
TL;DR I am a
Also, for the record... using CAN or even "can bus" as a search term sucks.
#9
SADFab Destructive Testing Engineer
iTrader: (5)
Join Date: Apr 2014
Location: Beaverton, USA
Posts: 18,642
Total Cats: 1,866
I of course realize that msextra is the first stop. However i've found that on this side of the MS universe we do a few things that aren't quite as common (can wb02 module). When I'm reading on msextra I often find myself wondering if a feature that's listed in a firmware update applies to our cars. Yes I know,
For example, in the 1.4 firmware release thread (at this link) it lists...
Under features:
-CAN Broadcasting - two new options
Holset HE351VE VGT turbo - this broadcasts 'boost duty' with a 29bit CAN identifier specific to the turbo.
-User defined testing - allows custom CAN packets to be broadcast
-CAN Realtime Data Broadcasting - this is a major enhancement allowing all of the engine parameters to be broadcast to the CAN using standard 11bit identifiers which can then be received and displayed by suitable 3rd party dashes or dash loggers.
-CAN Receiving - another major enhancement is the ability to receive and process standard 11bit CAN messages. These can be used to collect remote sensor data or wheel speed from ABS
And under known issues:
"can_in" polling setting corrupts "can_out". See Megasquirt Support Forum (MSEXTRA) ? Bug: 1.4 Firmware and IO Extender (View topic)
CAN passthrough may have issues with some older IO-x firmwares.
Boost by speed scaling issue.
After doing a lot of looking on msextra, it seems that per capita of ms users, this forum has a lot more people gravitating to the CAN functionality. Seeing those as part of the new firmware made me wonder if anyone here had insight on the new firmware. That's really what made this idea pop into my head. I find more succinct answers here that are easier to apply to my MS life on this forum then over there.
TL;DR I am a
Also, for the record... using CAN or even "can bus" as a search term sucks.
For example, in the 1.4 firmware release thread (at this link) it lists...
Under features:
-CAN Broadcasting - two new options
Holset HE351VE VGT turbo - this broadcasts 'boost duty' with a 29bit CAN identifier specific to the turbo.
-User defined testing - allows custom CAN packets to be broadcast
-CAN Realtime Data Broadcasting - this is a major enhancement allowing all of the engine parameters to be broadcast to the CAN using standard 11bit identifiers which can then be received and displayed by suitable 3rd party dashes or dash loggers.
-CAN Receiving - another major enhancement is the ability to receive and process standard 11bit CAN messages. These can be used to collect remote sensor data or wheel speed from ABS
And under known issues:
"can_in" polling setting corrupts "can_out". See Megasquirt Support Forum (MSEXTRA) ? Bug: 1.4 Firmware and IO Extender (View topic)
CAN passthrough may have issues with some older IO-x firmwares.
Boost by speed scaling issue.
After doing a lot of looking on msextra, it seems that per capita of ms users, this forum has a lot more people gravitating to the CAN functionality. Seeing those as part of the new firmware made me wonder if anyone here had insight on the new firmware. That's really what made this idea pop into my head. I find more succinct answers here that are easier to apply to my MS life on this forum then over there.
TL;DR I am a
Also, for the record... using CAN or even "can bus" as a search term sucks.
Holset HE351 has a CAN controled VGT actuator that is finally getting real support. It has been in testing for a while.
IO-x is an expander board made by a 3rd party, only relevant if you have his expander board.
If you aren't using boost by speed then the other issue isn't needed.
The biggest issue on this forum is that a lot of people use a MS3Basic, which is different than your standard builds on msextra. But as far as I know it uses an MS3 chip, which means any firmware can be loaded. @Reverant can comment on this.
Thread
Thread Starter
Forum
Replies
Last Post