allan.kidd@optusnet.com.au Posted January 30, 2021 Report Share Posted January 30, 2021 The FSUIPC.ini with the error section [Buttons.LearJet35A] 0=R2,3,C65792,0 -{AUTOPILOT_ON}- 1=U2,3,C65792,0 -{AUTOPILOT_ON}- 2=P2,2,C65596,0 -{THROTTLE_FULL}- 3=P2,20,C68086,0 -{BEACON_LIGHTS_ON}- 4=P2,21,C68087,0 -{BEACON_LIGHTS_OFF}- 5=P2,23,CM10:6,0 -{Macro LearJet35A: LandLightOFF}- 6=P2,26,C68089,0 -{NAV_LIGHTS_ON}- 7=P2,27,C68090,0 -{NAV_LIGHTS_OFF}- 8=P2,28,C66052,0 -{STROBES_ON}- 9=P2,29,C65560,0 -{STROBES_TOGGLE}- 10=P2,22,CM10:5,0 -{Macro LearJet35A: LandLightON}- 11=P2,24,CM10:5,0 -{Macro LearJet35A: LandLightON}- 12=P2,25,CM10:6,0 -{Macro LearJet35A: LandLightOFF}- 13=CP(+64,20),P64,12,CM10:7,0 << ERROR 19! Line ignored >> 14=CP(+64,20),P64,13,CM10:8,0 << ERROR 19! Line ignored >> 15=CP(+64,16),P64,12,CM10:1,0 << ERROR 19! Line ignored >> 16=CP(+64,16),P64,13,CM10:2,0 << ERROR 19! Line ignored >> 17=P0,12,CM10:9,0 -{Macro LearJet35A: CRSInc}- 18=P64,13,CM10:2,0 -{Macro LearJet35A: IASDown}- 19=P64,12,CM10:7,0 -{Macro LearJet35A: AltInc}- Lines 13 through 16 are to program the 2 rotary keys on the Honeycomb Bravo - 64,20 is the the altitude selector while 12 is the increment dial. 64,16 is the IAS selector and 14 is the decrement direction. Error 19 in the manual: "19 The C.r Kor M needed for Control, Key or Macro is missing" I have included the Macro file 10 below. Macro file 10 does have macros 1,2,7 & 8. This is evidenced by line 19 in FSUIPC.ini above (19=P64,12,CM10:7,0 -{Macro LearJet35A: AltInc}-) which does not have an error. Suggestions appreciated!! Macro file 10: [Macros] 1=IASUp=RX400000fb,1 2=IASDown=RX400000fb,3 3=ALTUp 3.1=RX4000010c,1 3.2=RX4000010c,1 4=ALTDown 4.1=RX4000010c,3 4.2=RX4000010c,3 5=LandLightON=RX400000cd,3 6=LandLightOFF=RX400000cd,1 7=AltInc=RX4000010c,14 8=AltDecr=RX4000010c,15 9=CRSInc=RX4000014e,1 10=CRSDecr=RX4000014e,3 11=HEADInc=RX4000014d,1 12=HEADDecr=RX4000014d,3 Allan Link to comment Share on other sites More sharing options...
allan.kidd@optusnet.com.au Posted January 30, 2021 Author Report Share Posted January 30, 2021 Whooops - found my problem. I had put a comma after the condition that was not the correct syntax. The error code threw me. Allan Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now