KBrzez Posted February 25, 2024 Posted February 25, 2024 Hi and thanks for reading and offering some insight. I just downloaded the target software last night and activated those 5 LEDs on the throttle. Was thinking of a use for them. I made some overlays for the led lights. What I wanted to do, and was wondering if its possible. I wanted the first LED to be light when in NAV mode, the second LED to be lit while in GUN mode, third LED for CCIP the fourth LED for CCRP and the fifth for RKT or Master Caution flash. Is this even possible to acheive with target? Thanks again for your time and insight.
Rudel_chw Posted February 25, 2024 Posted February 25, 2024 9 minutes ago, KBrzez said: Is this even possible to acheive with target? yes, it is entirely possible ... check the TARGET Script Manual: LED and backlighting control The script language lets you control the LED state and backlighting intensity of several controllers, such as the HOTAS Warthog Throttle and MFD pack. T.A.R.G.E.T supports some devices that were developed a long time before the software was created. The MFD lighting support in the T.A.R.G.E.T software is a bonus. If you are experiencing issues like MFDs not responding: stop the script execution, simply unplug and then reconnect the MFDs and then relaunch the script. This can happen if the USB port was in "sleep" mode while the MFDs were not being used. Turn "ON" a LED Syntax: LED(&input device, LED_ONOFF,LED_CURRENT operator LEDnumber); The operator is used to control the status: - will turn "OFF" + will turn "ON" ^ will revert the LED status Example using a MapKey function (here, we turn "ON" LED 1 on the Warthog Throttle when the joystick Hat 2 Up position is pressed): MapKey(&Joystick, H2U, LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1)); Turn "OFF" a LED LED(&input device, LED_ONOFF,LED_CURRENT-LEDnumber); Notice that we've just changed the + for a - to turn off the LED. Now let's turn "OFF" our Throttle LED1 each time Hat 2 down is pressed. MapKey(&Joystick, H2D, LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1)); Change the status of a LED Sometimes, you may want to change the status of a LED, whatever its current state (to make it blink, for example). LED(&LMFD, LED_ONOFF, LED_CURRENT^LED2) MapKey(&Joystick, H4P, LED(&RMFD, LED_ONOFF, LED_CURRENT^LED2)); Each time we press the hat 4 push button, the LED 2 on the right MFD will change its state. The backlighting intensity is controlled nearly the same way. The difference is that we have different backlight steps. You can control the Backlighting intensity from null to full. The Warthog throttle offers 6 levels of intensity, while the MFDs have 256 different levels of intensity, from 0 to 255. The throttle and the MFDs share the same command, but as the throttle doesn't offer the same number of levels of lighting, you have to divide the full range of values: 0 to 42 is OFF 43 to 85 is level 1 86 to 128 is level 2 129 to 171 is level 3 172 to 214 is level 4 215 to 255 is level 5 Syntax: LED(&Input Device, LED_INTENSITY, value of the intensity) Let's imagine that we want to control the left MFD backlight power with the Warthog throttle EAC switch. MapKey(&Throttle, EACON, LED(&LMFD, LED_INTENSITY, 255)); MapKey(&Throttle, EACOFF, LED(&LMFD, LED_INTENSITY, 0)); Start a configuration with all lights in the right status. It's possible to initialize the LED status when launching the script. For this we use the advanced programming code (see later). The commands must be placed in the same part of the script as your MapKey functions. //initialize backlight power ActKey(PULSE+KEYON+LED(&Throttle, LED_INTENSITY, 129)); //set Throttle backlight power to middle ActKey(PULSE+KEYON+LED(&LMFD, LED_INTENSITY, 129)); //set left MFD backlight power to middle ActKey(PULSE+KEYON+LED(&RMFD, LED_INTENSITY, 129)); //set right MFD backlight power to middle //initialize LED status all "OFF" ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1)); //set LED 1 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2)); //set LED 2 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3)); //set LED 3 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); //set LED 4 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)); //set LED 5 OFF ActKey(PULSE+KEYON+LED(&LMFD, LED_ONOFF, LED_CURRENT-LED1)); //set left MFD LED 1 OFF ActKey(PULSE+KEYON+LED(&LMFD, LED_ONOFF, LED_CURRENT-LED2)); //set left MFD LED 2 OFF ActKey(PULSE+KEYON+LED(&RMFD, LED_ONOFF, LED_CURRENT-LED1)); //set right MFD LED 1 OFF ActKey(PULSE+KEYON+LED(&RMFD, LED_ONOFF, LED_CURRENT-LED2)); //set right MFD LED 2 OFF To take full advantages of the LED possibilities, we recommend that you learn the multiple output function call CHAIN, SEQ... Once you’re done, you will be able to interact with the simulator and play with LEDs at the same time, with just one action on a button. You can also control the LED or backlight with an axis (the Throttle friction control, for example) with Axmap2 (please see page 27). For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Recommended Posts