
Posted by TagFerret
![]()
on June 1, 2009, 2:24 pm, in reply to "Re: LCX Project Needs"
"Tape on the lights? Are they simply too complicated to put a simple toggle on?"
Adding a toggle to turn the Strength and Ammo lights completely off isn't too bad -- there is a ribbon cable to each set of LEDs. One of the leads in each ribbon cable is a common. A double-pole double-throw switch could interrupt both. But you'd need to switch ten seperate resistors in or out do do dimming, since each LED has it's own current limit resistor. So if you want dim rather than off, tape or paint is the way to go.
As LazerBait said, you can hold the hammer down at power-up to inhibit recoil during play -- that will also stop the hammer flash from occuring since it is triggered by a switch in the recoil mechanism.
You'll have to pain the clips black, or cut the wires tot he clip LED, or do the pushbutton reload mod, to prevent the clip from lighting up during reloading.
- - - - - - - - - - - - - - - - -
"We did some range testing last night on the LTX and TMB. It seems that Laser Challenge Vests can pick up the hit signal better than the TMB/LTX sensors since we got better range test results from the LC Vests."
Not surprising -- everything I've seen in discussions of LC range testing and the whole "Magic TMB mod" tells me that most LC vests are simply looking for 2 complete cycles of the 250 Hz signal, and if that is seen they take a hit. IN other words, they only need to see about 8 msec clean of the 150 msec tag signal, and they will take a hit. This explains why they are so much more susceptible to false hits from bright sunlight, and why they work so much better at night. In ELS mode, the performance is probably very close to that of LTTO/LTX since both require seeing the entire signal in order to decode it.
This would also explain why the "Extreme" (Radar Extreme, Gotcha Extreme, etc) vests do NOT accept LTTO/LTX tags -- they have more involved signals they are looking for, and as such are more picky about making sure the signal is exactly correct.



Message Thread:
![]()
« Back to thread