Mag's OSE 12P Thread

[ToyHicko]

Not 100% sure on the question at hand but I believe the answer is Yes and Yes.

Yes Realtime changes are capiable with the NVRAM in TP5 using the plugin the Plugin allows for Emulation and data login at the same time with TP5.

Yes the save parameter button updates the scalar values and flags the tables are a little different just can't remember off the top of my head the button/option.

Here what Holden202 stated in the plugin thread

another thing to add for those that arn't aware.

when you are emulating, if you open a table and change something you need to hit the update button at the top of the table for it to update.

so if you wanted to update more than one cell, do all that, then hit update and it will update the whole table changes in one go!

Hope this helps

[mag]

Took a while but the dummy got it all working, thanks for the assistance all. Hopefully final question on this subject, why would TP5 show "Hardware: OSE12 Pro v1.1.0" if I have successfully installed v112. TP5 Preferences/Data Acq./Emulation shows "OSE Plugin v1.1.2" as the options.

[Holden202T]

normally what i do, is load TP5, it detects my hardware at startup, then make sure i have the right xdf adx and bin loaded for the ecm im connected to, then tick emulate, then the download arrow (to download the bin to emulator) then away i go changing stuff / logging etc.

[VL400]

Hopefully final question on this subject, why would TP5 show "Hardware: OSE12 Pro v1.1.0" if I have successfully installed v112. TP5 Preferences/Data Acq./Emulation shows "OSE Plugin v1.1.2" as the options.

Have a think about it ... think about whats running in the ECM (and the name of this thread) and the version of plugin software (and the name of that thread) ....

[mag]

I said I was a dummy, thanks VL400. And thnks also Holden202 for confirmation that my setup is correct.

[mag]

Here is the first question on my own thread.

From habit I tend to do start/stop logging using TP5, by this I mean running TP5 logging up to a point in time, then stopping the logging, saving to file & then placing the laptop in standby. After a period of time I will bring the laptop out of standby or hibernation & start another logging session, to be stopped again, saved etc. This process may be repeated a number of times.

When I go to replay the log records, other than for the first record, all the record data is located at the end of the record period. There is no data at the beginning, the size of the blank area is dependant on the duration of time for which the laptop was in standby with TP5 running but not recording. It appears as though an elapsed time timer within TP5 has kept running between recordings. Also TP5 log record length appears to be limited to 60 minutes & then rolls over to zero & starts again. No data is lost, just everything shifted in time.

Hope my description of the issue makes sense. Is my log recording procedure faulty, perhaps my laptop not up to the task of running TP5 or this is normal TP5 operation.

[mag]

Now for a baro pressure question. Flag set for update while engine is running but have yet to find a log that shows same. Baro pressure remains at value measured at ignition ON, right through the run & only changes after engine stopped & restarted. Any suggestions.

[Holden202T]

i never put my machine into standby because it is effectively still running .... i do however ALWAYS use hibernation..... having said that i save the log and stop the aldl polling ..... maybe thats your issue, try disconnecting the aldl polling before hibernating etc and see if that fixes the issue.

[mag]

Thanks Holden202, I do as you do up to the point where you use hibernation. I have been using standby & my laptop would only go into hibernation after too long in standby. I will try hibernation, if in standby TP5 is still running then this might explain the long time frames without log data.

[antus]

regarding the baro, the value is recorded from the map at key on, before the engine starts, after that it cant tell the difference between engine load and atmospheric pressure. you wont see it change with the engine running.