Printable View
For the 36V bots, can you connect the input in series and the output in parallel (Max voltage is 33.6V input) or would this kill them?
I also dont see a problem with using a seperate power supply in heavies and feathers. After all it is only another 5-10g bit more of an issue in an ant though.
Andy
The problem your experiencing is purely not having enough power in your receiver supply to do the job - this is by no means a problem with the receivers and has been known since spektrum receivers were being used. As geoff said, you should always use a seperate battery pack or BEC to make sure these problems dont occur unless you can guarentee that the built in BEC on the speedcontroller will supply the current.
If your having problems when running a seperate BEC thats rated for the job, then you are REALLY over stressing your battery packs with the drive motors.
Grudge Andy?...Im confused by the first part your post.
If Ive offended apologies.
It is never my intent to tick anyone off.
Woody
(Message edited by woody on August 23, 2008)
Not against you Woody. Im just having a sulk at Spektrum mate, throwing toys out of pram and all that.
Andy
another option... http://www.robotmarketplace.com/products/0-SPM5500.htmlhttp://www.robotmarketplace.com/products/0-SPM5500.html ?
Bit late on the link there Al, check out the archives.
Shows how much attention ive been paying!
known since spektrum receivers were being used
Grant,
As with all these issues, only known to those people around at the time and party to the discussion. Steep learning curve with all these things for someone newish to this.
Bear with me a little as I obviously have some catching up to do.
Andy
Does the DX5 not bind to more than 1 RX (IE: I cant use 2 bots on the same TX) ?
The DX5 is just a cheap 5 channel no frills version of the DX6i....I see no reason to treat it any differently.
David, the DX5 will bind to as many receivers as you like. What it says is that the DX5 does not model match to multiple receivers as it only has a single model memorey unlike the other spektrum TXs. So int that respect treat it like a DX6 but without any programmable features.
I like to keep my robots simple, so I dont need programming :) So long Interferance !
I think I will go with the AR500 Rxs as it sounds like a goer. When I get them I will put my two BR6000s up for sale on here
The complete package seems to be available on Ebay
http://cgi.ebay.co.uk/Spektrum-DX5E-Radio-Receiver-Suitable-for-Parkflyers_W0QQitemZ250288796905QQcmdZViewItem?has h=item250288796905&_trkparms=72%3A984%7C39%3A1%7C6 6%3A2%7C65%3A12%7C240%3A1318&_trksid=p3286.c0.m14http://cgi.ebay.co.uk/Spektrum-DX5E-...rkflyers_W0QQi temZ250288796905QQcmdZViewItem?hash=item2502887969 05&_trkparms=72%3A984%7C39%3A1 %7C66%3A2%7C65%3A12%7C240%3A1318&_trksid=p3286.c0. m14
dave- let us know what you want for em:)
Ill have one :wink:
Alan, do you happen to know if Dave got my eamil?
Dunno, hes working about 150 miles away, ill ask him when i speak to him, unless he posts here first...
thanks
not seen anything on my dlang@stanley....com address try sending to teamkronic(at)hotmail.co.uk instead.Cheers,Dave
sorry Dave, long day:) i meant Dave Young, sorry about the confusion, too many Daves on this forum! Theres 4 on this page:)
lol no probs dude :lol:
Just checked the BR6000 with the DX5e. Not conclusive but having tried it twice I was easily able to replicate the long duration for binding and the long duration for initial connection when you turn it back on.
That said, worked fabulously well with the receiver the AR500 which did exactly what it said it should do.
Andy
Will give the AR500 a try with the DX6i, see if it will bind into that, which would be nice. Off out now though.
Andy
The DSM1 receivers will often take around 30 seconds or so to start to connect as it says in the manual. the DSM 2 transmitters look for DSM2 RXs first and if they dont find one after 30s they then look for dsm1
I know that, weve been through that conversation before when the DX6i was initially released, but it was more than that. As I said, I only did it twice, so it needs a bit more of a look at.
The BR6000 can take an age to bind/connect to the DX6i and may need the tx turning on and off again a number of times. This is what was occurring.
I will have a look at it again over the weekend though and let you know whats happening in a bit more detail. Good or bad. I will also pay a bit more attention to the actual time it takes.
I actually quite like the DX5e now Ive got one and it sorts out a lot of problems with BOOMs control when used with the AR500. The tx is cheap and simple and it looks cheap and simple. Build quality isnt as good as the DX6 or DX6i but as I said its cheap and simple!
Andy
How about failsafing on the other channels with the AR500 Andy? Does it work like we want it? If so it is a very nice option if one doesnt need the computer stuff.
Havent tried it Leo. BOOM! is very simple in that it is a two wheel drive box on wheels. It uses a scoprion XXL speedo which has a built in failsafe which worked fine on all directions.
I think Woody said it just killed the output and we would need one of the external failsafes. It gives a signal which you can read so itll work one way or another.
Oh and just looking round the web it will work with the DX6i, but Ill give it a try anyway.
Andy
I think Woody said it just killed the output and we would need one of the external failsafes
The AR500 shouldnt output anything on 4 of the 5 channels and it should be possible to set a failsafe position on the 5th.
NO signal input to your controller = NO output from the controller to motors.
In fact nothing at all should happen with any R/C device if there is NO signal input... it should effectively be dead....in the event of a signal loss a R/C servo will sit at its last instructed postion ( it might coast if its already moving ) but wont actually hold any position.
No signal also means that a std plug in failsafe will work and one could be used to move the afore mentioned servo to a failsafe position.
Not many , if any bots will need to use a seperate failsafe but its nice to have the option available.
Simply plug your current speed controller/s and R/C switches into the AR500 ... without the addition of any extra plugin failsafes ...and IMO 98% of bots will be perfectly safe and pass Tech check.
(Message edited by woody on September 11, 2008)
Provided it is correct what they say in the manual.
Andy .... You stated that you tried out the AR500 with an XXL Controller....did you happen to notice if the XXL Status LED flashed indicating a lost signal when you turned off the transmitter?
The Scorpion XL indicates the status of the R/C signal by various blink patterns on the
Status LED. Here are the blink codes:
Solid - all signals good, motors enabled
Slow blink - searching for required radio channels especially at startup
Fast blink - R/C signal lost or pulses out of legal range
Very fast blink - Calibrating radio signals (after Cal jumper placed see below)
Nope, but I can have a look over the weekend.
Will be sticking one in Hydra too if it works with the DX6i, which it should, so I can also test the failsafes with the electronize switches for the axe and flipper. Hopefully thatll just confirm Woodys comments.
Andy
Andy...The elecronize switches should be fine plugged straight into the receiver without the addition of an external inline failsafe.
Look forward to the results of your testing.
Me too, because then the 2.4GHz market will be accessible for all roboteers. The price of 3 pairs of 40MHz crystals would amount to the same cost of this entire set.
Had a bit of time today to look over the systems in a few configurations.
In BOOM! the DX5e and AR500 combo worked as I said before (as you would expect)
In Hydra I started off looking at the BR6000 with the DX5e. Took ages to bind etc. I was also fitting a 6V BEC in there as well and after that was fitted it all worked very well and seemed to be ok. Bind was quick and connection was about 3secs.
Changed the RX for the AR500 and tested with the DX6i. Bound in very quick and connection always almost immediate. One thing I found a bit wierd is that sometimes I get an orange lights and sometimes I get a slow flashing orange light (without bind plug). Doesnt seem to affect operation but just not what I was expecting.
In each case I tested the failsafes and they all worked ok with the AR500 and the BR6000.
Anyway, well be running BOOM! on the DX5e and AR500, Cylon on the DX5e and BR6000 and Hydra on the DX6i and the AR500 at Portsmouth, so should get a lot of feedback on performance in combat.
Andy
Sounds good.
The flashing lights on the receiver is due to an inbuilt feature in the RX/TX.
Its supposed to be an indication of loss of signal or loss of power to the RX. If you turn the RX/tx on, and then turn off the RX, when you turn it back on it will flash to say that you have lost power or signal. To reset it, you need to turn off both the RX and TX. Maybe not always usefull for the robots, but it come in very handy with planes and helicopters when trouble shooting problems.
Ahhh! Thatll be why then cos I was checking it on failsafes by turning off the tx and so on, so its just working as it should.
Andy
Andy, that is awesome news, thank you for testing. This means that you can have a 2.4GHz set (TX and RX) compliant with the rules for $100.00 usd.
As Ive said before Leo. I am not generally convinced yet. The problems with the DX6i/BR6000 didnt really raise their head until they were used in combat. That will be the real test.
Andy
I doubt the DX5e and AR500 combo will be a problem since they are both DSM2 and designed to work with each other (They are from the same set). My sneaky suspicion is that it is the DSM2 - DSM combination that is going haywire in the DX6i with the BR6000.