Hi there,
I am working on trying to fix joystick issues faced by an organisation in our region,
My guess is that the joysticks were unplugged during the firmware update, affecting 5 joysticks in one organisation. There is no way I am able to locate to force firmware updates on the joysticks themselves, only the v5 brain.
I’ve not had much time to test myself but can get more details if needed.
The joysticks. However, the behaviour, as explained to me, is:
An inability to wirelessly connect to the brain
Connection over wire only partially works
Cannot run driver skills or driver control
Can run Autonomous coding skills from the joystick (I am unsure if this actually enables it on the brain)
As this has affected five joysticks in one organisation, it is a costly issue, and we would ideally like to fix it. Any help that could be offered would be appreciated.
If firmware update fails then the joystick would usually show a red screen with an indication to tether to the V5 brain.
This is correct, there is no way to force a firmware update from VEXcode or other tools.
Can you elaborate on what does and what does not work.
It sounds as if perhaps smartports are damaged and communication with the brain is intermittent.
Having just sat down and tested myself, it appears the radio connectivity is functioning.
The issue appears to be the controller is permanently locked into autonomous. Looking in the field control port and smart ports, no pins appear to be bent to my view (images attached)
When utilising an old manual field controller, the robot enters the disabled state correctly; however, driver control results in autonomous activating. The autonomous program symbol is permanently visible on the screen, as pictured. I will try continuity testing the field control port to validate if the autonomous pin is shorted. Still, my multimeter probes are a bit unwieldy, and I do not have a cut ethernet cable right now.
The baffling part of this is how all of this organisation’s
Joysticks have this same behaviour, and I cannot think of anything blatantly obvious that would result in this.
Continuing my diagnosis, the joystick, when set to Bluetooth, displays a red screen stating it cannot use Bluetooth - which, with my joystick on the same brain, runs fine on Bluetooth.
The radio screen on the brain shows competition mode when no competition switch is connected as opposed to my personal joystick reading Drive and Data.
The issue persists with radio data being turned on or off.
I can provide any more details if needed and apologies for my incorrect statements before.
Typically this happens when a smartport cable is (accidentally when tethering to the V5 brain) plugged into the RJ45 competition port and damages internal components.
Right are there any potential fixes for this, or an option to send it off for repairs? I presume repairs would be difficult as you mention damaged internal components. With being in nz it is difficult to get parts in and out of the country so if there is any option in NZ that would be appreciated but I understand if not.
