Flávio Oliveira Posted Thursday at 11:19 AM Report Posted Thursday at 11:19 AM Hello everyone! I recently purchased the A321 from FSLabs and I'm having trouble configuring my X-56 Logitech using FSUIPC7. I've tried to find the events on the Hubhop website, I've searched the FSUIPC7 presets, and nothing! I noticed that each of the aircraft's controls appear in the FSUIPC7 console log, see the screenshot below. On the PMDG 737, I take the number that appears in the console log and add 69632 to get the "Custom Code" to operate a function. Can I do this with the A321 FS? Can I assign a function to my Joystick using only the information I receive from the console? I'd appreciate it if you could help!
John Dowson Posted Thursday at 01:01 PM Report Posted Thursday at 01:01 PM 1 hour ago, Flávio Oliveira said: On the PMDG 737, I take the number that appears in the console log and add 69632 to get the "Custom Code" to operate a function. Yes, with the PMDG aircraft you can use either custom control numbers (preferred) or the Rotor Brake control method - there are FAQ entries for each method. 1 hour ago, Flávio Oliveira said: Can I do this with the A321 FS? Can I assign a function to my Joystick using only the information I receive from the console? I don't know if the FSL aircraft support custom controls (I will check when I have time), but if the Rotor Brake controls are logged, then I would try assigning to those, using the parameter logged. Please just try this to see if it works and let me know. If not, let me know one button/switch that you are trying to assign and I will look into that here. John
John Dowson Posted Thursday at 04:21 PM Report Posted Thursday at 04:21 PM I just took a look at the FSLabs A321 and tested the Captain EFIS ND Mode switch, which uses the Rotor Brake control with parameter 71026 for a clockwise turn and 71027 for an anti-clockwise turn. Assigning to this in FSUIPC also controls the switch in the same way. So yes, you can use the Rotor Brake controls with the parameters you see logged.
Flávio Oliveira Posted Thursday at 06:51 PM Author Report Posted Thursday at 06:51 PM Thank you very much John for your answer. And did you find these numbers "71026" and "71027" in the FSUIPC7 console? In the image I sent I was trying to assign the taxi light. The console gave me the parameter "72510" and I was wondering if that was what I should include in the FSUIPC7 Custom Code. Excuse my ignorance, if you could guide me better on the first one I can do the others. Thanks
John Dowson Posted Thursday at 06:57 PM Report Posted Thursday at 06:57 PM Just now, Flávio Oliveira said: And did you find these numbers "71026" and "71027" in the FSUIPC7 console? Yes - they were logged when I turned the Captain EFIS ND Mode switch, as I said. 1 minute ago, Flávio Oliveira said: In the image I sent I was trying to assign the taxi light. The console gave me the parameter "72510" and I was wondering if that was what I should include in the FSUIPC7 Custom Code. You assign to the Rotor Brake control and use 72510 as the parameter - that should then control the taxi lights. I didn't yest/check that as you did not mention that this was for the taxi lights. 4 minutes ago, Flávio Oliveira said: Excuse my ignorance, if you could guide me better on the first one I can do the others. It is straightforward - whatever you want to assign, operate in the VC, see what is logged and then assign to that. In most cases it will be a Rotor Brake control with a parameter, so assign to the Rotor Brake control and use the parameter logged. John
Flávio Oliveira Posted Thursday at 07:42 PM Author Report Posted Thursday at 07:42 PM Good afternoon, Jonh. For you as a developer, this should be a very simple task. In my case, since I don't understand anything about programming, it's already quite complicated. What am I trying to do? 1) I put the parameter "72511" in Custom code in FSUIPC7, which was the number I found in the console when I clicked on the taxi light. 2) I assigned the number 1 to the parameter field, which I believe will turn on the light. I'll send you another print of my configuration. If possible, tell me if I'm doing it correctly, because it's not working this way. !!!(Yes, I got confused with the numbers "72511" is the taxi light parameter) Thank you.
Flávio Oliveira Posted Thursday at 07:59 PM Author Report Posted Thursday at 07:59 PM (edited) I tried this too and it didn't work: Edited Thursday at 08:02 PM by Flávio Oliveira
John Dowson Posted Friday at 08:07 AM Report Posted Friday at 08:07 AM 11 hours ago, Flávio Oliveira said: In my case, since I don't understand anything about programming, it's already quite complicated. This is nothing to do with "programming". It is assigning to the logged FS control/event with the logged parameter. 11 hours ago, Flávio Oliveira said: What am I trying to do? 1) I put the parameter "72511" in Custom code in FSUIPC7, which was the number I found in the console when I clicked on the taxi light. 2) I assigned the number 1 to the parameter field, which I believe will turn on the light. I don't know why you tried this - that obviously won't work. There is no SDK for the FSLabs and therefore no custom controls. It may be possible to use custom controls, but you would have to determine the control number and it certainly will not be the parameter used via the Rotor Brake control. Please re-read my previous comment as it looks like you did not understand this at all: 12 hours ago, John Dowson said: You assign to the Rotor Brake control and use 72510 as the parameter - that should then control the taxi lights. I didn't yest/check that as you did not mention that this was for the taxi lights. I said use parameter 72510 as you said this was logged when you use the taxi light switch in the VC. 11 hours ago, Flávio Oliveira said: I tried this too and it didn't work: Why are you using 72511 when you said this was 72510? When I move the Nose light switch from Off to Taxi, I see this logged: Quote 2065734 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 72512 (0x00011b40) ROTOR_BRAKE 2065891 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 72514 (0x00011b42) ROTOR_BRAKE and moving back, I see this: Quote 2206750 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 72511 (0x00011b3f) ROTOR_BRAKE 2206906 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 72513 (0x00011b41) ROTOR_BRAKE I am not sure why 2 controls are logged, but assigning to the Rotor Brake control with parameter 72512 moves the Nose light switch up, and assigning to 72511 moves the nose light switch down. So try that. If that works, you can just leave it at that. However, as two controls are logged when you move the switch in the VC, I would replicate this in the assignments. How you do this depends on what you are assigning to. The easiest way, if using a momentary push-button, would be to assign using one parameter for the press and another to the release, with both using the Rotor Brake control. The other way of doing this is overloading (i.e. having more than one assignment on a button) via editing the FSUIPC7.ini file. Assign the button press to the first control, save (press OK), and then open your ini file in an editor. Then open the button assignments panel again in FSUIPC7. Locate the assignment just made - it will look something like this (the index number may vary, as well as the button used) 4=PB,10,C66587,72512 -{ROTOR_BRAKE}- Duplicate this line, and give the new entry a unique index number and change the parameter, i.e. 4=PB,10,C66587,72512 -{ROTOR_BRAKE}- 5=PB,10,C66587,72514 -{ROTOR_BRAKE}- Save the changes, and then in FSUIPC7 click Reload all buttons. You then have two assignments on the same button, but you will not see this in the UI. John
John Dowson Posted Friday at 09:50 AM Report Posted Friday at 09:50 AM (edited) It also may be easier to use macros, which are another method of sending multiple controls/events. Save this attached file to your FSUIPC7 installation folder (before running FSUIPC7, or restart FSUIPC7 after installing): FSLA321.mcro Then start FSUIPC7, and assign your buttons/switches to FSLA321: Nose Swtch Up - to move the switch up FSLA321: Nose Swtch Down - to move the switch down You can then add other macros to the same file to control other switches. I have added Strobe and Beacon. John P.S. The Beacon switch controls seem to act like a toggle, so sending the Up when in Up position moves the switch down, and vica versa. So you only actually need one macro for this switch. Just FYI. Edited Friday at 11:27 AM by John Dowson Changed names, added Strobe and Beacon lights
John Dowson Posted Friday at 10:50 AM Report Posted Friday at 10:50 AM I have moved this topic to the FSUIPC7 sub-forum. Please use this sub-forum for all FSUIPC7 support.
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