Jump to content
The simFlight Network Forums

set value codes


bob barrell

Recommended Posts

i have 3 rotary encoders for speed,, heading and altitude (fsuipc codes 0x07E2 for speed  0x07cc for heading  0x0704 for altitude) the problem i have is the set values the speed only goes from 990 to 10 the heading goes through 360 degrees and stops at 178 and the heading starts at 99900 feet, i have watched a youtube video for heading and it says on left -182 left fast -1820 on the right +182 and fast right +1820 

they are working but not right 

thanks bob

its the flybywire a320

Link to comment
Share on other sites

11 hours ago, bob barrell said:

i have 3 rotary encoders for speed,, heading and altitude (fsuipc codes 0x07E2 for speed  0x07cc for heading  0x0704 for altitude) the problem i have is the set values the speed only goes from 990 to 10 the heading goes through 360 degrees and stops at 178 and the heading starts at 99900 feet, i have watched a youtube video for heading and it says on left -182 left fast -1820 on the right +182 and fast right +1820 

Please show me your FSUIPC7.ini file. Also, please activate logging for Buttons & Keys as well as Events and generate a short log file showing your issue, i.e. turn each of your encoders to show your issue, and attach the FSUIPC7.log file generated.

Link to comment
Share on other sites

apart from the heading which would stop at -180 +180 all others were ok i am not to sure how to adjust set value at the moment its at $-180 and $+180

 

5/05/2021 23:55:10(673): Executing OnRight: SPEED 1@SN-9fb-e62
25/05/2021 23:55:10(555): Config found for Encoder: SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:55:10(144): Executing OnLeft: SPEED 1@SN-9fb-e62
25/05/2021 23:55:10(42): Config found for Encoder: SPEED 1 (LEFT)@SN-9fb-e62
25/05/2021 23:55:09(946): Executing OnLeft: SPEED 1@SN-9fb-e62
25/05/2021 23:55:09(841): Config found for Encoder: SPEED 1 (LEFT)@SN-9fb-e62
25/05/2021 23:55:09(738): Executing OnLeft: SPEED 1@SN-9fb-e62
25/05/2021 23:55:09(636): Config found for Encoder: SPEED 1 (LEFT)@SN-9fb-e62
25/05/2021 23:55:07(879): Executing OnRight: HEADING1@SN-9fb-e62
25/05/2021 23:55:07(789): Config found for Encoder: HEADING1 (RIGHT)@SN-9fb-e62
25/05/2021 23:55:07(674): Executing OnRight: HEADING1@SN-9fb-e62
25/05/2021 23:55:07(566): Config found for Encoder: HEADING1 (RIGHT)@SN-9fb-e62
25/05/2021 23:55:07(461): Executing OnRight: HEADING1@SN-9fb-e62
25/05/2021 23:55:07(368): Config found for Encoder: HEADING1 (RIGHT)@SN-9fb-e62
25/05/2021 23:55:07(271): Executing OnRight: HEADING1@SN-9fb-e62
25/05/2021 23:55:07(176): Config found for Encoder: HEADING1 (RIGHT)@SN-9fb-e62
25/05/2021 23:55:06(87): Executing OnRight: ALTITUDE1@SN-9fb-e62
25/05/2021 23:55:05(999): Config found for Encoder: ALTITUDE1 (RIGHT)@SN-9fb-e62
25/05/2021 23:55:05(894): Executing OnLeft: ALTITUDE1@SN-9fb-e62
25/05/2021 23:55:05(811): Config found for Encoder: ALTITUDE1 (LEFT)@SN-9fb-e62
25/05/2021 23:55:05(718): Executing OnLeft: ALTITUDE1@SN-9fb-e62
25/05/2021 23:55:05(623): Config found for Encoder: ALTITUDE1 (LEFT)@SN-9fb-e62
25/05/2021 23:55:05(527): Executing OnLeft: ALTITUDE1@SN-9fb-e62
25/05/2021 23:55:05(442): Config found for Encoder: ALTITUDE1 (LEFT)@SN-9fb-e62
25/05/2021 23:55:05(335): Executing OnLeft: ALTITUDE1@SN-9fb-e62
25/05/2021 23:55:05(234): Config found for Encoder: ALTITUDE1 (LEFT)@SN-9fb-e62
25/05/2021 23:55:05(131): Executing OnLeft: ALTITUDE1@SN-9fb-e62
25/05/2021 23:55:05(40): Config found for Encoder: ALTITUDE1 (LEFT)@SN-9fb-e62
25/05/2021 23:55:04(946): Executing OnLeft: ALTITUDE1@SN-9fb-e62
25/05/2021 23:55:04(859): Config found for Encoder: ALTITUDE1 (LEFT)@SN-9fb-e62
25/05/2021 23:55:04(763): Executing OnLeft: ALTITUDE1@SN-9fb-e62
25/05/2021 23:55:04(683): Config found for Encoder: ALTITUDE1 (LEFT)@SN-9fb-e62
25/05/2021 23:50:38(6): Command: SetPin <2,48,255;>
25/05/2021 23:50:37(904): Preventing entering EnergySaving Mode: KeepAlive!
25/05/2021 23:48:51(520): Executing OnLeft: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:51(427): Config found for Encoder: VIRTICAL SPEED 1 (LEFT)@SN-9fb-e62
25/05/2021 23:48:50(535): Executing OnLeft: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:50(444): Config found for Encoder: VIRTICAL SPEED 1 (LEFT)@SN-9fb-e62
25/05/2021 23:48:49(255): Executing OnLeft: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:49(162): Config found for Encoder: VIRTICAL SPEED 1 (LEFT)@SN-9fb-e62
25/05/2021 23:48:48(327): Executing OnLeft: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:48(244): Config found for Encoder: VIRTICAL SPEED 1 (LEFT)@SN-9fb-e62
25/05/2021 23:48:47(319): Executing OnLeft: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:47(223): Config found for Encoder: VIRTICAL SPEED 1 (LEFT)@SN-9fb-e62
25/05/2021 23:48:44(703): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:44(601): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:44(496): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:44(414): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:44(305): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:44(209): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:44(103): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:44(5): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:43(896): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:43(818): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:43(714): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:43(611): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:43(491): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:43(375): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:43(274): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:43(170): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:43(51): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:42(963): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:42(851): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:42(760): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:42(638): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:42(533): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:42(442): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:42(343): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:42(248): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:42(137): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:42(35): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62
25/05/2021 23:48:41(940): Config found for Encoder: VIRTICAL SPEED 1 (RIGHT)@SN-9fb-e62
25/05/2021 23:48:41(838): Executing OnRight: VIRTICAL SPEED 1@SN-9fb-e62

Link to comment
Share on other sites

9 hours ago, bob barrell said:

apart from the heading which would stop at -180 +180 all others were ok

You are reading an UNSIGNED value as SIGNED! Just read as unsigned and you'll get 0-359.

I don't know what the rest of your posting is supposed to show. It isn't a log I recognise, and makes no sense anyway. Why did you post it? You need to show us the FSUIPC INI file and the LOG as John requested.

Pete

 

Link to comment
Share on other sites

8 minutes ago, bob barrell said:

could you explain what you mean by unsigned

A number stored in computer memory is represented by a number of bits ("binary digits") which are either 0 or 1.  A byte is a collection of 8 bits and can store a numeric value from 0 to 255. In order to represent negative numbers one of those 8 bits is used as an indicator as to whether the number is above zero (positive) or below zero. This reduces the range to -128 to +127. But the bits look the same either way -- it is how you interpret the bits.  Hence signed or unsigned.

So something representing an angle like heading be seen as -180 to +179 or 0 to 359.

13 minutes ago, bob barrell said:

and how i change it

I don't know what you've done to get your numbers, so I cannot help. I'd need you to show me, as I said.

What produced that weird log you showed before?

14 minutes ago, bob barrell said:

i change it also ALT/F dosnt bring fsuipc control panel also there is no icon in the icon box i assume the ini file is in there

If FSUIPC is running, then there's something wrong then. John will need to help you there. 

The INI file is next to FSUIPC7.EXE itself, in the folder you told the installer to install it into. If you don't remember where you put it and FSUIPC7 won't run then either do a search with Windows Explorer, or install it again and this time choose a folder you can remember. I create a folder called "FSUIPC7" to put it in.

Pete

 

Link to comment
Share on other sites

13 minutes ago, bob barrell said:

could you explain what you mean by unsigned and signed

Integers are either signed or unsigned.  How are you reading and setting this value? You need to show us your FSUIPC ini and log files... As Pete says, we don't know where that log you posted came from or why you posted it - it is NOT from FSUIPC.

16 minutes ago, bob barrell said:

also ALT/F dosnt bring fsuipc control panel also there is no icon in the icon box

Are you sure FSUIPC is running? If there is no FSUIPC icon in your system tray then it is not running.

18 minutes ago, bob barrell said:

i assume the ini file is in there

Why do you assume - why not just look for it and show it to us. If you don't know where this is, you can use the File -> Open Installation Folder... menu entry.  Of course, FSUIPC needs to be running to do this....

Link to comment
Share on other sites

fsuipc is running and connected and running sorry to be a pain but i am not a computer illiterate so everything has to be explain at basic level

i got the codes etc from you tube

heading  offset  0x07cc   bytes 2

set value  $-182 left  $+182 right  

altitude   offset  0x07D4   bytes 4
set value    if($>0,$-1997537,0if($>0,$-1997537,0  left  if($>0,$+1997537,0

V/S      offset 0x07F2   bytes 2
set value $-100 right  and $+100 left

i am using the fsuipc7 AP altitude value etc

 

FSUIPC7.11.log

Link to comment
Share on other sites

Just now, bob barrell said:

set value  $-182 left  $+182 right  

altitude   offset  0x07D4   bytes 4
set value    if($>0,$-1997537,0if($>0,$-1997537,0  left  if($>0,$+1997537,0

V/S      offset 0x07F2   bytes 2
set value $-100 right  and $+100 left

What is this? ....ok, you are using MobiFlight to access the offsets? Then you need to probably need MobiFlight support.
If you are assigning in FSUIPC, we need to see your FSUIPC7.ini.

The log you posted is also useless as it is a continuation log. Pease supply the full log file, and do not start a new/continuation log file.

5 minutes ago, bob barrell said:

i got the codes etc from you tube

Then maybe you should ask the person who posted that video. I have no idea what 'codes' you are talking about, sorry.

 

Link to comment
Share on other sites

3 minutes ago, bob barrell said:

sorry but where is the log file you want and i will send it i thought what i sent was a log file

You posted your log file, but it was a continuation log file, i.e. you started a new log. I need to see the full log file, not a continuation log file.
But, if you are assigning using MobiFlight, not FSUIPC, then you need MobiFlight support. If you are assigning in FSUIPC, I need also to see your FSUIPC7.ini file.

Link to comment
Share on other sites

3 minutes ago, bob barrell said:

there is another file which is to big to sent 4.8megs

You can zip it. That log file you posted doesn't contain anything useful.

But, as I said, if assigning in MobiFlight, you need MobiFlight support, not FSUIPC support. And if assigning in FSUIPC, I need to see your FSUIPC7.ini file as well as the log.
So no point in posting the log file really at the moment.

As Pete has said, it just looks like you are using the heading as a signed value when it should be unsigned. That shouldn't be too difficult to trace....

And I still don't know why you said Alt+F isn't working, and there is no FSUIPC icon in your system tray.... that log file you did post shows the Alt+F hot key is registered:

Quote

 

      265 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)

 

 

Link to comment
Share on other sites

Why do you keep sending me useless logs?

NEVER post me a continuation log. They are useless to me when investigating issues. I ALWAYS need to see a full log. And always with you latest FSUIPC7.ini file, as I have told you many times now.

Also, when generating log files to investigate an issue, it is a good idea to try and remove all events that are continuously being logged (i.e. noise). To do this, use the DontLogThese ini parameter, in either your [General] or [Profile.<name>] sections. i.e. add this:
    DontLogThese=66065,67042

Link to comment
Share on other sites

Sorry I hanvt a clue what you are saying you need to understand we are not all of your computer level and I am paying for the privilege for it not once have you said exactly where this file is I have sent what says fsuipc ini file 

Link to comment
Share on other sites

8 minutes ago, bob barrell said:

Sorry I hanvt a clue what you are saying you need to understand we are not all of your computer level and I am paying for the privilege for it not once have you said exactly where this file is I have sent what says fsuipc ini file 

ALL files that  I request will be in your FSUIPC installation folder, unless I say otherwise. I have asked for this file many times. Have you actually read the User Guide? If not, please do so.

I am not expecting you to be as knowledgeable as me in these matters, but I expect you to read my comments, and if you don't understand them ask for clarification (ie. "Sorry, I don't know what or where my FSUIPC7.ini file is - can you please explain?").

We can only progress with your issues if you read my comments and follow my advice. Please do that if you require further assistance.

Lets go back to mt very first comment on your issue:

On 5/25/2021 at 12:18 PM, John Dowson said:

Please show me your FSUIPC7.ini file. Also, please activate logging for Buttons & Keys as well as Events and generate a short log file showing your issue, i.e. turn each of your encoders to show your issue, and attach the FSUIPC7.log file generated.

Can you do that? If not, explain why and I can clarify.

NB. If you cannot see the extensions of the files in your installation folder, you have windows explorer configured to "hide known file types". If this is the case, please see the Addendum in the Installation and Registration guide.

Edited by John Dowson
Further info added
Link to comment
Share on other sites

i think i am gradully understanding this now

the speed which is working is  2476594 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 301 (0x0000012d) AP_SPD_VAR_SET

the alt dosnt work   2476594 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 301 (0x0000012d) AP_SPD_VAR_SET

heading dosnt work     894532 13728 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 178 (0x000000b2) HEADING_BUG_SET

vs dosnt work    2009672 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2000 (0x000007d0) AP_VS_VAR_SET_ENGLISH

 

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • 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.