Using Phigdets directly with pmSystems

[ekezz]

Hi,
In a great overview by Gert van der Winden I see that you need FS2PhUIPC.ini
I think this was made in march 2005.

Since (july?) pmSystems has direct control over phidgets via phidgets.txt
So it was easy to get the parkingbrake light assigned to a LED64 and it works as it should.
Now I want to make the autobrake switch to work on a 0/16/16 Phidgets board.
Can I make this work directly in phidgets.txt (pmSystems file) or do I still also need to make the modifications to the FS2PhUIPC.ini as Gert described.

Kester

[ekezz]

A collegue builder John Ebbers from Nijmegen, The Netherlands posted the same kind of question to the Project Magenta forum and Enrico gave a clear answer I would like to share here.

Another tip from John is to go to the menu of pmSystems and check the following boxes:
- Development Mode
- Show Variable Name
When you move your mouse over the screen it will show the variable name, offset and present value.
When you change the switch setting the value will also change.

Copy and assign these names, offsets and values to the switch in the file phidgets.txt in the pmSystems folder
Kester



Hello,

> the 3 position switch for GEN1 switch we cannot configure
> correctly
> This is the line:
> 4590 DI00 gen1 (this is when switch to above, so off)
> 4590 DI01 gen1 (this is when switch to below, so on)
>
> what do we have to add after gen1... how does the offset
> works.
> We using the latest PMS 76.


// [DeviceSerial] DIXX [VariableName]
// [DeviceSerial] DIXX [VariableName] INV // Inverts 1 =
off, 0 = on
// [DeviceSerial] DIXX [VariableName] MOM // Momentary
Switches
// [DeviceSerial] DIXX [VariableName] 5 // sets value 5 when
on, 0 when off
// [DeviceSerial] DIXX [VariableName] 1 2 // sets value 1
when on, to 2 when off
// [DeviceSerial] DIXX [VariableName] 1 - // sets value 1
when on, does nothing when off

You would need to use, as described, the values 0, 1, 2 as
necessary.

> 4590 DI00 gen1 (this is when switch to above, so off)
> 4590 DI01 gen1 (this is when switch to below, so on)

Thus if you have three inputs for the positions...

4590 DI00 gen1 0
4590 DI01 gen1 1
4590 DI01 gen1 2

If you have two inputs (both off, one on, then the other one
on...

4590 DI00 gen1 1 0
4590 DI01 gen1 2 -

DI02 would do nothing in the off position

"John Ebbers" wrote in message
news:372847.74690@wb.onvix.com...
> hi there,
>
> Something new here in our cockpit.
>
> Now we placed the Phidget board on the same pc as
> PMSystems is running, so no
> need to install the Phidget software anymore.
>
> Assigned that Phidget is connected in the PMSystems menu.
> PMSystems detects the cards perfectly and created the new
> option in the
> menu.
>
> Now we assigned some overhead switches by filling in the
> PMSystem names,exp.
> landinglightR, seatbelts etc etc works perfect.
> But now the hard one..... :-)
> the 3 position switch for GEN1 switch we cannot configure
> correctly
> This is the line:
> 4590 DI00 gen1 (this is when switch to above, so off)
> 4590 DI01 gen1 (this is when switch to below, so on)
>
> what do we have to add after gen1... how does the offset
> works.
> We using the latest PMS 76.
>
> thanks, regards
> John & Bart
>

[Bob Reed]

Hi Guys! Well the answer is that PMSystems does not have to be used as it comes "out of the box"! One of the things is, it is totaly programable! In other words if you don't like the 737 logic in it.. Re do it, want to use PMSystems with another type aircraft? Program the logic for it. So adding what is not in FS is exactly what PMsystems was written for. Hope this helps.

[ekezz]

Thanks Bob, good addition.
My posting was meant as a partial How to.
Kester