Problem getting button assignment to work

[Guest jcardana]

Sorry Mr. Dowson... I didn't think I'd be back so soon. This time it's not a HEX problem though. :D

I'm running Win2k SP1, Goflight Config v1.81 Build 83. FSUIPC 3.9 for FS9.

I have an RP-48 with 8 buttons assigned via FSUIPC. One of them is not working.

Could you please take a glance and make sure the code is correct. The only changes I did do to the FSUIPC.ini file was add the remarks. I added more remarks here to show which function I used "OFFSET BYTE"

FSUIPC ENTRIES
85=P175,0,Cx05003122,x80 ;    COM1 XMIT     |OFFSET BYTE SETBITS
86=P175,1,Cx05003122,x40 ;    COM2 XMIT     |OFFSET BYTE SETBITS     <----- This is my problem button
87=P175,2,Cx0D003122,x20 ;    COM 1/2 RCV   |OFFSET BYTE TOGGLEBITS
88=P175,3,Cx0D003122,x10 ;    NAV 1 IDENT   |OFFSET BYTE TOGGLEBITS
89=P175,4,Cx0D003122,x08 ;    NAV 2 IDENT   |OFFSET BYTE TOGGLEBITS
90=P175,5,Cx0D003122,x04 ;    MARKER BEACON |OFFSET BYTE TOGGLEBITS
91=P175,6,Cx0D003122,x02 ;    DME IDENT     |OFFSET BYTE TOGGLEBITS
92=P175,7,Cx0D003122,x01 ;    ADF IDENT     |OFFSET BYTE TOGGLEBITS

GFDISPLAY ENTRIES
[GFRP48.1]
Needs= B E
L0.1=x3122 U8 M0080 ; COM1 XMIT
L1.1=x3122 U8 M0040 ; COM2 XMIT
L2.1=x3122 U8 M0020 ; COM 1/2 RCV
L3.1=x3122 U8 M0010 ; NAV 1 IDENT
L4.1=x3122 U8 M0008 ; NAV 2 IDENT
L5.1=x3122 U8 M0004 ; MARKER BEACON
L6.1=x3122 U8 M0002 ; DME IDENT
L7.1=x3122 U8 M0001 ; ADF IDENT

I did the assignments within FSUIPC, (I did not mod the config manually accept for the remarks). The "Buttons + Switches" tab accurately shows Button#1 being pressed. Obviously since I wouldn't have been able to make the assignment if it didn't work. So the button itself does work.

When I select the COM2 Transmit button on the aircraft panel within FS, LED#1 on the RP-48 lights up. (that's why I included the GFDisplay code). So I know I have the masking correct. Everything else relating to the GFDisplay.ini works fine.

Pushing Button#1 has no affect. When I push Button#0, LED#1 goes off and the LED#0 lights up. All other buttons and LEDs work fine.

I verified the GFConfig has no assignments for the RP-48. Additionally, I used "FSInterrogate2std" to verify that the memory address is not changing. I was wondering if I'm using the wrong "OFFSET" function. But since everything else is working OK, I guessed not. I can't think of anything else I may be missing.

Do you have any ideas/comments/questions?

Thanks for your time,

Joe

[Pete Dowson]

I have an RP-48 with 8 buttons assigned via FSUIPC. One of them is not working.

...

FSUIPC ENTRIES

85=P175,0,Cx05003122,x80 ; COM1 XMIT |OFFSET BYTE SETBITS

86=P175,1,Cx05003122,x40 ; COM2 XMIT |OFFSET BYTE SETBITS <----- This is my problem button

...

Pushing Button#1 has no affect. When I push Button#0, LED#1 goes off and the LED#0 lights up. All other buttons and LEDs work fine.

You are only SETTING bits, not toggling them? how do you switch them off?

COM1 XMIT and COM2 XMIT are mutually exclusive. Try them yourself, using the mouse on the gauge! You need to turn COM1 off when turning COM2 on and vice versa (though by default the latter action occurs, as you see).

This is nothing to do with FSUIPC or the codes, simply the way FS works. Play with the actual gauge first so you understand. Until i know why you are only SETTING bits and not TOGGLING them I can't help further -- normally you'd toggle those two bits together.

Pete

[Skittles]

When I select the COM2 Transmit button on the aircraft panel within FS, LED#1 on the RP-48 lights up. (that's why I included the GFDisplay code). So I know I have the masking correct. Everything else relating to the GFDisplay.ini works fine.

I did use the mouse on the panel. It seems we just have different terminology.

When Com1 is selected, Com2 2 turns off automatically, and vise-versa. That's why I'm not toggling the bits. If it's not a FSUIPC problem, then thanks for your time.

Hope you had a good visit,

Joe

[Pete Dowson]

When Com1 is selected, Com2 2 turns off automatically, and vise-versa. That's why I'm not toggling the bits.

The problem arises because of the combination of commands needed. You can compare what happens with that FSUIPC offset and the Gauge by using the event logging in FSUIPC's logging options and checking the log.

I think it would work if you togglebits with parameter 0xC0. You only need one button teally, as you've found out!

I'm not really sure why you are going to all the trouble of using offsets and parameters for these functions in any case. Why not use the FS controls provided for the purpose? After all, all FSUIPC does is convert your bit changes into those controls, so it is actually less efficient using the offset for writing. You want to read it to set the indicators, of course. In case you can't find the relevant controls they are:

COM1_TRANSMIT_SELECT

COM2_TRANSMIT_SELECT

COM_RECEIVE_ALL_TOGGLE

NAV1_SOUND_TOGGLE

NAV2_SOUND_TOGGLE

DME_SOUND_TOGGLE

ADF_SOUND_TOGGLE

MARKER_SOUND_TOGGLE

If it's not a FSUIPC problem, then thanks for your time.

I'm not sure now -- enable event logging, and (on the Right hand side) monitor 3122 as type U8, check the 2normal log" option below, run your tests on those buttons, and show me the log. Remind me which version of FSUIPC it is too, please.

Pete

[Skittles]

I'm not really sure why you are going to all the trouble of using offsets and parameters for these functions in any case. Why not use the FS controls provided for the purpose?

Yeah, I found those after posting. I currently have them setup that way and it's working fine.

I'm running FSUIPC 3.9 26FEB09

Here's my log info:

********* FSUIPC, Version 3.90 by Pete Dowson *********
Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)
User Name="intentionally removed"
User Addr="intentionally removed"
FSUIPC Key is provided
WIDEFS not user registered, or expired
[Continuation log requested by user]
Module base=61000000
ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E
WeatherOptions(Orig)=4000B6AF[4000B6AF]
InitDelay: 0 seconds
WeatherReadInterval=4
LogOptions=00000001
   697937 System time = 14:22:01, FS2004 time = 14:16:55 (21:16Z)
   730750 Monitor IPC:3122 (U8) = 64
   735953 Monitor IPC:3122 (U8) = 128
   751640 Monitor IPC:3122 (U8) = 64
   759687 Monitor IPC:3122 (U8) = 128
   776390 Monitor IPC:3122 (U8) = 64

Here's the sequence of buttons I pressed

COM2 on the aircraft panel (AC) with the mouse

COM1 on the GoFlight RP-48 Panel (GF)

COM2 GF

COM2 AC

COM1 GF

COM2 GF

COM2 AC

COM1 AC

[Pete Dowson]

... it's working fine.

... Here's my log info:

What's the log for if it's working fine?

The log is no use to me in any case as you didn't enable the event logging as I asked. But don't bother if it is working fine.

Regards

Pete