You ALSO can ask P. Cesarrato a "kit" of his servo tester ... he sells it @ " friend price " ( no much more than the components price ...)
I join some description of the used tester manual ...
Add to that I have been dealing with R/C stuff for ... over 40 years. If I tell you to forget about Hitech products, It's ALSO because I personnaly have tested, repaired ... and thrown their products to the Wastebox !!!
Want some copies of the ( constructive ...) mails I've sent to and received from their technical staff ???
They even do agree their servos are " not so good " ... and , of course, always promise they will correct them !!!
Talking price ...
you can get much, much better prices ( ~ half what you tell !!! )... but may be NOT from your local reseller or any " robotics shop " !!!
Also have a look to Futaba S3302 ...
Alain
Last edited by Acetronics2; - 4th August 2010 at 22:40.
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
So far i have got my old Sanwas from www.rapidonline.co.uk and my new Hitec servos from www.servoshop.co.uk. There isnt a local place i can go to and buy any but if you can recommend a website (preferably in the UK) then i will have a look.
Hmm, Even if these servos arnt very good i still dont believe that 3 brand new ones would suddenly fail in the same way at the same time. There must be some reason behind it. My biggest worry is that i spend yet more money on more expensive servos and only get the same problem
All three might fail at the same time being they are all driven by the same in-correct code? You have already stated that the code was not good and with out the servos connected to the MCU all was well...
Dave
Always wear safety glasses while programming.
Thats true. The code was originally wrong. It was causing very short pauses of about 6ms. I assume digital servos are fine with really short gaps but could something like that actually break the servos? Or could it just be that the invalid code caused the initial buzzing and the heat caused the rest of the damage?
IF those 3 wonderful servos are " so good " ... why not test their behaviour into the skull, with a so simple 555 based servo driver ( 10 components is a maximum ) that will produce neat-known signals ...
would certainly save time to everyone and, may be money to you ...
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Ok, sounds like a good idea. Ill try and make a 555 circuit tonight. Im pretty confident the signal from my circuit is fine now (it works on the digital servo and the old Sanwa). Im all for saving money though so ill see how the 555 goes.
Originally Posted by The Master
Bookmarks