nbworld Posted April 16, 2012 Report Share Posted April 16, 2012 Hi, In need some help... i'm trying to get the offset for programming Cpflight Ics system. I just get the hex data on the advanced serial port monitor but i cannot finf the solution for cenvert/get the offset data. For example... for autobrake RTO -> 4D 49 50 43 4F 4D 35 5F 30 00 Please help. Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 16, 2012 Report Share Posted April 16, 2012 I just get the hex data on the advanced serial port monitor but i cannot finf the solution for cenvert/get the offset data. For example... for autobrake RTO -> 4D 49 50 43 4F 4D 35 5F 30 00 That's not actually binary data, it is a character string reading "MIPCOM5_0". I think you'll need a table of all the string values you receive, and look them up to determine their function. Pete Link to comment Share on other sites More sharing options...
nbworld Posted April 16, 2012 Author Report Share Posted April 16, 2012 Hi Pete, Ok is true, i'm trying to get the offset to put in prosim737 on the fsuipc 8 bit U but i only get the "MIPCOM5_0" FOR Autobrake RTO, on Cpflight dont have the correct offsets or the fsuipc values. Have you find a way to do so ? Thanks Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 16, 2012 Report Share Posted April 16, 2012 Ok is true, i'm trying to get the offset to put in prosim737 on the fsuipc 8 bit U but i only get the "MIPCOM5_0" FOR Autobrake RTO, on Cpflight dont have the correct offsets or the fsuipc values. Have you find a way to do so ? Sorry, I don't understand the question. If you want FSUIPC offsets relating to FS aircraft then these are all listed in the Offsets lists provided with the FSUIPC SDK. If you want offsets relating to an add-on, assuming the add-on even uses offsets, then you'll need the list from the add-on maker or support. I know Project magenta fully documents their offset use, Have you checked ProSim documentation? I've no idea what cpFlight has to do with it I'm afraid, nor where the string you are reading on a serial port comes into all this. Regards Pete Link to comment Share on other sites More sharing options...
nbworld Posted April 16, 2012 Author Report Share Posted April 16, 2012 Pete, I explain in detail. I have a Complete Mip off engravity based on cpflight ICS system. On prosim all switch's and bottons work 100%. But when to work with TRS autobrake the system don't work. I need to cancel inside the autobrake system when put manually a fsuipc value for this to work... the problem is that i don't have the fsuipc value to work with csflight hardware. On site the cpflight refer on sdk the numbers that i have but don't the fsuipc values. For Autobrake set i only have this: MIPCOM5_0 - RTO MIPCOM5_1 - OFF MIPCOM5_2 - 1 MIPCOM5_3 - 2 MIPCOM5_4 - 3 MIPCOM5_5 - MAX Thanks Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 16, 2012 Report Share Posted April 16, 2012 But when to work with TRS autobrake the system don't work. I need to cancel inside the autobrake system when put manually a fsuipc value for this to work... the problem is that i don't have the fsuipc value to work with csflight hardware. On site the cpflight refer on sdk the numbers that i have but don't the fsuipc values. The FSUIPC offset for the autobrake switch is listed in the FSUIPC offsets list. That is for FS aircraft. I think TSR has its own autobrake system, though, so you might need to refer to its documentation. And some add-on aircraft will be different again -- e.g. PMDG. The FS one is 2F80, one byte, value 0-5, matching your strings. I don't understand why you couldn't find it. Just search on the word "autobrake".! Pete Link to comment Share on other sites More sharing options...
nbworld Posted April 16, 2012 Author Report Share Posted April 16, 2012 Ok Pete, I know this offsets but tsr Offset 2F80 (normal FS2004 Offset) and for fsx the Offset is 6DB1. The main problem is to adquire the offset for the switch for Cpflight Ics system for then put the offset 6DB1 in fsuipc. If i go put the offset by key no problem... but for my system... i go talk with guys from prosim & cpflight. Thanks. Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 16, 2012 Report Share Posted April 16, 2012 The main problem is to adquire the offset for the switch for Cpflight Ics system for then put the offset 6DB1 in fsuipc. Sorry, that makes no sense at all to me. Why is cpFlight using a different offset to everything else? How can cpFlight hope that its users can operate the Autobrake if their switch is programmed to operate via an offset which isn't used by anything else? Regards Pete Link to comment Share on other sites More sharing options...
nbworld Posted April 17, 2012 Author Report Share Posted April 17, 2012 Peter, The main problem is that the ICS system of cpflight have a different way internally to communicate, for put the offsets out it's the same of all but for fsuipc grab the switch of ICS you just can't (today). If you can grab the switch's of ICS system then the problem is over... Can you get the bottons/switch's work it ICS ?. If you look at this address http://www.cpflight.com/sito/sdk/sdk.asp , you see that the comms internally of activate the rotary/bottoms have a way of cpflight. When you put the joystics/yock's etc. grab the cooms on fsuipc you will see, but on ICS system i can't. If you please make connect like the other's makers... saitek...etc. Link to comment Share on other sites More sharing options...
nbworld Posted April 17, 2012 Author Report Share Posted April 17, 2012 Hi Pete, If i go log the axis controls i found this... Switch Autobrake 1 2690081 System time = 17/04/2012 11:14:20, Simulator time = 11:13:56 (10:13Z) 2703762 *** AXIS: Cntrl= 66387 (0x00010353), Param= -14254 (0xffffc852) AXIS_LEFT_BRAKE_SET 2703762 *** AXIS: Cntrl= 66388 (0x00010354), Param= -14254 (0xffffc852) AXIS_RIGHT_BRAKE_SET 2703762 *** TOE BRAKE AXIS, Left set = 0 (IN=-14254, OUT=-16383) 2703762 *** TOE BRAKE AXIS, Right set = 0 (IN=-14254, OUT=-16383) 2703762 *** Both toe brakes off ... Release Armed 2703887 *** AXIS: Cntrl= 66387 (0x00010353), Param= -11960 (0xffffd148) AXIS_LEFT_BRAKE_SET 2703887 *** AXIS: Cntrl= 66388 (0x00010354), Param= -11960 (0xffffd148) AXIS_RIGHT_BRAKE_SET 2704012 *** AXIS: Cntrl= 66387 (0x00010353), Param= -9666 (0xffffda3e) AXIS_LEFT_BRAKE_SET 2704012 *** AXIS: Cntrl= 66388 (0x00010354), Param= -9666 (0xffffda3e) AXIS_RIGHT_BRAKE_SET 2704137 *** AXIS: Cntrl= 66387 (0x00010353), Param= -7373 (0xffffe333) AXIS_LEFT_BRAKE_SET 2704137 *** AXIS: Cntrl= 66388 (0x00010354), Param= -7373 (0xffffe333) AXIS_RIGHT_BRAKE_SET 2704277 *** AXIS: Cntrl= 66387 (0x00010353), Param= -5079 (0xffffec29) AXIS_LEFT_BRAKE_SET 2704277 *** AXIS: Cntrl= 66388 (0x00010354), Param= -5079 (0xffffec29) AXIS_RIGHT_BRAKE_SET 2704386 *** AXIS: Cntrl= 66387 (0x00010353), Param= -2786 (0xfffff51e) AXIS_LEFT_BRAKE_SET 2704386 *** AXIS: Cntrl= 66388 (0x00010354), Param= -2786 (0xfffff51e) AXIS_RIGHT_BRAKE_SET 2704511 *** AXIS: Cntrl= 66387 (0x00010353), Param= -492 (0xfffffe14) AXIS_LEFT_BRAKE_SET 2704511 *** AXIS: Cntrl= 66388 (0x00010354), Param= -492 (0xfffffe14) AXIS_RIGHT_BRAKE_SET 2704652 *** AXIS: Cntrl= 66387 (0x00010353), Param= 1802 (0x0000070a) AXIS_LEFT_BRAKE_SET 2704652 *** AXIS: Cntrl= 66388 (0x00010354), Param= 1802 (0x0000070a) AXIS_RIGHT_BRAKE_SET 2704776 *** AXIS: Cntrl= 66387 (0x00010353), Param= 4095 (0x00000fff) AXIS_LEFT_BRAKE_SET 2704776 *** AXIS: Cntrl= 66388 (0x00010354), Param= 4095 (0x00000fff) AXIS_RIGHT_BRAKE_SET 2704886 *** AXIS: Cntrl= 66387 (0x00010353), Param= 6389 (0x000018f5) AXIS_LEFT_BRAKE_SET 2704886 *** AXIS: Cntrl= 66388 (0x00010354), Param= 6389 (0x000018f5) AXIS_RIGHT_BRAKE_SET 2704964 *** AXIS: Cntrl= 66387 (0x00010353), Param= 8682 (0x000021ea) AXIS_LEFT_BRAKE_SET 2704964 *** AXIS: Cntrl= 66388 (0x00010354), Param= 8682 (0x000021ea) AXIS_RIGHT_BRAKE_SET 2705073 *** AXIS: Cntrl= 66387 (0x00010353), Param= 10976 (0x00002ae0) AXIS_LEFT_BRAKE_SET 2705073 *** AXIS: Cntrl= 66388 (0x00010354), Param= 10976 (0x00002ae0) AXIS_RIGHT_BRAKE_SET 2705198 *** AXIS: Cntrl= 66387 (0x00010353), Param= 13270 (0x000033d6) AXIS_LEFT_BRAKE_SET 2705198 *** AXIS: Cntrl= 66388 (0x00010354), Param= 13270 (0x000033d6) AXIS_RIGHT_BRAKE_SET 2705322 *** AXIS: Cntrl= 66387 (0x00010353), Param= 15891 (0x00003e13) AXIS_LEFT_BRAKE_SET 2705322 *** AXIS: Cntrl= 66388 (0x00010354), Param= 15891 (0x00003e13) AXIS_RIGHT_BRAKE_SET 2705463 *** AXIS: Cntrl= 66387 (0x00010353), Param= 16383 (0x00003fff) AXIS_LEFT_BRAKE_SET 2705463 *** AXIS: Cntrl= 66388 (0x00010354), Param= 16383 (0x00003fff) AXIS_RIGHT_BRAKE_SET Switch Autobrake to OFF 2921134 *** AXIS: Cntrl= 66387 (0x00010353), Param= 14744 (0x00003998) AXIS_LEFT_BRAKE_SET 2921134 *** AXIS: Cntrl= 66388 (0x00010354), Param= 14744 (0x00003998) AXIS_RIGHT_BRAKE_SET 2921134 *** TOE BRAKE AXIS, Left set = 180 (IN=14744, OUT=13104) 2921134 *** TOE BRAKE AXIS, Right set = 180 (IN=14744, OUT=13104) 2921134 *** Both toe brakes over threshold: FS BRAKES control sent 2921197 *** AXIS: Cntrl= 66387 (0x00010353), Param= 13106 (0x00003332) AXIS_LEFT_BRAKE_SET 2921197 *** AXIS: Cntrl= 66388 (0x00010354), Param= 13106 (0x00003332) AXIS_RIGHT_BRAKE_SET The others switch dont work On fsuipc option i cannot but the switch to work. Best regards, Nuno Link to comment Share on other sites More sharing options...
nbworld Posted April 17, 2012 Author Report Share Posted April 17, 2012 Hi Pete... again I look inside the cpflight directory and i see an DigitalIN.cfg. I grab this... "Autobrake rto","&H2f80",1,0,0,1 "Autobrake off","&H2f80",1,0,1,1 "Autobrake 1","&H2f80",1,0,2,1 "Autobrake 2","&H2f80",1,0,3,1 "Autobrake 3","&H2f80",1,0,4,1 "Autobrake max","&H2f80",1,0,5,1 Thanks, Nuno Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 17, 2012 Report Share Posted April 17, 2012 The main problem is that the ICS system of cpflight have a different way internally to communicate, for put the offsets out it's the same of all but for fsuipc grab the switch of ICS you just can't (today). If you can grab the switch's of ICS system then the problem is over... Can you get the bottons/switch's work it ICS ?. No. There is no way I can keep adding hardware drivers for every company that cannot be bothered to provide their own software. You must complain to cpFlight if they cannot make hardware which works with FS. What simulator are they providing it for if not FS? If you please make connect like the other's makers... saitek...etc. I do not support Saitek etc. I support standard Windows-compatible joysticks. Saitek etc make windows-compatible joysticks. If i go log the axis controls i found this... What have Axes got to do with an Autobrake switch? Nothing in your log relates to anything useful at all. If you want to see what switches do, you must log buttons, not axes. I look inside the cpflight directory and i see an DigitalIN.cfg. I grab this... "Autobrake rto","&H2f80",1,0,0,1 "Autobrake off","&H2f80",1,0,1,1 "Autobrake 1","&H2f80",1,0,2,1 "Autobrake 2","&H2f80",1,0,3,1 "Autobrake 3","&H2f80",1,0,4,1 "Autobrake max","&H2f80",1,0,5,1 So. What is that supposed to do? Seems like it is configured to use offset 2F80 which is correct for the FS Autobrake, doesn't it? So you have no problem! Check by Monitoring 2F80 as a U8 on the right-hand side of the Logging tab in FSUIPC. Check the FS window option below the list so you can see it in real time on screen. I don't understand what you want from me. It seems you need to get your cpFlight hardware supported by cpFlight. Don't they help? Pete Link to comment Share on other sites More sharing options...
nbworld Posted April 17, 2012 Author Report Share Posted April 17, 2012 Pete, The 2F80 With Hex selected ? Best regards, Nuno Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 17, 2012 Report Share Posted April 17, 2012 The 2F80 With Hex selected ? Doesn't matter whether you select hex or not. the numbers 0 - 5 are the same in decimal and hex! Pete Link to comment Share on other sites More sharing options...
nbworld Posted April 17, 2012 Author Report Share Posted April 17, 2012 Hi Pete, To close this section i have received this email that explain all... ICS does not use FSUIPC offsets but communicate directly with compatible software (this eliminates the need of an extra layer like FSUIPC and thus errors). As such, the ICS autobrake section can not be used with TSR autobrake which DOES need FSUIPC offsets. Thanks again. Nuno Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 17, 2012 Report Share Posted April 17, 2012 ICS does not use FSUIPC offsets but communicate directly with compatible software (this eliminates the need of an extra layer like FSUIPC and thus errors). As such, the ICS autobrake section can not be used with TSR autobrake which DOES need FSUIPC offsets. Odd, then, that they have the correct FSUIPC offset listed in one of their configuratin files. Oh, well. ... Pete 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