Page 1 of 2 12 LastLast
Results 1 to 10 of 13
  1. #1
    New Member
    Join Date
    Apr 2013
    Location
    Brussels
    Posts
    4
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    SIOC and 737PMDG - programing switches

    Hi guys!

    I'm building my small ovh panel and have some problem with programing switches. It seems all right at the begining but the problem occurs when I use two different switches. Then it takes one change without action to let it back to work. Here is the code. It programes two light switches (logo and wing light)

    Code:
     Var 1 name FS_CONTROL1 Link FSUIPC_OUT Offset $3110 Length 4
     Var 2 name FS_PAR1 Link FSUIPC_OUT Offset $3114 Length 4
     
     Var 3 Link IOCARD_SW Input 0 Type I
     {
      &FS_PAR1 = v003
      &FS_CONTROL1 = 69757
      &FS_CONTROL1 = DELAY 0 10
     }
    
     Var 4 name FS_CONTROL2 Link FSUIPC_OUT Offset $3110 Length 4
     Var 5 name FS_PAR2 Link FSUIPC_OUT Offset $3114 Length 4
     
     Var 6 Link IOCARD_SW Input 1 Type I
     {
      &FS_PAR2 = v006
      &FS_CONTROL2 = 69754
      &FS_CONTROL2 = DELAY 0 10
     }
    When I look at OIMonitor it seems that FS_PARS change their value (0,1) everytime. But PMDG is not responding at the first time... Only after two moves. Did I forget about something?

    Thank you in advance
    best regards,
    Leszek

  2. #2
    75+ Posting Member
    Join Date
    Oct 2012
    Location
    London ON, CA
    Posts
    106
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: SIOC and 737PMDG - programing switches

    Is it PMDG for FSX the 737NGX...?

    If so i strongly recommend using OCP4NXG software by Roar Kristensen this is all the code you need to write example below and this is 5 switches.. some are more complicated then others.. but still a lot less code to write and it works like magic. you would need to change device # and Input if you wanted to use it...

    example for simple on/off switches
    Code:
    Var 2678 Static, name LIGHT_LOGO Link IOCARD_SW device 4 Input 87 Type I
    Var 2670 Static, name ANTI_COL Link IOCARD_SW device 4 Input 95 Type I
    Var 2685 Static, name LIGHT_WHEEL Link IOCARD_SW device 4 Input 93 Type I
    Var 2686 Static, name LIGHT_WING Link IOCARD_SW device 4 Input 92 Type I
    Var 2603 Static, name HORN_CUTOUT Link IOCARD_SW device 4 Input 105 Type I

    as you can see i got 5 working switches with 5 lines of code you got 2 not working with 16 lines of code...

    I am now in a process of wiring my OVH got 36 switches wired and working ... then another 100+ to go... then some annunciators like another 100+ .. what did i get myself into...
    anyways i be happy to post my entire code for OVH if you interested some switches like landing retractable lights are a bit more complicated cuz they have 3 positions i only use 2 though OFF and retractedON
    Andy

  3. #3
    New Member
    Join Date
    Apr 2013
    Location
    Brussels
    Posts
    4
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: SIOC and 737PMDG - programing switches

    Andy!

    Thank you very very much! I've downloaded OC4NGX and it works!!! So now I have to code all switches and leds... lots of work. Can you post your code for 3 pos switches and rotary switches like ign switch? That would save me some work
    I was hoping to finish my OVH in 2 months. It seems it will take 2 years

    best,
    Leszek

  4. #4
    75+ Posting Member
    Join Date
    Oct 2012
    Location
    London ON, CA
    Posts
    106
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: SIOC and 737PMDG - programing switches

    here is my ovh so far i got connected 38 switches so i code them as i go...
    as you already know remember to change device# and input#

    it should help you for the most part at least as temple one thing i wanted to mention is my 4 landing lights switches i use simple on/off switch that they have only two connectors meaning the way they mount in my panel the switch is OFF, but physical position represents what you would see if the switch is ON so my code says .. IF SWITCH IS OFF THEN LANDING LIGHTS ARE ON

    OTHER switches match regular thinking switch ON (signal ON) means variable is ON state

    use Roar's event_list_for_info.txt that came with the program to help you code more switches and also FSUIPC offsets document for PMDG where it says value for a variable (do not use FSUIPC offsets just value) for example.... most if not all rotary switches will have 3 or more values they might be 0,1,2,3,4..so on. ... as you start reverse engineering my code you will get a hang of... also you welcome to visit my blog i posted there some other sioc scripts again great to use as a temple... link at the bottom...

    here is the code:

    Code:
    Var 2676 Static, name LND_RT_L
    Var 5000 name LND_RT_LSW Link IOCARD_SW device 4 Input 77 Type I
    {
    IF &LND_RT_LSW = 0
    {
    V2676 = 2
    }
    ELSE
    {
    V2676 = 0
    }
    }
    
    Var 2682 Static, name LND_RT_R
    Var 5001 name LND_RT_RSW Link IOCARD_SW device 4 Input 72 Type I
    {
    IF &LND_RT_RSW = 0
    {
    V2682 = 2
    }
    ELSE
    {
    V2682 = 0
    }
    }
    
    Var 2674 Static, name LND_L
    Var 5002 name LND_LSW Link IOCARD_SW device 4 Input 80 Type I
    {
    IF &LND_LSW = 0
    {
    V2674 = 1
    }
    ELSE
    {
    V2674 = 0
    }
    }
    
    Var 2680 Static, name LND_R
    Var 5003 name LND_RSW Link IOCARD_SW device 4 Input 76 Type I
    {
    IF &LND_RSW = 0
    {
    V2680 = 1
    }
    ELSE
    {
    V2680 = 0
    }
    }
    
    Var 2677 Static, name LND_L_TOFF Link IOCARD_SW device 4 Input 73 Type I
    Var 2683 Static, name LND_R_TOFF Link IOCARD_SW device 4 Input 74 Type I
    Var 2684 Static, name LND_TAXI Link IOCARD_SW device 4 Input 75 Type I
    
    //Var 2684 Static, name APU_OFF Link IOCARD_SW device 4 Input 79 Type I
    //Var 2671 Static, name APU_START Link IOCARD_SW device 4 Input 78 Type I
    
    
    //---------------APU SELECTOR-------------
    Var 2671 Static, NAME APU_SEL
    Var 5004 name APU_OFF Link IOCARD_SW device 4 Input 79 Type I
    {
    IF &APU_OFF = 1
    {
    V2671 = 0
    }
    ELSE
    {
    V2671 = 1
    }
    }
    
    Var 5005 name APU_START Link IOCARD_SW device 4 Input 78 Type I
    {
    IF &APU_START = 1
    {
    V2671 = 2
    }
    ELSE
    {
    V2671 = 1
    }
    }
    
    //---------------IGNITION SELECTOR-------------
    Var 2673 Static, NAME IGN_SEL
    Var 5006 name IGN_L Link IOCARD_SW device 4 Input 94 Type I
    {
    IF &IGN_L = 1
    {
    V2673 = 0
    }
    ELSE
    {
    V2673 = 1
    }
    }
    
    Var 5007 name IGN_R Link IOCARD_SW device 4 Input 91 Type I
    {
    IF &IGN_R = 1
    {
    V2673 = 2
    }
    ELSE
    {
    V2673 = 1
    }
    }
    
    
    //---------------ENGINE START-------------
    Var 2675 Static, NAME ENG_L_START
    Var 5008 name GRD_L Link IOCARD_SW device 4 Input 81 Type I
    {
    IF &GRD_L = 1
    {
    V2675 = 0
    }
    }
    Var 5009 name OFF_L Link IOCARD_SW device 4 Input 89 Type I
    {
    IF &OFF_L = 1
    {
    V2675 = 1
    }
    }
    
    Var 5010 name CONT_L Link IOCARD_SW device 4 Input 85 Type I
    {
    IF &CONT_L = 1
    {
    V2675 = 2
    }
    }
    
    Var 5011 name FLT_L Link IOCARD_SW device 4 Input 82 Type I
    {
    IF &FLT_L = 1
    {
    V2675 = 3
    }
    }
    
    //---------------ENGINE START-------------
    Var 2681 Static, NAME ENG_R_START
    Var 5012 name GRD_R Link IOCARD_SW device 4 Input 88 Type I
    {
    IF &GRD_R = 1
    {
    V2681 = 0
    }
    }
    
    Var 5013 name OFF_R Link IOCARD_SW device 4 Input 84 Type I
    {
    IF &OFF_R = 1
    {
    V2681 = 1
    }
    }
    
    Var 5014 name CONT_R Link IOCARD_SW device 4 Input 83 Type I
    {
    IF &CONT_R = 1
    {
    V2681 = 2
    }
    }
    
    Var 5015 name FLT_R Link IOCARD_SW device 4 Input 86 Type I
    {
    IF &FLT_R = 1
    {
    V2681 = 3
    }
    }
    
    Var 2678 Static, name LIGHT_LOGO Link IOCARD_SW device 4 Input 87 Type I
    Var 2670 Static, name ANTI_COL Link IOCARD_SW device 4 Input 95 Type I
    Var 2685 Static, name LIGHT_WHEEL Link IOCARD_SW device 4 Input 93 Type I
    Var 2686 Static, name LIGHT_WING Link IOCARD_SW device 4 Input 92 Type I
    Var 2603 Static, name HORN_CUTOUT Link IOCARD_SW device 4 Input 105 Type I
    
    //---------------POSITION STOBE-------------
    Var 2679 Static, NAME POS_STROBE
    Var 5016 name STROBE1 Link IOCARD_SW device 4 Input 90 Type I
    {
    IF &STROBE1 = 1
    {
    V2679 = 2
    }
    ELSE
    {
    V2679 = 1
    }
    }
    
    
    
    Var 5017 name STROBE3 Link IOCARD_SW device 4 Input 98 Type I
    {
    IF &STROBE3 = 1
    {
    V2679 = 0
    }
    ELSE
    {
    V2679 = 1
    }
    }
    
    //------------------------------PRESSURE PANEL-----------------------------------
    
    //----------------------------EVT_OH_PRESS_VALVE_SWITCH--------------------------
    Var 2703 Static, NAME PRESS_VALVE
    Var 5018 name PRS_CLOSED Link IOCARD_SW device 4 Input 96 Type I
    {
    IF &PRS_CLOSED = 1
    {
    V2703 = 0
    }
    ELSE
    {
    V2703 = 1
    }
    }
    
    
    
    Var 5019 name PRS_OPEN Link IOCARD_SW device 4 Input 97 Type I
    {
    IF &PRS_OPEN = 1
    {
    V2703 = 2
    }
    ELSE
    {
    V2703 = 1
    }
    }
    
    
    //---------------------------------------WIPER LEFT-------------------------------
    Var 2715 Static, NAME WIPER_L
    Var 5020 name WIPER_PARKL Link IOCARD_SW device 4 Input 101 Type I
    {
    IF &WIPER_PARKL = 1
    {
    V2715 = 0
    }
    }
    
    Var 5021 name WIPER_INTL Link IOCARD_SW device 4 Input 107 Type I
    {
    IF &WIPER_INTL = 1
    {
    V2715 = 1
    }
    }
    
    Var 5022 name WIPER_LOWL Link IOCARD_SW device 4 Input 104 Type I
    {
    IF &WIPER_LOWL = 1
    {
    V2715 = 2
    }
    }
    
    Var 5023 name WIPER_HIGHL Link IOCARD_SW device 4 Input 99 Type I
    {
    IF &WIPER_HIGHL = 1
    {
    V2715 = 3
    }
    }
    
    //----------------------------------------WIPER RIGHT---------------------------------
    Var 2716 Static, NAME WIPER_R
    Var 5024 name WIPER_PARKR Link IOCARD_SW device 4 Input 106 Type I
    {
    IF &WIPER_PARKR = 1
    {
    V2716 = 0
    }
    }
    
    Var 5025 name WIPER_INTR Link IOCARD_SW device 4 Input 100 Type I
    {
    IF &WIPER_INTR = 1
    {
    V2716 = 1
    }
    }
    
    Var 5026 name WIPER_LOWR Link IOCARD_SW device 4 Input 102 Type I
    {
    IF &WIPER_LOWR = 1
    {
    V2716 = 2
    }
    }
    
    Var 5027 name WIPER_HIGHR Link IOCARD_SW device 4 Input 103 Type I
    {
    IF &WIPER_HIGHR = 1
    {
    V2716 = 3
    }
    }
    Also wanted to point out that:

    WIPER SWITCH is a good example (temple) how to code ROTARY SWITCH this is where 1 variubale will have more then 2 values (same as ENGINE IGNITION SELECTOR) i think in my code i actually called it ENGINE_START OOPS (NOT A BIG DEAL REALLY)

    STROBE good example how to code for ON-OFF-ON SWITCH also here this is where 1 variubale will have (i think in most cases) 3 values 0,1 and 2 (same as ENGINE START SELECTOR) i think in my code i actually called it ENGINE_IGNITION OOPS (NOT A BIG DEAL REALLY)

    OVH_PRESS_VALVE_SWITCH good temple for MOMENTARY-OFF-MOMENTERY switch same are found on APU GEN panel.

    and

    SIMPLE ON-OFF switches are a joy 1 line of code

    Andy

  5. #5
    New Member
    Join Date
    Apr 2013
    Location
    Brussels
    Posts
    4
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: SIOC and 737PMDG - programing switches

    Andy,

    Thank you very much! I've looked through your code and started writing mine without any problem. So here are effects. Maybe will be useful for you. Instead of typing all variables once again you can just change dev and inputs. I've tested most of them but on one switch (have no switches installed, waiting for board cutted). I will try to write controls for leds now and will share the code too.

    Code:
    // FUEL PUMPS PANEL INPUTS
    
    Var 2645 Static, name FUEL_CRSFD Link IOCARD_SW device 0 Input 10 Type I
    Var 2646 Static, name FUEL_P1_AFT Link IOCARD_SW device 0 Input 10 Type I
    Var 2647 Static, name FUEL_P1_FWD Link IOCARD_SW device 0 Input 10 Type I
    Var 2648 Static, name FUEL_P2AFT Link IOCARD_SW device 0 Input 10 Type I
    Var 2649 Static, name FUEL_P2_FWD Link IOCARD_SW device 0 Input 10 Type I
    Var 2650 Static, name FUEL_PL_CTR Link IOCARD_SW device 0 Input 10 Type I
    Var 2651 Static, name FUEL_PR_CTR Link IOCARD_SW device 0 Input 10 Type I
    
    // BATTERY SWITCH
    Var 2618 Static, name BAT_GUARD value 1 // OPENING GUARD
    Var 2619 Static, name BAT_SWITCH Link IOCARD_SW device 0 Input 6 Type I
    
    // FASTEN SEATBELTS SWITCH
    Var 2638 Static, name SEATBELTS
    Var 5000 name SEATBELTS_ON Link IOCARD_SW device 0 Input 13 Type I
    {
    IF &SEATBELTS_ON = 1
        {
        &SEATBELTS = 2
        }
    ELSE
        {
        &SEATBELTS = 1
        }
    }
    Var 5001 name SEATBELTS_OFF Link IOCARD_SW device 0 Input 14 Type I
    {
    IF &SEATBELTS_OFF = 1
        {
        &SEATBELTS = 0
        }
    ELSE
        {
        &SEATBELTS = 1
        }
    }
    
    // EMERGENCY LIGHTS SWITCH
    Var 2636 Static, name EMERLTGUARD value 1 // OPENING GUARD
    Var 2637 Static, name EMERLIGHTS
    Var 5002 name EMERLIGHTS_ON Link IOCARD_SW device 0 Input 13 Type I
    {
    IF &EMERLIGHTS_ON = 1
        {
        &EMERLIGHTS = 2
        }
    ELSE
        {
        &EMERLIGHTS = 1
        }
    }
    Var 5003 name EMERLIGHTS_OFF Link IOCARD_SW device 0 Input 14 Type I
    {
    IF &EMERLIGHTS_OFF = 1
        {
        &EMERLIGHTS = 0
        }
    ELSE
        {
        &EMERLIGHTS = 1
        }
    }
    
    // WINDOW AND PROBE HEAT
    Var 2657 Static, name ENG_ICE_1 Link IOCARD_SW device 0 Input 11 Type I
    Var 2658 Static, name ENG_ICE_2 Link IOCARD_SW device 0 Input 11 Type I
    Var 2659 Static, name PROBE_HEAT_1 Link IOCARD_SW device 0 Input 11 Type I
    Var 2660 Static, name PROBE_HEAT_2 Link IOCARD_SW device 0 Input 11 Type I
    Var 2661 Static, name TAT_TEST Link IOCARD_SW device 0 Input 5 Type I
    Var 2662 Static, name WIN_HEAT_1 Link IOCARD_SW device 0 Input 11 Type I
    Var 2663 Static, name WIN_HEAT_2 Link IOCARD_SW device 0 Input 12 Type I
    Var 2664 Static, name WIN_HEAT_3 Link IOCARD_SW device 0 Input 12 Type I
    Var 2665 Static, name WIN_HEAT_4 Link IOCARD_SW device 0 Input 12 Type I
    Var 2667 Static, name WING_ANTIICE Link IOCARD_SW device 0 Input 12 Type I
    
    // HYD PUMPS
    Var 2653 Static, name HYD_ELEC1 Link IOCARD_SW device 0 Input 1 Type I
    Var 2654 Static, name HYD_ELEC2 Link IOCARD_SW device 0 Input 1 Type I
    Var 2655 Static, name HYD_ENG1 Link IOCARD_SW device 0 Input 1 Type I
    Var 2656 Static, name HYD_ENG2 Link IOCARD_SW device 0 Input 1 Type I
    
    // AIR BLEED PANEL
    Var 2593 Static, name BLEED_APU_SW  Link IOCARD_SW device 0 Input 0 Type I
    Var 2594 Static, name BLEED_ENG_1_SW Link IOCARD_SW device 0 Input 0 Type I
    Var 2595 Static, name BLEED_ENG_2_SW Link IOCARD_SW device 0 Input 0 Type I
    
    Var 2596 Static, name ISO_VLV_SW 
    Var 5004 name ISO_VLV_OPEN Link IOCARD_SW device 0 Input 3 Type I
    {
    IF &ISO_VLV_OPEN = 1
        {
        &ISO_VLV_SW = 2
        }
    ELSE
        {
        &ISO_VLV_SW = 1
        }
    }
    Var 5005 name ISO_VLV_CL Link IOCARD_SW device 0 Input 4 Type I
    {
    IF &ISO_VLV_CL = 1
        {
        &ISO_VLV_SW = 0
        }
    ELSE
        {
        &ISO_VLV_SW = 1
        }
    }
    
    // Var 2597 Static, name BLEED_OVHT_TEST Link IOCARD_SW device 0 Input 1 Type I - have to change type of the switch I think
    Var 2598 Static, name PACK_L_SW 
    Var 5006 name PACK_L_OFF Link IOCARD_SW device 0 Input 3 Type I
    {
    IF &PACK_L_OFF = 1
        {
        &PACK_L_SW = 2
        }
    ELSE
        {
        &PACK_L_SW = 1
        }
    }
    Var 5007 name PACK_L_HIGH Link IOCARD_SW device 0 Input 4 Type I
    {
    IF &PACK_L_HIGH = 1
        {
        &PACK_L_SW = 0
        }
    ELSE
        {
        &PACK_L_SW = 1
        }
    }
    Var 2599 Static, name PACK_R_SW
    Var 5008 name PACK_R_OFF Link IOCARD_SW device 0 Input 3 Type I
    {
    IF &PACK_R_OFF = 1
        {
        &PACK_R_SW = 2
        }
    ELSE
        {
        &PACK_R_SW = 1
        }
    }
    Var 5009 name PACK_R_HIGH Link IOCARD_SW device 0 Input 4 Type I
    {
    IF &PACK_R_HIGH = 1
        {
        &PACK_R_SW = 0
        }
    ELSE
        {
        &PACK_R_SW = 1
        }
    }
    Var 2600 Static, name BLEED_FAN_L_SW Link IOCARD_SW device 0 Input 0 Type I
    Var 2601 Static, name BLEED_FAN_R_SW Link IOCARD_SW device 0 Input 0 Type I
    
    // Var 2602 Static, name BLEED_TRIP_RST_BUT Link IOCARD_SW device 0 Input 1 Type I
    Let's keep an exchange. It will reduce work for both of us

    best,
    Leszek

  6. #6
    75+ Posting Member
    Join Date
    Oct 2012
    Location
    London ON, CA
    Posts
    106
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: SIOC and 737PMDG - programing switches

    sounds good, so far I wired 108 switches (positions s some have more then 1 position ie. rotaries mon-off-mon etc..) wireing seems to be the hardest part of the whole process...

  7. #7
    New Member
    Join Date
    Apr 2013
    Location
    Oulu, Finland
    Posts
    4
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: SIOC and 737PMDG - programing switches

    Hello!

    Finaly I found this great site I am trying to began make homecockpit fsx with pmdg 737 nxg. I have Opencockpits card and I load OC4NGX but I cant find file event_list_for_info.txt. I would like to know all possible variables.

    I visited Andy's website and you have done great job with cockpit. Is it possible to get information about your hardware?

    Best Regards
    Jouko

  8. #8
    75+ Posting Member
    Join Date
    Oct 2012
    Location
    London ON, CA
    Posts
    106
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: SIOC and 737PMDG - programing switches

    this file should be in root directory where oc4ngx was installed...
    my hardware.. well ...
    all runs from 1 computer in a nutshell :
    Intel i2700 o/c to 4.9 ghz
    2 video cards 1 gtx680 2gb, runs the 3 monitors on top in nvidia surround, 2nd card is gtx670 4gb, runs the 4 monitors for gauges , 1st officer and captain are split (the same) simple y cable then 1 monitor used by fmc and eicas
    all of the switches etc are controlled by opencockpits cards, also all panels gauges are open cockpit stuff except ovh, but again will be controlled by oc cards and I also used oc made announciators .
    i am very happy with overall performance of the sim fps/smoothness wise. sure you get occasional stutter here and there but I have to say it is overall enjoyable play I even fix the nusty stutter I was getting just before touchdown.. ( can be seen on video) I disabled water reflections !!! I think at this inst#nce sim was calculating if it should display reflection or not or whatever it was doing anyhow disabling water reflection solved the problem 100%.hope you find some of it use full


    Andy

  9. #9
    New Member
    Join Date
    Apr 2013
    Location
    Oulu, Finland
    Posts
    4
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: SIOC and 737PMDG - programing switches

    Hi,

    I am downloading Download - flightsim4fun.com files OC4BA 1.1and OCP4NGX_V2 . I cant find any event_list_for_info.txt when extracting files. Wondering what is wrong?

    Where did you buy your OVH panel?

    Jouko

  10. #10
    75+ Posting Member
    Join Date
    Oct 2012
    Location
    London ON, CA
    Posts
    106
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Re: SIOC and 737PMDG - programing switches

    hmm idk why you not seeing this file have you actually installed the software... ?

    my ovh is from prosimparts if you can afford extra apprx 300 then I would recoment oc's ovh, the quality of panels will be way superior to the ones from prosim, however if you just want to be able to have ovh and perfer to save some $$$ then by all means go with prosimparts.
    don't get me wrong prosim panels are very nice too, but they do have the budget feel to them, when I compered them to quality of other panels I got from oc for all my other stuff opencockpits are way superior and nicer over the prosim, better cut feels stronger etc... I took on real flying lessons, so I don't regret buying prosim, saved me some money, but otherwise I think I would be bit dissapointed ...

    if you don't find this file I post it here, but you should actually install the software and then it should appear in root directory where you installed it, if not I will post it here.
    Andy

Page 1 of 2 12 LastLast