Jump to content
The simFlight Network Forums

Axes and Potentiometer


JoeAir
 Share

Recommended Posts

Certainly something similar was already mentioned here in the forum- Is there a possibility that an axis can be assigned to a potentiometer in the cockpit? I've been trying to assign axes or buttons to the potentiometer for the cockpit lighting for a long time. I always use fsuipc for all controls and aircraft, of course profile-related. can you help ? Thanks, joeair

Link to comment
Share on other sites

52 minutes ago, JoeAir said:

Is there a possibility that an axis can be assigned to a potentiometer in the cockpit?

How are you connecting your potentiometer to the computer? If you wired it through something like a Leo Bodnar BU0836 card then connect that to the PC via USB, it will be seen as an axis by both Windows and FSUIPC, and you can assign it as you like.

I don't know about cockpit lighting though. I don't know of a simulated aircraft which has adjustable cockpit lighting, so perhaps you are talking about controlling real lighting in your built cockpit using some control in FSUIPC, but in that case I can't see where a potentiometer comes into it. You need a DtoA (digital to analogue) ciruit instead?

Perhaps you could explain in a little more detail exactly what it is you are trying to achieve?

Pete

 

 

 

Link to comment
Share on other sites

Thanks for answer, it's a lot easier. The 3 axes of the ch flightsim yoke are not used and I want to use them for the cockpit lighting. No self-made card. In the fsuipc log, I think I remember, that the variable lights_potentiometer_set appears when the poti is operated in the cockpit. I can say more precisely this evening if neede. There is apparently no direct axis assignment.  JoeAir

Cockpitlights.JPG

Link to comment
Share on other sites

41 minutes ago, JoeAir said:

I think I remember, that the variable lights_potentiometer_set appears when the poti is operated in the cockpit.

Ah, so it is a facility in a simulated aircraft, not in your own cockpit, and a simulated potentiometer not a real one you are connecting!  Which aircraft is that?

Isn't this "lights_potentiometer_set" control listed for assignment in the drop down for axes? All controls ending in "_set" should be. Otherwise I'll have to ask John to look.

Pete

 

Link to comment
Share on other sites

3 minutes ago, Pete Dowson said:

Isn't this "lights_potentiometer_set" control listed for assignment in the drop down for axes? All controls ending in "_set" should be. Otherwise I'll have to ask John to look.

The LIGHT_POTENTIOMETER_SET control/event are currently not flagged as axes controls. I can add/flag this as an axis control so that it is available in the axes assignments drop-down. Presumably this also applies to the LIGHT_POTENTIOMETER_*_SET (where * is 1,2,3..30), which I can also add.

I'll post a version for you to try with this added later today....

John

Link to comment
Share on other sites

1 hour ago, John Dowson said:

The LIGHT_POTENTIOMETER_SET control/event are currently not flagged as axes controls.

yes, thats it- it isn't listed as axis. When you can add it, would be big step for me and what i heard, for others too.

1 hour ago, John Dowson said:

LIGHT_POTENTIOMETER_*_SET

i have never seen it before in any cockpit. If you want, i will go through all planes if any uses those "n_set"

To answer Pete's question, it is the Mooney M20R from Carenado.

Thank you, JoeAir

Link to comment
Share on other sites

Hi, a tried it out, but it doesn't adjust the panel light.
What i did:

Pic 01- you see, in FSUIPC I set the ch yoke axis to normal axis
Pic 02- what the log shows when moving the ch yoke axis
Pic 03- what the log shows when turning the potentiometer in the cockpit

Added 22 minutes later:

is the same at Carenado and MS Planes.

Axis Light_01.JPG

Axis Light 02.JPG

Axis Light 03.JPG

Link to comment
Share on other sites

It is not possible to tell what is happening for screen shots. Please attach your FSUIPC7.log and FSUIPC7.init files. We ALWAYS need to see these to lookl at such issues, not screen shots - they nearly always turn out to be useless.

Link to comment
Share on other sites

You logs show the control is being sent with the correct axis parameter, although the axis isn't moving that much:

Quote

 1796704 FS Control Sent: Ctrl=67227, Param=-15083 LIGHT_POTENTIOMETER_SET
  1796719 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -15083 (0xffffc515) LIGHT_POTENTIOMETER_SET
  1797407 FS Control Sent: Ctrl=67227, Param=-14433 LIGHT_POTENTIOMETER_SET
  1797422 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -14433 (0xffffc79f) LIGHT_POTENTIOMETER_SET
  1797422 FS Control Sent: Ctrl=67227, Param=-14173 LIGHT_POTENTIOMETER_SET
  1797438 FS Control Sent: Ctrl=67227, Param=-13783 LIGHT_POTENTIOMETER_SET
  1797438 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -14173 (0xffffc8a3) LIGHT_POTENTIOMETER_SET
  1797438 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -13783 (0xffffca29) LIGHT_POTENTIOMETER_SET
  1797469 FS Control Sent: Ctrl=67227, Param=-13523 LIGHT_POTENTIOMETER_SET
  1797485 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -13523 (0xffffcb2d) LIGHT_POTENTIOMETER_SET
  1797485 FS Control Sent: Ctrl=67227, Param=-13003 LIGHT_POTENTIOMETER_SET
  1797500 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -13003 (0xffffcd35) LIGHT_POTENTIOMETER_SET
  1797516 FS Control Sent: Ctrl=67227, Param=-12743 LIGHT_POTENTIOMETER_SET
  1797532 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -12743 (0xffffce39) LIGHT_POTENTIOMETER_SET
  1797547 FS Control Sent: Ctrl=67227, Param=-12483 LIGHT_POTENTIOMETER_SET
  1797563 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -12483 (0xffffcf3d) LIGHT_POTENTIOMETER_SET
  1797563 FS Control Sent: Ctrl=67227, Param=-12223 LIGHT_POTENTIOMETER_SET
  1797579 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -12223 (0xffffd041) LIGHT_POTENTIOMETER_SET
  1797625 FS Control Sent: Ctrl=67227, Param=-11963 LIGHT_POTENTIOMETER_SET
  1797641 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -11963 (0xffffd145) LIGHT_POTENTIOMETER_SET
  1797922 FS Control Sent: Ctrl=67227, Param=-12223 LIGHT_POTENTIOMETER_SET
  1797938 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -12223 (0xffffd041) LIGHT_POTENTIOMETER_SET
  1798047 FS Control Sent: Ctrl=67227, Param=-12483 LIGHT_POTENTIOMETER_SET
  1798047 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -12483 (0xffffcf3d) LIGHT_POTENTIOMETER_SET
  1798672 FS Control Sent: Ctrl=67227, Param=-12223 LIGHT_POTENTIOMETER_SET
  1798688 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -12223 (0xffffd041) LIGHT_POTENTIOMETER_SET
  1798766 FS Control Sent: Ctrl=67227, Param=-11963 LIGHT_POTENTIOMETER_SET
  1798766 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -11963 (0xffffd145) LIGHT_POTENTIOMETER_SET
  1799250 FS Control Sent: Ctrl=67227, Param=-12223 LIGHT_POTENTIOMETER_SET
  1799266 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -12223 (0xffffd041) LIGHT_POTENTIOMETER_SET
  1799407 FS Control Sent: Ctrl=67227, Param=-12483 LIGHT_POTENTIOMETER_SET
  1799407 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -12483 (0xffffcf3d) LIGHT_POTENTIOMETER_SET
  1802344 FS Control Sent: Ctrl=67227, Param=-12743 LIGHT_POTENTIOMETER_SET
  1802360 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -12743 (0xffffce39) LIGHT_POTENTIOMETER_SET
  1818204 FS Control Sent: Ctrl=67227, Param=-13003 LIGHT_POTENTIOMETER_SET
  1818219 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= -13003 (0xffffcd35) LIGHT_POTENTIOMETER_SET
 

And you also have the same control set to a button with a fixed parameter of 5 for some reason:

Quote

  2178454 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= 3 (0x00000003) LIGHT_POTENTIOMETER_SET
  2181219 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= 3 (0x00000003) LIGHT_POTENTIOMETER_SET
  2181875 ***  AXIS: Cntrl= 67227 (0x0001069b), Param= 3 (0x00000003) LIGHT_POTENTIOMETER_SET

On fact, you have multiple assignments to LIGHT_POTENTIOMETER_SET in the profile you use for the Carenado Mooney:

Quote

35=RB,0,C67227,5     -{LIGHT_POTENTIOMETER_SET}-
36=RB,1,C66894,0     -{LIGHT_POTENTIOMETER_INC}-
37=UB,0,C0,0     -{Custom control: <0>}-
38=UB,1,C66894,0     -{LIGHT_POTENTIOMETER_INC}-
...
 

1=BX,256,F,67227,0,0,0    -{ TO SIM: LIGHT_POTENTIOMETER_SET }-
2=BY,256,F,65765,0,0,0    -{ TO SIM: AXIS_THROTTLE_SET }-
3=BZ,256,F,67227,0,0,0    -{ TO SIM: LIGHT_POTENTIOMETER_SET }-
4=GX,256,F,65763,0,0,0    -{ TO SIM: AXIS_AILERONS_SET }-
5=GZ,256
6=GZ,B,0,0,67227,5    -{ Entering=LIGHT_POTENTIOMETER_SET }-

Why assigned in so many places?

Anyway, can you generate one more log. This time, please don't start a new log file - its far easier for me if you give me one full log file, not continuation log files (I think I'm going to remove this facility). For this log, just load your aircraft, and move a single axis to, which you have assigned LIGHT_POTENTIOMETER_SET , through its full range forwards then backwards. We can then see the parameters being sent with that control when you operate it through its full range. 

Link to comment
Share on other sites

Thank you for patience,

Sorry, I had a mess with 8 log files. First I tried axes, then switches and others.
Today I deleted all logs and assigned only the ch yoke axis with a fresh ini and one log.
Once the poti in the cockpit had moved briefly, but only in one direction of rotation.
I notice that the type param = with the yoke axis is 5 digits, when I turn it in the cocpit it is 1 digit param = 5.

FSUIPC7.logFSUIPC7.ini

Link to comment
Share on other sites

2 minutes ago, JoeAir said:

Sorry, I had a mess with 8 log files. First I tried axes, then switches and others.
Today I deleted all logs and assigned only the ch yoke axis with a fresh ini and one log.
Once the poti in the cockpit had moved briefly, but only in one direction of rotation.

Ok. The log shows that the axis is assigned and sending the correct axis value.

3 minutes ago, JoeAir said:

I notice that the type param = with the yoke axis is 5 digits, when I turn it in the cocpit it is 1 digit param = 5.

If thats the case, then it doesn't look like this us a real axis control. What happens if you assign to a button with parameter 5 - does that work at all?

You could try to see if there are any available lvars that you could use - try listing them using the Add-ons->WASM->List Lvars menu entry, and see if any look applicable, Then change in the UI, and list again to see the new values. If you find something that looks like it controls the lighting. Then, you can test this by changing the value of the lvar using the WASM0>Set Lvar... menu option. if you find an lvar that works, I can then show you how to use this.

Otherwise, you may want to ask how this works and how to control on the Carenado forums. I dont have this add-on so its difficult to advise.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.