SE-LSU Posted September 29, 2013 Report Posted September 29, 2013 Dear Colleagues, I have done my mest in trying to comply to both Pete Dowson's and Gunter Steiners quite-easy-to-follow instructions of how to connect VRInsight equipment to FSUIPC. The thing is that I, among other things, would like the Autopilot to hold altitude when I press the ALT knob at my Radiostack. Now it is trying to catch another unknown altitude. I am close but I am not there yet. In the attached file I have put together some (hopefully all that is needed) log information. Perhaps some of you more experienced FSUIPC-people can see what is wrong, and help me to reach the finnish line. Thanks in advance /SE-LSU
Pete Dowson Posted September 29, 2013 Report Posted September 29, 2013 You don't say what assignments you are making in FSUIPC. All you are shoing is a trace of VRI commands and replies. Are you using FSUIPC just to change the action for some of the commands? Have you tried assignment to whatever button number appears when you press the ALT hold button? Pete
SE-LSU Posted September 29, 2013 Author Report Posted September 29, 2013 Hi Pete and thank you for your very quick answer. When I am trying to make the connection by making a "new assignment" to the "Autopilot attitude hold"-event, and click on the "ATT"-button on the radiostack, as I usually do by clicking at a keyboard or Joystick-button, nothing happens. No button number shows at all. Since some information lacks, if I compare my log file with your example in Appendix 3, .eg. "from Device" and "from VRI driver", I suspect that some link in the chain is broken. /LSU
Pete Dowson Posted September 29, 2013 Report Posted September 29, 2013 When I am trying to make the connection by making a "new assignment" to the "Autopilot attitude hold"-event, and click on the "ATT"-button on the radiostack, as I usually do by clicking at a keyboard or Joystick-button, nothing happens. No button number shows at all. ATT? Do you mean ALT? I've never had a Radio Stack here. My code should recognise it, thanks to help from users who have it, but it only handles these codes from that device (the numbers after the // are the joystick/button number assigned, which you should see). "TRNVFR", // 274,0 "TRNx1200", // 274,1 "TRNIDEN", // 274,2 "TRNON", // 274,3 "TRNSTBY", // 274,4 "APLMST", // 274,5 "APLHDG", // 274,6 "APLNAV", // 274,7 "APLLOC", // 274,8 "APLBCRS", // 274,9 "APLALT", // 274,10 "APLTHR", // 274,11 "APLFD", // 274,12 Don't you see any of those button numbers appearing in the Buttons & Switches tab when you operate those buttons? You should do. Since some information lacks, if I compare my log file with your example in Appendix 3, .eg. "from Device" and "from VRI driver", I suspect that some link in the chain is broken. What parts do you see missing? Pete
SE-LSU Posted September 29, 2013 Author Report Posted September 29, 2013 ATT? Do you mean ALT? - Yes. Don't you see any of those button numbers appearing in the Buttons & Switches tab when you operate those buttons? If you mean the attached "New Assignment" dialogue box - No, Nothing Happens. What parts do you see missing? 1. My arrows are just in one direction while they in the example in Appendix 3 (see the second attachment) are in two directions. 2. I have no "from" as there is in Appendix 3 (same attachment). SE-LSU
Andydigital Posted September 29, 2013 Report Posted September 29, 2013 Why are you looking in the default controls assignment interface in FSX, you need to be looking inside FSUIPC in the Addons menu!!
SE-LSU Posted September 29, 2013 Author Report Posted September 29, 2013 Aha! - Now something happened! Contact is established! However, I have yet some work to do before I'm finnished. Pete and Andydigital thanks for now, really appreciate your help. SE-LSU
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