Denis Albisser
-
Posts
55 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Denis Albisser
-
-
Hi,
I am using MSFS (store version) and Asobo cessna 172 classic, FSUIPC 7.3.19.
My axes configurattion worked since years and I didn't change anything on my setup. Suddenly, I note a strange behaviour with my Cessna.
The brakes are not correctly managed : I can scan the left brake and right brake axis, they are detected and I can assign them to a direct calibration.
But in the calibration box, they appear "not assigned" and pressing "Set" has no effect, but the values change as always when i press the pedals. So, I cannot invert them and taxiing is a nightmare. This behaviour happens only for the brakes, the other axis react correctly when I press the "Set" button...
So, I cannot invert the axis and when i press the pedals, the brakes are off, but the sim detects the pedal positions, My CH products rudder is functional.
I have checked there is no control for the brakes in the MSFS config.
I have tried to edit the ini file, copy and past the brake lines from another aircraft but no effect.
Best regards
-
Hi,
I wanted to upgrade my P3d V4 and use FSUIPC with P3DV5.
But the only things i have are the docs. There is no dll or key file in the modules folders
When i try installing again, it says it is still there and wants to uninstall before, what i did. Now i could reinstall and get the same confirmation it worked.
So the former and long working installation in V4 is lost and the new wanted in V5 is not there.
What's wrong ?
-
-
Hi, Combo2009,
Could you please post these famous lua files ? (or a link...)
Best regards
-
Hi,
I have change my PC and now fly only with P3D.
So I've installed the last software. At nbegionning, it says that my old I/O module is not compatible :evil:. What can I do ?
But my biggest difficulty is that i use a generic single needle gauge as an Angle Of Attck gauge, like there is one on the lear 45 pannel : at minimum value, the needle is at 9' clock, at maximum at 12h00. So, the positions between 09 and 12h00 are not used. After a lot of trying, i've obtained a good result.
But now, no luck : I've set the different values and needle positions, created and affected a plate. When Simulator control is right, the needle goes to the 09h00 position as I want. But when P3D is running, aircraft on ground and no wind, the needle translates to 10h30, and voilà ! :oops:
So a little how/to with screens could help :mrgreen:
I attach a copy of my cfg (saved as txt, posting a cfg is not allowed)
Best regards
Denis
-
Hi,
I have regularly same problems when assigning any function to A GF button. Part or all GF modules are freezed, FPS can some time be affected. Restarting FSX cannot change the state of the modules, Windows restaring cannot. I hve to stop the computer AND disconnect the electric power.
So, I think this is USB power problem : there are too many modules on the same USB plug anywhere in the USB chain, OR an USB cabel is too long or has defect.
Best regards
Denis
-
Hi,
Is there a way that FI software can work with Prepar3D ? I've got a complex hardware with FI gauges, Goflight modules and Project Magenta software. I see FSUIPC, PM and Goflight are P3D frendly. The last condition for me to convert to P3D is FI compliant software.
Best regards
Denis
-
I use gyro compas, but cannot convert 0580in degrees.
I have a network, Master PC Vista64, FSX, GFDiplay FSUIPC 4.53 and Wideserver 7.53, firts slave Project Magenta PMRJ, second slave PM systems, PM CDU and PM MCP
[GF Connections]
GFDev=DLL found
GFLGT=1
GFRP48=1
GFT8=2
GF166=2
GF45=1
GFP8=1
[Conditions]
0=X500 U16 ;PM's MCP is active if this is non-zero
1=X4F0 U16 M8000 ; PMs speed is Mach
2=X7E4 U32 ; FSs speed is Mach -- see condition 46 too
3=X4F0 U16 M0002 ; PMs V/S mode
4=X3300 U16 M0100 ; FS LOC acquired
5=XC4E U16 ; CRS nonzero?
6=X4E2 U16 ; PM HDG nonzero?
7=X7CC U16 *360 /65536 ;FS's HDG nonzero?
8=X3300 U16 M0080 ; FS NAV CRS acquired
9=XBEC U16 =16383 ; Nose Gear Down
10=XBF0 U16 =16383 ; Right Gear Down
11=XBF4 U16 =16383 ; Left Gear Down
; offset 66C0 used as GF45/46 radio selector, 0-6 as follows:
12=X66c0 U8 =0 ;Radio selector 0=COM1
13=X66c0 U8 =1 ;Radio selector 1=COM2
14=X66c0 U8 =2 ;Radio selector 2=NAV1
15=X66c0 U8 =3 ;Radio selector 3=NAV2
16=X66c0 U8 =4 ;Radio selector 4=ADF1
17=X66c0 U8 =5 ;Radio selector 5=ADF2
18=X66c0 U8 =6 ;Radio selector 6=TPNR
; GF166 support includes both radios and an offset viewing debug mode
; Offset 66C4 has flag bits as follows
; bit 0 (1) = debug offset view if 0, debug type view if 1
; bit 1 (2) = debug decimal display if 0, hex display if 1
; bit 2 (4) = radio if 0, debug offset mode if 1
; bit 3 (8) = standby shown if 0, radial shown if 1
; bit 4 (16)= set by Centre button press, Cleared when released and if L or R pressed
; bit 5 (32)= set for MCP Mach display instead of IAS (FS MCP)
; Offset 66C1 used for debug mode offset type (0-12)
; Offset 66C5 used as radio selector, 0-5
; Offset 66C2 (2bytes) is offset in debug mode
19=X66C4 U8 M01 ; Offset (0) or Type (1) display mode
20=X66C4 U8 M02 ; Num value in dec (0) or hex (1)
21=X66C1 U8 =0 ; U16
22=X66C1 U8 =1 ; S8
23=X66C1 U8 =2 ; U8
24=X66C1 U8 =3 ; S16
25=X66C1 U8 =4 ; U16
26=X66C1 U8 =5 ; S32
27=X66C1 U8 =6 ; U32
28=X66C1 U8 =7 ; F32
29=X66C1 U8 =8 ; F64
30=X66C1 U8 =9 ; STR
31=X66C1 U8 =10 ; R0
32=X66C1 U8 =11 ; R1
33=X66C1 U8 =12 ; R2
34=X66C1 U8 <7 ;Fixed point
35=X66C1 U8 <9 ;Numeric
36=X66C4 U8 M04 ; Flag for Debug mode, else Radio
37=X66c5 U8 =0 ;GF166 radio selector 0=COM1
38=X66c5 U8 =1 ;GF166 radio selector 1=COM2
39=X66c5 U8 =2 ;GF166 radio selector 2=NAV1
40=X66c5 U8 =3 ;GF166 radio selector 3=NAV2
41=X66c5 U8 =4 ;GF166 radio selector 4=ADF1
42=X66c5 U8 =5 ;GF166 radio selector 5=ADF2
43=X66C4 U8 M08 ; Flag for radial display for NAV
44=X3300 U16 M0002 ;Active Nav1
45=X3300 U16 M0004 ;Active Nav2
46=!C1 !C2 X66C4 U8 M20 ;Mach not IAS
47=X051C U8 M01 ; PM blank VS
48=X051C U8 M02 ; PM blamk SPD
49=X7B91 U8 =1; Mode C
50=X7B91 U8 =0; Standby
51=X7B93 U8 =1; Ident Active
52=x3102 u8 =1
53=x2054 u8 =1 ;tank allp
54=x2054 u8 =2 ;tank left
55=x2054 u8 =6 ;tank center
56=x2054 u8 =3 ;tank right
57=x2054 u8 =13 ;crossfeed
58=x2054 u8 =14 ;crossfeed LtoR
59=x2054 u8 =15 ;crossfeed RtoL
60=x2054 u8 =14 ;crossfeed both
[GF45.0]
Needs=V16 B E A
B=4
;D0.1=!C51 C49 ="MD C"
;D0.2=!C51 C50 ="STBY"
;D0.3=C51 ="IDNT" Ff2on
;D0=X2B00 F64 D-30 ;Heading issu de Simconnect MARCHE !!!
;D0=X0580 u16 *360/(65536 *65536) f64 d-30 <<< Bad multiplier (*)
;D1=x02a0 u16 *360/(65536 *65536) <<< Bad multiplier (*)
;D1=X0580 u16 *360 d-30 f64
;D1=D-30 X2B00 F64 ;;;X08b8 u16 *140/16384 D21 ;FS's HDG as nnn ;Affiche le heading mais de manière erratique
;d0=d-30 x08f8 f64 *144 ne marche pas
;d0=x123e ;
d1=x126c ; fuel total marche !
d0.0= c53 ="ALL"
d0.1=c55 ="CNTR"
d0.2=c54 ="LAUX"
d0.3=c56 ="RAUX"
;d1=x2018
[GFP8.0]
Needs=V16 B E A
B=5
;L0=c0 X4F0 U16 M4000 ;VNAV
;L1=c0 X4F0 U16 M0040 ;LNAV
;L2=c0 X4F0 U16 M0100 ;FLCHG
L3=X281c =1 ; Battery Master
L4=X3101 U8; Alternator Master
;L5.0=Xb54 U16>10; <2000 Fslow
;L5.1=Xb54 U16>2000; <40000 Ffast
L5.0= X560E = 1
L5.1=!X560E = 1 <<< Bad literal value
;L5=xB54 u16 =44909 Ff10on; Xb54 APU on ne s'éteint pas mais s'allume size 4 32 bit float
;L6=xB54 U16 <2000
L7=c52 X2e80 ; Avionics Master
[GFT8.0]
Needs=V16 B E
B=2
L0=X337D U16 ;De-ICE STRUCT size 1 on=1 off=0
L1=X029C U16 ; pitot heat size 1 on=1 off=0
L2=X0D0C U16 M0020 ;panel lights size 2
L3=X0D0C U16 M0004 ;land l
L4=X0D0C U16 M0008 ;taxi lt
L5=X0D0C U16 M0001 ;nav lt
L6=X0D0C U16 M0002 ; beacon
L7=X0D0C U16 M0010 ; strobe
[GFT8.1]
Needs=V16 B E
B=8
;L6.0=XBAC =1 Ffast ;inner
;L6.1=XBAE =1 Ffast ;middle
;L6.2=XBB0 =1 Ffast ;outer
L7=X808 =1;yaw damper ffast size4
[GFRP48.0]
Needs=V16 B E
L0=X3590 U16 =1 ;fuelvalve eng1
L1=x3594 u16 =1 ;fuel valve eng2
;L1=X3104 =1 ;FUEL PUMP
L2.0=xAF8 =1 ;FUEL all
L2.1=xAF8 =2 Fslow;FUEL all
L3.0=xAF8 =1 ;FUEL all
L3.1=xAF8 =6 Ff5on;FUEL all
L4.0=xAF8 =1 ; fuel all
L4.1=xAF8 =3 Fslow;FUEL right
L5=X894 =1 Ff7on ;engine 1 running size2
L6=X092C U16=1 Ff7on ;engine 2 running
L7=C0 X4f0 U16 M0800 ;A/T
[GF166.0]
Needs=V16 B E A
B=5
[GF166.1]
Needs=V16 B E A
B=5
[GFLGT.0]
Needs=E B
B=5
L7=XBEC U16 =16383 ;Nose Gear Down
L6=!C9 XBEC U16 !=0 ;Nose Gear Moving
L5=XBF4 U16 =16383 ;Left Gear Down
L4=!C11 XBF4 U16 !=0 ;Left Gear Moving
L3=XBF0 U16 =16383 ;Right Gear Down
L2=!C10 XBF0 U16 !=0 ;Right Gear Moving
-
Thak you for your quick help, i'll try it soon.
But I have other difficulties :
I would diplay current plane magheading on a GF45 :
When I try this :
D0=X2B00 F64 D-30
The displayed value i correct at beginning, but when I change the heading, the display stops a few degrees before the good one, and so it stays false till the next turn when it refreshes the value and restops befor and of turning.
I have trie a few other variables who have same behaviour
What is the trick ?
Best regards
Denis
-
Hi,
I have programmed leds for my GF-T8 module so :
[GFT8.0]
Needs=V16 B E
B=2
L0=X337D =1 ;De-ICE STRUCT size 1 on=1 off=0
L1=X029C =1 ; pitot heat size 1 on=1 off=0
L2=XD0C U16=32 ;panel lights size 2
L3=XD0C U16=4 ;land l
L4=XD0C U16=8 ;taxi lt
L5=XD0C U16=1 ;nav lt
L6=XD0C U16=2 ; beacon
L7=XD0C U16=16 ; strobe
But, leds 0 and 1 are working a moment, than go off without any action.
I have a lot of ather situations like this ;
I've found how to attach a led or display to a variable, but the led or the display are erratic, chnaged without reason, or affected when another led form same module changes its state.
What do I wrong ?
Best regards
Denis
-
Hi Mark,
This works, I've changed the I/O card Id in that way.
But what can I do with my other probs ?
best Regards
Denis
for the changing of the ID, try to disconnect all other gauges and just connect the gauge you want to change the ID for.then search and change it in the configuration screen
let me know if that works
Mark
-
Hi Simbuf,
Thank you for your answer
Hi Denis,The idea of a second setup to change elementary Gauge properties will only work with equal Gauge properties. The basic configuration settings, like Gauge ID, millibar /InchHg are saved in the gauge itself. This is done for efficiency reasons and to reduce overhead in the control program. Within this limitation a dual configuration for Master/Slave will work.
In normal situations the Gauge is configured only once and the settings in the Gauge aren’t read-back from the gauge when re-opening the configuration window for that particular gauge. I agree that can lead to confusion, but that is the way it is currently programmed (for overhead reasons as mentioned before).
So is there a special way to turn the settings back to default ?
So, I advice to toggle the pressure mode and “air pressure effects...” settings , to make sure that the gauge is configured correctly. The latter setting should never be selected. This mode is for non-MS-FS applications.
To check the “Air pressure effects …” : Turning the pressure knob will change the altitude directly. Even when control program isn’t running.
To check the millibar / inHG: depress the air pressure knob for the default values ( 1013 or 29:92)
The test button on the configuration window should result in showing all digits 0-9 in a loop. This must be the case in all modes and if an error or misreading occurs there must be something wrong with the gauge or power.
I must say that since this test button exists, the digits are not functionning like I said in "slave mode". The test shows only "8888" and "10000" with all digits working, the steps of test don't display properly, only a portion of the digit is working. I see the same bug when I try to write to the gauge (read works fine)...
In a double altimeter config, each one should have its own gauge ID
There is no need to change com port number. This will have no effect on the problem.
i have an other difficulty that could have anything to do with my prob : there is no way to change the gauge ID. Each time I try it (and that is right for my 6 modules), the driver says the gauge is not connected.
In case this doesn’t work please send us both configuration files for analysis.
best regards
Denis
all the best
Simbuff (Mark)
-
Hi
I have serious difficulty to setup my digital altimeter. As it was running in slave mode for IVAO flights, it was fine working since a few weeks.
So i wanted to make a second setup to return in master mode when flying offline. And from now, it never works correct : In master mode, the gauge don't send any pressure value to FSX, but the needle and display are working, showing different values as FS. But modifying pressure in FS makes the gauge working, not the good values, but the hardware is functionnig correctly.
In slave mode, the display is bad : I have only the dot and a little part of the last altitude digit, with unstable brightness. (I always have this bug when I try to test display in the software, the only solution is to reset the card). So I don't understand what i'm doing wrong. I tested "slave", "master", "air pressure affects altitude", uninstalled and rescanned the gauge, nothing to do ; i've also tried to use another comport, but only the comport 3 is working.
What can I do ?
Best regards
Denis
-
Hi
So I wanted to save a setup for IVAO flights and one to fly offline (also, digital altimeter as slave for the first and as master for offline).
But , when switching from one to the other is bugging the digits !
I can only have them working trough reset of the card. And froml now, my altimeter is only working as slave. The setup file shows the right setup I want, but in slave mode, the altimeter is working as slaven and in master, turning pressure affects pressure display, but has no effect on altitude needle and display. What's wrong ?
Best regards
Denis
-
Hi Simbuff,
I see the new turn and bank coordinator gauge is comming. Nice !
What is actually the delay to have this gauge ?
Best regards
Denis
PS : and the GSA 13 Airspeed Indicator with barber pole ?
-
Hi Simbuff
Yes it works !!!
Thank you for your help !
Denis
-
Hi Simbuff,
I don't see such ticking option. I have only "Pressure effects altitude" and master/slave (5.3.1 soft) ??
Best regards
Denis
-
Hi all,
I cannot use my digital altimeter with IVAO. When I connect IVAO, after a few secinds, IVAO resets the meteo onditions, and i can see that my altitude changes on the FI digital altimeter. But from then, I cannot change the pressure, the perssure display is freezed.
Any Idea ?
(FSX SP2 DX10 Vista64)
Denis
-
Hi,
I have actually some FSX crashes (Vista64 says the display driver has failed).
In that cas, relounching FSX makes my comport problem.
When I restart the PC, everything is OK. i must say that when Vista has such failure, no 3D program can function, correctly, Vista has more and more display drives crashes and I must aniway restart the PC.
Denis
-
Hi everyone,
As I installed vista64 on my new PC for a few weeks, I had some problems to get Comport work, but I found free sftware who could bring everything OK. (I had to search on the net, because FI site has only the old software that didn't work on my PC.
Since i installed Vista SP1 yesterday, I have the comport error.
Has anybody a solution ?
Denis
-
Hi Manny
Thanks for advice ! I didn't see that there is a new FSUIPC and will try it later. My gauge problem seems solved, I simply have uninstalled the gauge and reinstalled... and it works so fine as ever !!!
But I have FS X crashes. I've tried if it goes better without the FI software, and the crashes continue. So, I hope the new FSUIPC is the answer.
Best regards
Denis
-
Hi
Since I've installed SP1, My altimeter presure button don't have any effect on altitude. The rest of the gauges works fine
Any idea ?
Denis
-
Hello
Seems that the 4-4-5 driver archive is wrong : Only 214 octets
-
Hello Simbuff,
Glad to see some answer
Yes, the gauges work very very fine. I foud the solution : I had not assigned any option for my connected I/O card. Could this card send offsets to FSUIPC ?
Best regards
Denis
Axes does not set
in FSUIPC7 MSFS
Posted
Hi,
THANK YOU !!!
Yes, this behaviour was common for all aircrafts from the DR400 profile
Your ini file has corrected everything and allowed me to set the brake axis like a charm.
I really don't know why this happened, i didn't change the axis since a while.
The only new thing in my setup was that it happened immediatly after pop out manager installation.
Best regards