Please help support the site by donating at the link below.https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8ZRU34U47BESW
My code uses the FIRERATE for both pull and release timing. In normal mode, its the actual hex value. In COD5 mode, I use half that rate for the release, and 1.5X the rate for the pull. When RF is active, it latches the output in one state always (low for CG, high for MX). It then only toggles the pin from input to output for the pulses. When RF is off, the pin always stays as an input.For burst mode, the pin remains an input until the PIC sees a change in the trigger. Then it activates the programmed number of shots and waits for the trigger to get released before monitoring again.
Is this the way t0pfire (v2 –r6) works t0p? added@edit..This was just incase ya missed it t0p.. No disrespect implied here, just read it and I felt it sounded rude... your doing a great job
Please make sure you have everything wired correctly. If you turn the LEFT trigger rapidfire off. does the problem still occur?
Yeah i still think its something to do with the release timings being too fast.As i said, I can mess around with it when i get time :-)
Yeah, That could be a possible update in 00.3. I would have to remove left trigger RF. or a LED indication. Seperate HEX would be good for this, a modded t0pfire for COD.
What about using a quick press of the tactile buttons to change mode, and LT + tactile to turn rapidfire off? I think it might be better