I’ve got 2 8th grade teams, more turn-out than expected and 2 robots. I want to share an RC controller with a Vexnet tx upgrade between the 2 bots for ‘development’ purposes.
I have 2 bricks with vexnet rx’r upgrades, each has a wireless key. I have an RC controller with a vexnet tx’r and a third wireless key.
I’ve downloaded the default vexnet brick firmware and master code to both bricks. Using the exact, same procedure for pairing I can get one combination to pair in under 5 seconds, the other combination will never pair, either by USB cable connection or wirelessly. Can anyone explain what’s going on here?
It was my impression that tx’rs and rx’rs and any keys could be interchanged and a vexnet ‘local’ connection could be established with any combination by pairing. I’ve got a ‘golden’ RC/vexnet tx’r that’ll pair with multiple brick/rx’rs/keys and I’ve Tx’r upgrades that will only pair with 1 and only 1 combination or rx’r. Can anyone explain this?
I’ve spent literally hours troubleshooting these issues. I’ve got a master’s degree in engineering and 20 years of industry experience so I understand ‘the concept’. I’ve got a tourney coming up on March 6 and the other advisors and I WERE joking that we may have to go back to crystals.
**The VEXnet R/X unit (the part that connects to the Microcontroller) is the unit that maintains it’s connection specific information. This includes secure information such as an SSID, IP address, etc. The T/X unit receives it’s connection specific information upon tethering with an R/X unit using the A-A USB cable. Once this link is established - the units are then paired. The USB keys themselves are wireless adapters containing no connection specific information other than a MAC address. They are fully interchangeable.
In direct response to your issue - we have since found that there may be some pairing issues regarding units with previous versions of code. You may experience issues when trying to pair older units with newer ones.
We have developed a utility that allows us to remotely check your units for code versions, as well as perform updates if necessary. Most code related connection issues can be corrected in this way. In rare occasions with some of the earliest units - some low level code needs to be updated here at IFI as it involves having a direct connection with the unit.
If you are unable to correct your issues using some of the trouble shooting steps and possible resolutions as described here: https://vexforum.com/showpost.php?p=101971 please contact us directly as your issue might involve a software update.**
I have another Rx’r that flashes the game led at a regular rate. Is this also a candidate and symptom of a software revision issue or can you direct me on this to somewhere else? I see that my post/thread on this issue has been deleted making me assume that my two threads were closely related??
Thanks for the feedback, it provides some direction.
To follow up - I believe we resolved this issue over the phone today, involving a software reset of your R/X unit.
If you did, it wasn’t with me and I don’t believe any of the other advisors would have taken on that task without letting me know.
Calling during business hours is not an option for me. Can you post the reset procedure here, please.
**The the utility I refered to is provided on an as needed basis and requires a unique serial number to be entered at the time of usage. This needs to be done over the phone. It is also possible that your issue can be resolved through direct trouble shooting. What would be a good time to contact you?
The other option is for me to issue you an RMA.**