MS3 pre-1.4 alpha 5 released

[jsmcortina]

To announce the release of "MS3 Pre 1.4 alpha 5"
ETA on this 1.4.x code becoming release is 6-12 months.

Who should use this code?
Experienced users wanting to test the new features.

Who should not use this code?
New or casual users - please use the current release code instead - see the Downloads page linked above.

Main changes since pre-1.4 alpha 4

Bug fixes:
Resolve MegaView units altering wrong bytes in 'A' datastream. Make degC work as expected.
Fix typo in ini file.
Bitmask generic sensor selectors.
Various ini tweaks, missing tooltips etc.
Rename a few indicators that were duplicated.
Apply bitmasks to EAEOption.
Fix on/off VVT output. (Minor re-arrangement of init code.)
Fix Y axis display units on VVT on/off table.

New / changed features:
Allow MAP/kPa to trigger an SDcard log
SDcard pulse output (for Go-Pro)
Allow cam polarity to be flipped on custom decoders. (Tested some modes.)
Ungrey cam poll polarity for GM7X. (Was being used already.)
Add 29bit CAN broadcast for Holset HE351VE turbo.
Change EGO delay scaling to allow longer delay.
Allow nitrous fuel solenoid to run at different frequency.
4G63 uses 'edge2' to allow cam to be flipped.
PDF help manual now available from within TunerStudio (linkage added to ini file) click on Help on any page, curve, table.

Minor / internal:
Tweak comments in ms3.h
More generalised 'edge2' handling.
Remove EAElag compensation (already partly removed.)

The firmware zip is available from:
http://www.msextra.com/doc/ms3/files/al ... alpha5.zip

Be sure to read the README.txt and RELEASE-NOTES.txt that are supplied in the zipfile.
Some of the ini changes will result in harmless warnings when loading MSQs from 1.3.x
Users upgrading from 1.2.x or earlier codes need to pay more attention.
TunerStudio 2.6.x is REQUIRED.

James

[hardline]

James, could you explain this one in a bit more detail, SD Card Pulse for Go-Pro?

[Reverant]

James, could you explain this one in a bit more detail, SD Card Pulse for Go-Pro?

Sends a "start recording" 5V pulse to a Go-Pro camera? But definitely needs more documentation.

[elaw]

New / changed features:
Allow MAP/kPa to trigger an SDcard log

James,

This isn't directly related to the alpha but reading the notes gave me an idea for a cool feature which basically would be a new SD logging mode (as if you didn't have enough to do already ).

What you'd do is continuously put data in a circular buffer (does SD logging do that already?), then when a specified trigger event occurs (CEL, sync loss, variable going above or below a set threshold, etc.) you'd start an SD log and write out the current contents of the buffer to the log file. The idea being that the log would show what happened just *before* a particular event occurred. Kind of like a digital 'scope that can show data sampled prior to the trigger point. What happens afterward is up for debate... my suggestion would be to continue logging for a specified amount of time (probably a few seconds) then stop and "rearm".

[jsmcortina]

Ah... the old "WTF!" mode.
We discussed that a few years back, but I wasn't able to figure out an easy way to do it.

James

[jsmcortina]

James, could you explain this one in a bit more detail, SD Card Pulse for Go-Pro?

Sends a "start recording" 5V pulse to a Go-Pro camera? But definitely needs more documentation.

It is a ground pulse that happens when the MS3 datalog is triggered. If wired correctly to a Go-Pro camera it will cause that to start recording at the same time.

James

[nismoautoxr]

James, could you explain this one in a bit more detail, SD Card Pulse for Go-Pro?

Sends a "start recording" 5V pulse to a Go-Pro camera? But definitely needs more documentation.

It is a ground pulse that happens when the MS3 datalog is triggered. If wired correctly to a Go-Pro camera it will cause that to start recording at the same time.

James

WOW . This is exactly what I need now because I can reach my datalog trigger just fine whilst being harnessed in and geared up . Cant reach the camera so I am forced to start the video before I head to grid and have to edit all that wasted space stuff out . Is there a thread or some other source that can give me a rundown on how the interface is done ?

[thokes82]

The GoPro must be set up in "1 button mode" so when it turns on it begins recording automatically. Then you connect Gopro's Pin 1 to GND of the MS and PIN 12 to the MS Output which you selected.
MS must send a pulse at the start of logging to switch it on and pulse at the end to switch it off. Now you need to get a cable to get started. Hero2 works for sure. There was something strange about the control of the recent models but I forgot.

[jsmcortina]

Recent models cannot be stopped apparently, so I didn't implement that.

James

[nismoautoxr]

the camera I use right now is a hero3 silver. I gather that leaves me out sorta? I mean here is my thing....I got 1 cell phone.... I got a transponder ....but only a few of the track events I do per season are timed ,so ,for those that are not using my transponder ....I use my phone to time the laps. This means that the phone is in use so i am obviously not going to bother to use it as a remote for the camera....if I could at least trigger the start of the video with the start of a log that would kill 2 birds with one stone and leave a 3rd for me to deal with accordingly...is that what is being said?

[jsmcortina]

The cable that you can plug into the GoPro cameras has a "start logging" ground-switch input (apparently.)

James

[nismoautoxr]

The cable that you can plug into the GoPro cameras has a "start logging" ground-switch input (apparently.)

James

Thanks James . I will see if any of this can work for me .

[nismoautoxr]

Its looking like for me to use this with my camera .... I will need to go into the camera and solder and bring out a couple wires to trigger the on off and shutter functions and then use ground to make those function . I have not seen any ready made plugin cable to make this happen. I think the wifi feature was meant to eliminate the need for this . Wifi is nice but you still gotta have the wifi on to make the remote work and that sucks the batteries so on a race weekend ...that is still just one more thing to do .

Now assuming I went through with this ... I assume I would have to ground the camera to the car so that ground would be common in order to utilize the ground pulse from the SD log beginning??? Is that so ?

[elaw]

That's correct... although if the camera is powered via an adapter from the car's electrical system the adapter might provide a ground path.

If you're using an adapter, before you go any farther it would be a good idea to measure voltage (while powered from the car) between the camera's ground and the car's ground to ensure that they're the same.

[coizamora]

That´s great!
My megaview finally work in deg C!!!
Tks a lot!!!

[JAM]

Allow cam polarity to be flipped on custom decoders. (Tested some modes.)
Ungrey cam poll polarity for GM7X. (Was being used already.)

this seems to be working great !

this has allowed the implementation of VVT on this engine, thanks!

[tpsretard2]

hello all.

I am trying to find out what changes were made that will affect the Antilag from pre-1.4 alpha 1 to this pre-1.4 alpha 5 release.

The als in this one is almost unusable. i get the retard and i get fuel and spark cut, but it is almost as is the spark limiting code is different. will not hold boost no matter what i do.
The reason i ask about the limiting code is the limit dos sounds very slow and random instead of clean and constant.

[jsmcortina]

[tpsretard2]

Storm finally left for long enough that i could take the car to the track and see what was happening.

I have found the problem. well, what is causing it, all though the maps are the same the alpha 5 fimware gives a lot more retard. It is not a problem i just need to retune the tables.
I just don't know now if it is a bug, so when you can please look at it.

[jsmcortina]

In a recent release I allowed full retard, earlier releases had been limited to -10. Perhaps that is what you were seeing?

James