sisoffi

thankyou Roman, but in the axis assignement the offset is correct word offset or not? in sioc script is $66D0 and in the fsuipc lien is : x020066D0,

Hi Pete, I'm working on a real ASI instruments of maddog. The script made by the previous owner is adapted on a pot range of 0-4096 that he himself had modified in the ini file (and not from the nominal -16k to + 16k). The previous owner not remembering the change from faer in fsuipc.ini, can you tell me how do I assign the range 0-4096 to the pot? The Delta need to low value 32 from 256. what does this lower set value mean? now is : [Axes] PollInterval=10 RangeRepeatRate=10 0=2X,256,F,x030066D8,0,0,0 -{ FSUIPC: offset dword set, offset 66D8 }- ASI SPEED 1=2Y,256,F,x020066D0,0,0,0 -{ FSUIPC: offset word set, offset 66D0 }- SALMON BUG 2=2Z,256,F,x030066D4,0,0,0 -{ FSUIPC: offset dword set, offset 66D4 }- BARBER POLE thank you Simone in attach script from sioc. G_ASI.txt

yes, the maddog has released all fsuipc offset, but the problem is the same. I need to intercept the functions write on onl .mco file with the skalarki interface. But somtehing is write in his internal code and difficult to bypass :(. Just switch to mobiflight and arduino and you're done. It was just not to throw away valuable and paid cards at the time

about this? do you have any idea? is not pmdg but the new maddogX

about this? do you have any idea?

one question: Fired through FSUIPC Control: 69919, Parameter: 16777217 16777217 ...what is this parameter?

Hi Pete, I discovered that the toggle switch is not replicated by the TAB test. Also in the example APU MASTER 3 positions OFF RUN and START. from off to run I click the mouse once (click-type 3) or turn the wheel (click-type 15). The moment I do the test it goes to the Start position (it still increases the click and that's fine). from Run to off (clicktype1 or 14). Now if I press the left mouse once the toggle switch goes into start and immediately into run (clicktype 3) while if I turn the mouse wheel (cliktype15) it stays in start. But if I do the TEST of the latter, it does not release remains in start.

Pete, I have tried many combinations. First of all, replace the old parameters 11 and 17 with the new ones. I also tried other combinations of parameters (the left mouse click is momentary and corresponds to 13) but nothing to do I do not understand why the switch does not return to neutral. In any case, the combination works and go in momentary ON position, but nothing to do I do not understand why the switch does not return to neutral. 21=APU_MASTER_MIN=RX40000226,1422=APU_MASTER_PLUS=RX40000226,1523=APU_MASTER_START23.1=RX40000226,1323.2=RX40000226,16

i found the corresponding: 11 MOUSE_LEAVE (fuispc4) = 16 Leave (fsuipc5) 17 MOUSE_LEFTRELEASE (fsuipc4)= 13 Left release so is corect so? 21=APU_MASTER_MIN=RX40000226,14 22=APU_MASTER_PLUS=RX40000226,15 23=APU_MASTER_START 23.1=RX40000226,16 23.2=RX40000226,13

Pete, I'm very confused, forgive me. So, in p3d if I click with the right mouse button I get parameter (3), left click on the mouse (1). If I move the mouse wheel 14 and 15. But what parameters should I use then? from the analysis of my file, both parameters work both if I put 14 in release and 15 in the click, that also 1 and 3. For all the switches I have the same problem on click 3 or 15 and on release 1 or 14 depending on what I press on the mouse (both work). I'm sorry but I just can't understand the logic of the macro function. 21 = APU_MASTER_MIN = RX40000226,14 or (1)22 = APU_MASTER_PLUS = RX40000226,15 or (3)23 = APU_MASTER_START = RX40000226,3 or (15) in any case, the problem remains for all momentary ON switches because in my interface program there is a function on click release programmed on old file with special string line macro: 23 = APU_MASTER_START= 23.1 * RX6c180 X81cc, 11= 23.2 * RX6c180 X81cc, 17 I have only one possibility to interface my switches on the I board with the damn software owned by the author with the indication that we have in the old profile. How would you write the Master Apu macros on the new file? can you give me an example? I would thank you very much. thank Simone

I follow the documentation and is the same of old macro. But now, what is the correct, parameter to assign in te new .mco ? <mouseflag> part provides the actual mouse action required to operate the facility. This is encoded as a number, one of those listed below (but note that some of these will probably never be seen in relation to such regions!): 1 Right single click 2 Middle single click` 3 Left single click 4 Right double click 5 Middle double click 6 Left double click 7 Right button & drag 8 Middlebutton & drag 9 Left button & drag 10 Move 11 Right elease 12 Middle release 13 Left release 14 Wheel up 15 Wheel down 16 Leave 17 Count

thank you pete for the explanation. The MomON is refer to the switch n the Momentary ON position :)

no pete, macro dont change for the moment now the system is stable.

if you followed another post you could find here in attach. Is work for readouts fgcp and some other outputs. For the input there are no problems you can assign in mobiflight inputs via Macro (better) or eventID from command list provided by MaddogX Team. Maddog_X FGCP.zip