Posts: 25 Threads: 4 Likes Received: 6 in 3 posts Likes Given: 10 Joined: Jun 2023 Reputation: 0 14-Dec-2023, 06:16 AM (This post was last modified: 25-Dec-2023, 11:22 AM by maxer.) Hi. I have this transmitter Jumper T Pro with bottom right toggle switch (earlier versions have pot in there). In EdgeTX / Hardware screen it shows under Pots: "S2 --- pot with detent", but it is physically a latching switch. You cannot change it from pot to switch there... It kinda works, shows channel output changing from 1000 to 2000. But it is in reverse: - when switch is pressed and latched down, output is 1000 - when switch is depressed and latched in up position, output is 2000 I want to use it for Arm/Disarm in Betaflight. I tried to toggle Outputs / CH5 / Direction = INV, but then it gets stuck at 1000, not reacting to switch. I tried same INV setting on momentary switch SC, and INV works as intended. So something is wrong with S2 in firmware, I suspect because it thinks its a pot... I need to invert it because ExpressLRS specifically asks for disarm value = 1000, Arm = 2000. 1. How fo a get firmware that lists S2 as a switch and not pot? 2. Why INV does not work on S2 and works on SC? I updated EdgeTX to 2.9.2, but S2 is still a pot Help Much appreciated! Related post • Posts: 2 Threads: 0 Likes Received: 2 in 2 posts Likes Given: 1 Joined: Dec 2023 Reputation: 0 24-Dec-2023, 05:42 PM (This post was last modified: 24-Dec-2023, 05:57 PM by sternpython.) Hello, I had the same problem as you but I managed to find a way. For my latching switch, pressed = 1000 and unpressed = 1500. I left S2 as pot, but I setup a logical switch to detect if the pot value <-80, "L01" activates. L01 is then used as a source to CH5. For disarming, I setup a special function to override CH5 to -100 when !L01 is detected. Let me know if you need pictures of my setup One thing that I find fascinating is that why Jumper had designed the latching arm switch as active-low when pressed rather then active-high. A hardware mod might be possible though. Which would simplify alot of things. Anyway, hope this answers your question EDIT: I did not re-calibrate the sticks after installing the switch. After recalibrating, there is a much simpler way. Just change the weight of CH5 in mixers tab to -100 and it should work. Posts: 2,369 Threads: 74 Likes Received: 1,336 in 996 posts Likes Given: 771 Joined: Apr 2022 Reputation: 41 Can't you setup a new mix, bind it to that switch and then set it high or low. I don't know on the V2. i only have the first version of the T-Pro. The biggest fun is getting the 6 buttons in the middle to work as individual switches. I had to watch JB's video on it three times to get a handle on it. Try Not, Do or Do Not - Yoda • Posts: 25 Threads: 4 Likes Received: 6 in 3 posts Likes Given: 10 Joined: Jun 2023 Reputation: 0 25-Dec-2023, 01:45 AM (This post was last modified: 25-Dec-2023, 02:54 AM by maxer.) (24-Dec-2023, 05:42 PM)sternpython Wrote: For my latching switch, pressed = 1000 and unpressed = 1500. Hmm... mine is different, On the radio itself, in Channel Monitor screen, I see 0 value when pressed (mid position, aka 1500 pwm) and +100 when un-pressed (2000 pwm). I have this in radio.yml after calibration: POT2: mid: 0 spanNeg: 0 spanPos: 1009 And another strange thing about it, in Betaflight Configurator / Receiver tab, CH5 moves from 1000pwm pressed to 2000pwm un-pressed! I hope someone can explain it, my head hurts. Tried Weight = -100: ------------------------- Pressed on Radio = 0 (mid position, aka 1500 pwm) Pressed in BF Configurator = 1000pwm Un-pressed on Radio = -100 (1000pwm) Un-Pressed in BF Configurator = 1000pwm So in BF, with Weight = -100, it does not move at all. I have fresh install of EdgeTX (erasing old radio.yml), its unlikely that I messed it up, but with me its always a possibility • Posts: 25 Threads: 4 Likes Received: 6 in 3 posts Likes Given: 10 Joined: Jun 2023 Reputation: 0 25-Dec-2023, 01:58 AM (This post was last modified: 25-Dec-2023, 02:12 AM by maxer.) (24-Dec-2023, 06:15 PM)Pathfinder075 Wrote: Can't you setup a new mix, bind it to that switch and then set it high or low. You need to be more specific in "set it high or low", there is more than one way (24-Dec-2023, 06:15 PM)Pathfinder075 Wrote: I don't know on the V2. i only have the first version of the T-Pro. We are talking V1 here, mine does not have "V2" in product description and its not OLED. They shipped some V1s with 2 pots, and some with 1 pot and 1 switch. • Posts: 2 Threads: 0 Likes Received: 2 in 2 posts Likes Given: 1 Joined: Dec 2023 Reputation: 0 25-Dec-2023, 10:43 AM (This post was last modified: 25-Dec-2023, 10:44 AM by sternpython.) (25-Dec-2023, 01:45 AM)maxer Wrote: Hmm... mine is different, On the radio itself, in Channel Monitor screen, I see 0 value when pressed (mid position, aka 1500 pwm) and +100 when un-pressed (2000 pwm). I have this in radio.yml after calibration: POT2: mid: 0 spanNeg: 0 spanPos: 1009 And another strange thing about it, in Betaflight Configurator / Receiver tab, CH5 moves from 1000pwm pressed to 2000pwm un-pressed! I hope someone can explain it, my head hurts. Tried Weight = -100: ------------------------- Pressed on Radio = 0 (mid position, aka 1500 pwm) Pressed in BF Configurator = 1000pwm Un-pressed on Radio = -100 (1000pwm) Un-Pressed in BF Configurator = 1000pwm So in BF, with Weight = -100, it does not move at all. I have fresh install of EdgeTX (erasing old radio.yml), its unlikely that I messed it up, but with me its always a possibility My radio.yml (after sticks and Pot re-calib) shows POT2: mid: 512 spanNeg: 504 spanPos: 504 With this, I get this as raw data when I have S2 as a source to CH5: Pressed on Radio = -100 (1000us) Unpressed on Radio = 100 (2000us) After applying weight of -100 in mixer, I get the desired output. Pressed on Radio = 100 (2000us) Unpressed on Radio = -100 (1000us) I'm not sure why your radio.yml is different from mine. That said, maybe you could try to play around with the offsets and weights. Here are my settings. 2nd Option You could try to use a logical switch just like my previous settings, using a>x with V2 = -10 (assuming the values you got before you did the -100 weight), L05 activates. L05 can then be used as a source for CH5 in mixes. Posts: 25 Threads: 4 Likes Received: 6 in 3 posts Likes Given: 10 Joined: Jun 2023 Reputation: 0 (25-Dec-2023, 10:43 AM)sternpython Wrote: My radio.yml (after sticks and Pot re-calib) shows POT2: mid: 512 spanNeg: 504 spanPos: 504 This was the fix! Edited my radio.yml and now everything works as in your T Pro. For ones reading this, also set "manuallyEdited: 1", otherwise radio will reject it saying its corrupt. Thank you and merry Xmas Posts: 2,369 Threads: 74 Likes Received: 1,336 in 996 posts Likes Given: 771 Joined: Apr 2022 Reputation: 41 (25-Dec-2023, 01:58 AM)maxer Wrote: You need to be more specific in "set it high or low", there is more than one way We are talking V1 here, mine does not have "V2" in product description and its not OLED. They shipped some V1s with 2 pots, and some with 1 pot and 1 switch. Mine is one of the very first ones with two pots. While I did think about buying the switch and adding it, once i made the other six buttons work as independent switches I had more than enough to fly with. Also the pot that it would replace is currently used as a throttle modifier to cut it by 50% for when I'm testing. Glad you found a solution. Try Not, Do or Do Not - Yoda • |