Hi Diego,
I am having the same problem, can't get the TOGA to work :-(. Testing my throttle with PM, Flightdecksolutions MCP and using phidgets all the way around. Any help is very appreciated :-). Thanks!!!
Printable View
Hi Diego,
I am having the same problem, can't get the TOGA to work :-(. Testing my throttle with PM, Flightdecksolutions MCP and using phidgets all the way around. Any help is very appreciated :-). Thanks!!!
Hello there,
I have Simparts throttle and the TOGA button is assigned as below to Fs2Phidgets:
[AUTO_THROTTLE_TOGA]
Offset=080C
Length=4
FSType=Digital
OffValue=0
OnValue=1
Everything is wokring normal, when i press TOGA button (just a simple push-button) the TOGA mode is engaged and the auto-trottle moves the thust levers fwd. I don't have the TOGA button connected to CpFlight's MCP Pro input, but via offset it works the same.
Regards
Eddie
Potroh,
i'm using Project Magenta !!
Maybe all the offsets i'm using are different, i have to check again.
For which offset you want to me to check?
Eddie
Eddie,
That's strange.
Project Magenta is NOT using the default 080C offset for toga at all.
In fact as many people fly PM without a panel it wouldn't have any use either, as PM also disables the default AT armed switch at 0x810, so no way the default TOGA could be invoked by.
What plane do you use?
regards
Potroh
Hi Potroh,
If you are using project magenta and have specified PROJECTMAGENTA=1 in the dvatx.ini then dvatx looks at offset 04F0 to compute its autothrottle logic. I check bits 9 -SPD, 10 - THR, 11 - AT, 14 - VNAV. If bit 11 is set to 1 and any of the other bits are set to one then the servos will power.. I personally dont use PM so im not sure how the TOGA works. I assumed that PM would envoke N1 when the TOGA was pressed. If you can let me know what values and offset change when TOGA is used in PM.. im happy to modify the program for you.. BTW i have posted version 1.16 on the board that has some additional features plus bug fixes..
Cheers
Diego
Hi Diego,
Is is possible to download the file from an alternate location? Tried the MC download library and just kept getting an error :(. Thanks!!!
Sorry my mistake, i was looking an ini file, which contains many offsets :-(
The correct offset is 04F2
Here is the ini :
[PMTO/GA]
Offset=04F2
Length=2
FSType=Digital
OnValue=121
Multiplier=1
Divisor=1
Integer=True
NormalizeAngle=False
WriteOnly=False
Format=0
OffValue=0
Copy from Pm's site for 04F2
MCP/FCU Throughpass (See MCPcodes at the end) (Read/Write)
Example: Write Value 33 to engage AP2 (K033 ELAN Code). Once read, the MCP resets the value to 0 and is ready for another read.
Only last three digits are used, you can use the thousands to indicate the key has been pressed again (state change), i.e. 4033 and 7033 do the same
Use 121 for TOGA (without N1)
DisableRemoteMCP must be set to OFF in the INI file for this to work.
I wish this will help you
Eddie
Hi Diego,
No, Project Magenta - fortunately - doesn't invoke N1 with the TOGA. That would be rather unrealistic.
Hence - just as Eddie quoted above:
It can be done either by writing a value of 121 to 0x04F2
or 0x050A bit 0
and 0x051C bit 2 does the same
- if I'm not mistaken.
Only 050A is writable.
So as a solution I guess either or both would be just perfect for us who use PM.
I think a single future entry in the ini file would do it for us, so could try both offsets if needed.
BTW, I wanted to drive my toga switch via DVATX, but as you don't accept bit in the ini, only bytes, it was not possible for the above mentioned reason.
Oh yes, and I'm also unable to download the new file.
thanks and eagerly waiting
Potroh
Eddie,
So finally you use 04f2, that's very different, now I understand why it works for you.
regards
Potroh