Mag's OSE 12P Thread

[vn5000]

Yeah Mag you got it. Ive used it and it works fine , not sure how vl400 did it though ,he must have written two aldl write routines in different areas of the code.
Also if youve been using the same bin for a while and are having unexplained problems it may have been corrupted - has happened to me before.
Try not migrating the bin you are using to v104 instead start again using tp5 compare \ copy.

[VL400]

There is some protected code that always stays (can be updated via the flashtool if need be). I was going to make it load into RAM like the VX/VY but did not think it would fit in the 808s limited space but as it turns out would have fitted easily, may change it in future but it works as is.

[vn5000]

Am i right in thinking that if you loaded the protected code into ram then you could use the 808 to program any bin ie not 12p but say two stacked 16 k bins or bigger bins with an adapter to switch address pins, just for an example , onto a nvsram

[mag]

vn5000 I had forgotton about migrating old cal to new, glad you mentioned it but you have lost me regarding using TP compare/copy. Could you add more details for the dummy.

[vn5000]

Say you want to copy your old ve table onto new bin , then bring up ve table in tp5 and hold mouse button to highlight all cells then select copy from compare (set up old bin as compare bin) and execute .
Doesnt take to long unless youve got a lot of mods.

[VL400]

Am i right in thinking that if you loaded the protected code into ram then you could use the 808 to program any bin ie not 12p but say two stacked 16 k bins or bigger bins with an adapter to switch address pins, just for an example , onto a nvsram

It would still initially require code (say 12P) loaded to the NVRAM to be able to boot the 808 and then invoke the RAM loader from the flashtool over the ALDL link. Could then potentially program any 32k or smaller bin to the NVRAM but your gonna need a programmer to begin with

[Holden202T]

have a look at the new baro settings in the version info thread, might be something in there you need to set/change.

[mag]

Just ware I have have started to look. VL400 post regarding v104 changes gave me impression that "use altitude adjusted map load variable as load variable" is default & thus should be set, not set in my migrated cal it is clear. Have I misunderstood his post.

Also noticed that all versions of TP5 RT interpret "tip-in bump spark vs TPS vs RPM......." differently to TP. Same equation, same values, same everything as far as I can tell yet different presentation. Have I goofed or is there a problem that should be reported.

Also have surging on very small throttle openings, any suggestions, other than avoiding small throttle openings.

[yoda69]

From my experience with TP5 I've noted that a lot of tables are inverted compared to TP4.
All the information is correct however.
Where you need to be careful is when using Excel to manipulate data between TP4 and TP5, as the tables are inverted.

yoda69

[Holden202T]

can't really speak for TP5 because i use TP4 for editing but i'd be weary of it ....

if you use the v1.04 base v6 cal that comes with v1.04 pacvkage then it will have the settings as VL400 suggests, but if you are migrating they will not be populated and will require checking .... i'd compare your bin to the v1.04 v6 base file and see whats different and if they are empty or different maybe change them to the vr numbers.

as far as surging .... too lean maybe, anythings possible, without a log its hard to say really.