-
MasterCautionSystem_FO Gauge is inactive
I am trying to add a new view with FO's MasterCaution These are the lines in my panel.cfg: [Window37] Background_color=0,0,0 size_mm=47,23 window_size_ratio=1.000 position=0 visible=0 ident=10037 window_size= 0.100, 0.100 window_pos= 0.000, 0.000 gauge00=PMDG_737NGX!MasterCautionSystem_FO, -51,-5,100,42 The gauge appears as expected BUT is inoperative! Not clickable and not lighting When I try with PMDG_737NGX!MasterCautionSystem_Captain all is OK Any ideas?
- O/C mastercard - Leds are always ON
-
O/C mastercard - Leds are always ON
When I connect a LED on any J2 pin ( 11-48 ) of my MasterCard (just bought), it is permanently ON! With SIOC monitor (last version) I turn the outputs status ON / OFF but the led never turns OFF. Is this normal? This is my first attempt with SIOC and OpenCockpits cards and for now I am testing and learning.. It looks like my master card does not open/closes the positives I've tested all pins and here are the results: [+5V],11,12,13,14,15,16,18,20,21 (dim) 17,19,30,31 (off) 22,23,24,25,26,27,28,29 (bright) 32,33,34,35,36,37,38,39,40 (very dim) 41,42,43,44,45,46,47,48 (dim) Nothing changes using "ALL ON" and "ALL OFF" EXCEPT PIN18! when I press "ALL ON" turns OFF! and when I press "ALL OFF" turns ON! Pressing just its square [18] there is no change Same results as I've described when I use a 4,9V supply and when I use just the USB connection (without ext. power) The only difference is that with power supply leds are brighter. All 71 digital inputs work normally So, all positives are always ON! (except 17,19,30,31 that are always OFF!) (PIN18: Connecting is ON but when I press "ALL ON" turns OFF! and when I press "ALL OFF" turns ON!) Normally connecting a LED must be OFF until card sends a signal to its positive to turn ON (am I wrong?) Do I have to run a specific SIOC script to do a reliable test? (I use SIOC Monitor ver 2.0) But connecting a LED is immediate ON and this is no good? Manolis
-
No wait to connect
SOLVED....strange but the problem was ESET firewall
-
No wait to connect
No, Tileproxy uses only one place (within the fsx folder) and you change proxyuser.ini manually. I forgot to notice that I use Tileproxy for months with no problems.This problem started with no particular reason. I didn't change anything.Perhaps I have to uninstall and install TILEPROXY again, but I'd prefer not to.PROXYUSER.BAT has 2 lines:proxyuser.exepausePAUSE command means wait FS to start???For some reason assumes that FSX has started and goes on??
-
No wait to connect
I've installed TileProxy for both FSX/FS9.When I start it boots up normally, shows the message "TileProxy is ready for takeoff" BUT WONT PAUSE to let me start FS9.Instead goes on.....proxyUser: Connected to Flight Simulator X!proxyUser: FSX process name assumed \Device\HarddiskVolume6\Program Files\Microsoft Games\Microsoft Flight Simulator X\fsx.exe......and then starts loading tiles...In FS9 around the plane every tile is blackAny advice please!
tzagman
Members
-
Joined
-
Last visited