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
Yes I connected in the button SYNC.If it is normal then everything goes well.Thank you very much for your time(weather) which you granted me
Ok, I updated the code to have "Reverse" when LT is pulled. Just re-download and re-flash chip.
Thanks for the code Seth. I will try it once I buy a new chip. I have a question can you use these points instead of the originals?one point would be sync and the other one B trace. I say this because in my opinion the installation would be easier (you would have nearly all the points on the back side)BTW this code doesn´t need resistor?
Is this a good time to mention that the code stops working after 255 boot-ups? Edit: I'm totally kidding about the code ceasing to work.
Its hard to understand your wording but if u look under rules of code use codes are NOT to be used for monetary gain. Its against forum rules. Still this doesn't stop people from selling others work. This more than likely is not the case with Seth but a lot of other programmers stop posting sourse codes all together because of this. Because of other abusing these free codes it makes everyone else suffer. Most of us just like to share this with friends and family and not try to make a buisness off of it.I hope in your case this isn't your example of embarrassment. To me this is down right stealing. Its stealing from the creator of the code and his intended usage & it steals this from others in here who use these for hobbies or to share with friends.
All kidding aside, When RF codes first hit market a few years ago, chives and king mike released one of the first basic rapidfire codes that would cease to work as you state. Then Hazer released his code and the opensource went wild. Hazer released his code in such a public manner to flood the market with free chips so the mod shops could not charge enormous prices for a 2$ chip. The more opensource or free codes (seth's code is not opensource but infact it is a free code) we put out there the more control we have on the market. keep the codes coming.
There's no problem at all charging your friends or people for your instillation services. The problem is these eBay hounds that take advantage of a good thing. Its good to post these free codes as matt said to regulate on companies overcharging but it sucks that people do this because it pushes some people away from posting new sourse codes. It was inevitable for this to happen so its no use getting bent over about it, but its just nice to stay classy about it and use these codes for hobbies friends or other people that Dont have the money or means to install these themselves. I have modded all my friends controllers and I do charge them part cost and ironically 20$ for my instillation labor. I Dont go out of my way and try to profit off this though. Its a hobby to me and I'm more than happy with my income from my regular job!
Look at it this way: The people buying from Ebay are not looking to research all that goes into programming this themselves. They sinply want a kit or pre-modified controller. If the seller has a reasonable price, this works for the buyer. If he does not have a reasonable price, nobody will buy it. These Ebay 'scags' as people call them are simply attempting to make some money from performing the work that the buyer does not want to get into. Even if the seller is only selling a kit, this kit includes a programmed chip, wire, tacts, etc. These items are not cheap unless purchased in bulk. An Ebay buyer is not looking to buy a bag of 100 tacts, or a 100' spool of wire, they dont want to purchase a programmer and learn how to use it. They just want the hard stuff done for them. If the seller is outrageous, he will be outsold by another seller who prices accordingly.
Does it do it if you are in Mode 0? Does it do it in a mode that doesn't have Rapid Fire associated to it?I have three theories I am trying to eliminate.1) There is some sort of bug in my code that randomly operates the trigger. (Unlikely,...but possible.)2) The PIC is losing sync with the controller and improperly registering the start of a new frame. (Very possible.)3) The threshold I set for the triggers is too aggressive. (Also very possible.)I haven't heard this from anyone else, but that doesn't mean it isn't a potential problem that I need to fix.