Radio Link 2.4GHz Tx & Rx

[RogueTwoRobots]

Forgot to add, I ran Drumroll in a busy whiteboard at the weekend on 40MHz. The robot has no suppression components fitted. I think every other robot in the fight was on 2.4GHz and I wasn't aware of suffering intereference at any point throughout that fight.

The rules change in 2011 for featherweights so it probably doesn't matter too much but based on this (and I know it's only one case, so not very conclusive) the 2.4GHz units aren't drowning out the 40MHz users.

[RogueTwoRobots]

Copied from the antweight forum, a copy of the CE certificates. There was some doubt cast over the legitimacy of the CE marking on the transmitter:

http://www.giantcod.co.uk/forum/downloa ... &mode=view

Not sure why the CE marking on the actual transmitter is different from the way it's supposed to look, but it seems correct on the certificates.

[RogueTwoRobots]

Sorry to dredge up an old thread but just got a point to mention and a question to ask:

The effects described above about the tx/rx not connecting when switched on while other 2.4GHz units are being powered up in close proximity occurred again at Edinburgh. It was the first fight and I had forgotten to turn on the tx and rx switches before everyone started powering their Spektrum units up. For all the following fights I took this approach and there was no problem.

After the end of the last fight though, I powered the robot up just to check everything was still running and once again I had the problem of the tx/rx not detecting each other. This time there were no other 2.4GHz units in use, and even once I was home and tried it again, the same thing happened. I've tried re-binding it and using different receiver battery packs etc but still no luck. I haven't had time to thoroughly try and diagnose the problem, but I'm beginning to think that this is a problem that I don't want happening during something like an important UK champs fight, so I'm looking to get a different 2.4GHz unit as part of the new Drumroll build.

My question is, for those of you using the Planet 5 systems, has this sort of problem ever occurred during the arming up phase in a battle? Or am I better off just spending a bit more on, say, a DX5e and getting a reliable connection?

Thanks

[widow_twanky]

Sorry to dredge up an old thread but just got a point to mention and a question to ask:

The effects described above about the tx/rx not connecting when switched on while other 2.4GHz units are being powered up in close proximity occurred again at Edinburgh. It was the first fight and I had forgotten to turn on the tx and rx switches before everyone started powering their Spektrum units up. For all the following fights I took this approach and there was no problem.

After the end of the last fight though, I powered the robot up just to check everything was still running and once again I had the problem of the tx/rx not detecting each other. This time there were no other 2.4GHz units in use, and even once I was home and tried it again, the same thing happened. I've tried re-binding it and using different receiver battery packs etc but still no luck. I haven't had time to thoroughly try and diagnose the problem, but I'm beginning to think that this is a problem that I don't want happening during something like an important UK champs fight, so I'm looking to get a different 2.4GHz unit as part of the new Drumroll build.

My question is, for those of you using the Planet 5 systems, has this sort of problem ever occurred during the arming up phase in a battle? Or am I better off just spending a bit more on, say, a DX5e and getting a reliable connection?

Thanks

Jamie,

Planet 5 has always worked fine for me with absolutely no issues with respect to binding and the like. What I do dislike about it is the way it is bound. You press the button and turn the tx on with no other action needed. This means if you get a scenario where you press your button and someone else turns their tx on, your robot is under their control. A lot less likely when you have to pull a bind switch.

Also I read that the throttle channel fails safe to the position your turn it on at. I've not tried this but something to consider when using the throttle for the spinner.

Anyway, have found the planet 5 to be a fantastic little set but hopefully someone will have looked at the issues I've raised. Personally though I would want digital trims for anything which is as nasty as drumroll because everything then turns on how i want it to without any chance of me making a mistake.

Andy

[RogueTwoRobots]

Thanks for the info Andy. The binding issue you described can happen in a similar way with the Radio Link sets. You power up the tx then press a bind button, so if any other Radio Link tx is on in the vicinity there is a chance that the receiver will bind to another unit. I guess it's just a potential risk associated with cheap 2.4GHz units.

Had a bit of trims discussion at Edinburgh actually. Liam's robot was always moving when the link was plugged in and it took a while to realise that the trims were miles out; it couldn't be seen because they were digital. I said then that I prefer mechanical trims because you can see where they are positioned, but I hadn't considered the benefit of digital trims that you have mentioned.
Common sense would dictate that you check all your stick positions and trims before powering things up but we all know most of us never do. I tend to just assume that they will be set in the position I left them in, which is a habit I should probably try to break. I always try to position my robot in such a way that the wheels are off the ground during arming up, just in case of offset trims and the locking pins help out in the event of weapon trim offsets. I guess seeing the mechanical trims having been knocked out of place is fine, the only problem I find after that is trying to remember what position they should be in!

[elobire]

the support on giantcod is terrible, my reciever is broke and after creating a support ticket i have had no reply in 48 hours.
going to phone them later.

[peterw]

I am suprised at that when I thought I had a problem with a receiver they were very quick to respond something I didn't really expect on such a low cost item.
Mind you 48hours from your post means you complained Saturday lunch time so they probably didn't pick it up until this morning.

[elobire]

I am suprised at that when I thought I had a problem with a receiver they were very quick to respond something I didn't really expect on such a low cost item.
Mind you 48hours from your post means you complained Saturday lunch time so they probably didn't pick it up until this morning.

your probably right, i think il wait another day.
EDIT: just got a email, have to send the receiver and trasmitter back for testing.

[peterw]

Before you do that have you checked that you have bound the transmitter and receiver together correctly.
See procedure cut from their site.

The bind procedure is the easiest, quickest, no fuss seen to date, this is done by powering up the transmitter and receiver, then a tiny button positioned at the end of the receiver case is pressed once. A green LED flashes for a second or so then stops, that€™s it, job done!

[elobire]

Before you do that have you checked that you have bound the transmitter and receiver together correctly.
See procedure cut from their site.

The bind procedure is the easiest, quickest, no fuss seen to date, this is done by powering up the transmitter and receiver, then a tiny button positioned at the end of the receiver case is pressed once. A green LED flashes for a second or so then stops, that€™s it, job done!

tried that, i did have it working fine before. not sure why it broke.