Wireless Controller V2 Dead TX Pin

I ordered this controller for a robot project in the spring, just getting around to using it.
Got the code working on the XBEE's, everything was great....
Then TX out for Serial1 (PIN 21 uC, Pin 2 XBEE) started being eratic. Strings would not complete on the serial line. AN hour later it stopped working. It's stuck high. I've verified this right at the XBEE header. I'm also able to make the vibrate motors work via serial, in both directions (Swapping the XBEE's from controller to robot) so I'm confident that the problem isn't with the xbees.
I've tried using it as just a on/off pin and no luck. I've tried running off the usb programmer, as well as a stable 5VDC source, no change.
Unless you guys have some other ideas on how to troubleshoot, I'll likely need to order a new main board for the controller, something I see you don't sell separately....
Some help would be appreciated.
Thanks!
Got the code working on the XBEE's, everything was great....
Then TX out for Serial1 (PIN 21 uC, Pin 2 XBEE) started being eratic. Strings would not complete on the serial line. AN hour later it stopped working. It's stuck high. I've verified this right at the XBEE header. I'm also able to make the vibrate motors work via serial, in both directions (Swapping the XBEE's from controller to robot) so I'm confident that the problem isn't with the xbees.
I've tried using it as just a on/off pin and no luck. I've tried running off the usb programmer, as well as a stable 5VDC source, no change.
Unless you guys have some other ideas on how to troubleshoot, I'll likely need to order a new main board for the controller, something I see you don't sell separately....
Some help would be appreciated.
Thanks!
2016-09-22 10:45:14 Hi Murray Chris,
I mean if you want to establish connection between gamepad and robot when you are going to use BLE module inserted to the XBee socket, the BLE module must be our DFRobot BLE product, it doesnt support other brand BLE.
This is only a reminder.
Wendy.Hu
I mean if you want to establish connection between gamepad and robot when you are going to use BLE module inserted to the XBee socket, the BLE module must be our DFRobot BLE product, it doesnt support other brand BLE.
This is only a reminder.

2016-09-22 10:45:14 Hi Murray Chris,
I mean if you want to establish connection between gamepad and robot when you are going to use BLE module inserted to the XBee socket, the BLE module must be our DFRobot BLE product, it doesnt support other brand BLE.
This is only a reminder.
Wendy.Hu
I mean if you want to establish connection between gamepad and robot when you are going to use BLE module inserted to the XBee socket, the BLE module must be our DFRobot BLE product, it doesnt support other brand BLE.
This is only a reminder.

2016-09-22 10:20:50 I'm not sure if I understand your last "Just a remind." If I understand this right you're saying you have to use your BLE module module with the gamepad, not an actual XBEE... Am I reading this right?
Murray Chris

2016-09-22 10:20:50 I'm not sure if I understand your last "Just a remind." If I understand this right you're saying you have to use your BLE module module with the gamepad, not an actual XBEE... Am I reading this right?
Murray Chris

2016-09-12 17:36:32 Hi Sir,
Now I fully understand your question. Its a pity that we dont sell the 32U4 board seperately, so we cant provide you just a board. Hope for your understanding.
And It looks like that the TX out pin on the 32U4 is faulty indeed. The only thing we can help you is to give you a replacement under the warranty.
Just a remind, if you inserted the BLE module, which must be our own BLE module, into Xbee socket, or two Xbee sockets will not be able to conmunicate or the problem that you say.
Waiting for your reply.
Wendy.Hu
Now I fully understand your question. Its a pity that we dont sell the 32U4 board seperately, so we cant provide you just a board. Hope for your understanding.
And It looks like that the TX out pin on the 32U4 is faulty indeed. The only thing we can help you is to give you a replacement under the warranty.
Just a remind, if you inserted the BLE module, which must be our own BLE module, into Xbee socket, or two Xbee sockets will not be able to conmunicate or the problem that you say.
Waiting for your reply.

2016-09-12 17:36:32 Hi Sir,
Now I fully understand your question. Its a pity that we dont sell the 32U4 board seperately, so we cant provide you just a board. Hope for your understanding.
And It looks like that the TX out pin on the 32U4 is faulty indeed. The only thing we can help you is to give you a replacement under the warranty.
Just a remind, if you inserted the BLE module, which must be our own BLE module, into Xbee socket, or two Xbee sockets will not be able to conmunicate or the problem that you say.
Waiting for your reply.
Wendy.Hu
Now I fully understand your question. Its a pity that we dont sell the 32U4 board seperately, so we cant provide you just a board. Hope for your understanding.
And It looks like that the TX out pin on the 32U4 is faulty indeed. The only thing we can help you is to give you a replacement under the warranty.
Just a remind, if you inserted the BLE module, which must be our own BLE module, into Xbee socket, or two Xbee sockets will not be able to conmunicate or the problem that you say.
Waiting for your reply.

2016-09-10 10:57:47 OK....somehow you're still not understanding this. I'll try again.
- I have a pair of linked XBEE series 2 chips, one inserted in the gamepad, one connected to the robot.
- The code I had loaded in the gamepad was sending strings through the XBEE link - It was working.
- After about an hour, the strings coming from the gamepad stopped being continuous.
Example: If the string was supposed to report:
Buttons: UP
500,500,500,500,500,500
It would sometimes report:
Buttons: UP
500 500 50
Buttons: UP
500,500,500,500,500,
tons: UP
As if the XBEE was receiving incomplete strings.
Then it stopped working at all. No strings were being sent to the receiving xbee.
- Testing in the opposite direction, I was able to trigger the vibration function of the Gamepad. I then swapped the XBEE chips and was again able to trigger and disable the vibration function. This tells me the XBEE's were functioning properly as they demonstrated that they could both send and receive.
With my oscilloscope on the RX pin of the XBEE socket, the signal is held HIGH.
- I then wrote a simple program to just Change that pin from HIGH to LOW and uploaded it to the gamepad. With the oscilloscope on the same pin, it was again held high. This leaves me to believe that the TX out pin on the 32U4 is faulty, or for some reason it isn't getting clean code from the bootloader.
Is there any way you can sell me just the 32U4 board for the controller?
Thanks.
Murray Chris
- I have a pair of linked XBEE series 2 chips, one inserted in the gamepad, one connected to the robot.
- The code I had loaded in the gamepad was sending strings through the XBEE link - It was working.
- After about an hour, the strings coming from the gamepad stopped being continuous.
Example: If the string was supposed to report:
Buttons: UP
500,500,500,500,500,500
It would sometimes report:
Buttons: UP
500 500 50
Buttons: UP
500,500,500,500,500,
tons: UP
As if the XBEE was receiving incomplete strings.
Then it stopped working at all. No strings were being sent to the receiving xbee.
- Testing in the opposite direction, I was able to trigger the vibration function of the Gamepad. I then swapped the XBEE chips and was again able to trigger and disable the vibration function. This tells me the XBEE's were functioning properly as they demonstrated that they could both send and receive.
With my oscilloscope on the RX pin of the XBEE socket, the signal is held HIGH.
- I then wrote a simple program to just Change that pin from HIGH to LOW and uploaded it to the gamepad. With the oscilloscope on the same pin, it was again held high. This leaves me to believe that the TX out pin on the 32U4 is faulty, or for some reason it isn't getting clean code from the bootloader.
Is there any way you can sell me just the 32U4 board for the controller?
Thanks.

2016-09-10 10:57:47 OK....somehow you're still not understanding this. I'll try again.
- I have a pair of linked XBEE series 2 chips, one inserted in the gamepad, one connected to the robot.
- The code I had loaded in the gamepad was sending strings through the XBEE link - It was working.
- After about an hour, the strings coming from the gamepad stopped being continuous.
Example: If the string was supposed to report:
Buttons: UP
500,500,500,500,500,500
It would sometimes report:
Buttons: UP
500 500 50
Buttons: UP
500,500,500,500,500,
tons: UP
As if the XBEE was receiving incomplete strings.
Then it stopped working at all. No strings were being sent to the receiving xbee.
- Testing in the opposite direction, I was able to trigger the vibration function of the Gamepad. I then swapped the XBEE chips and was again able to trigger and disable the vibration function. This tells me the XBEE's were functioning properly as they demonstrated that they could both send and receive.
With my oscilloscope on the RX pin of the XBEE socket, the signal is held HIGH.
- I then wrote a simple program to just Change that pin from HIGH to LOW and uploaded it to the gamepad. With the oscilloscope on the same pin, it was again held high. This leaves me to believe that the TX out pin on the 32U4 is faulty, or for some reason it isn't getting clean code from the bootloader.
Is there any way you can sell me just the 32U4 board for the controller?
Thanks.
Murray Chris
- I have a pair of linked XBEE series 2 chips, one inserted in the gamepad, one connected to the robot.
- The code I had loaded in the gamepad was sending strings through the XBEE link - It was working.
- After about an hour, the strings coming from the gamepad stopped being continuous.
Example: If the string was supposed to report:
Buttons: UP
500,500,500,500,500,500
It would sometimes report:
Buttons: UP
500 500 50
Buttons: UP
500,500,500,500,500,
tons: UP
As if the XBEE was receiving incomplete strings.
Then it stopped working at all. No strings were being sent to the receiving xbee.
- Testing in the opposite direction, I was able to trigger the vibration function of the Gamepad. I then swapped the XBEE chips and was again able to trigger and disable the vibration function. This tells me the XBEE's were functioning properly as they demonstrated that they could both send and receive.
With my oscilloscope on the RX pin of the XBEE socket, the signal is held HIGH.
- I then wrote a simple program to just Change that pin from HIGH to LOW and uploaded it to the gamepad. With the oscilloscope on the same pin, it was again held high. This leaves me to believe that the TX out pin on the 32U4 is faulty, or for some reason it isn't getting clean code from the bootloader.
Is there any way you can sell me just the 32U4 board for the controller?
Thanks.

2016-09-07 16:26:40 Hi
Sorry for my late reply.
I am not sure what are you going to do with the Xbee? Insert a BLE module? If you want to control the robot, only need to insert a BLE LINK (SKU: TEL0073-forum is updating, cant add link)to Xbee socket, upload code to the robot and the gamepad separately, build connection between the robot and the gamepad, then everthing is ok.
And the TX pin for serial1 and Xbee are all connected to D1 pin, when the BLE module is used, the TX pin will not be able to use.
In your previous reply, the main board you mentioned we dont sell separately. And If you can upload the code to the controller, it proves the bootloader of the main board is good. So I am not sure why did you want to burn bootloader and change 32u4 chip?
Of course, if the gamepad is a defective one indeed and under the warranty, you are entitled to require a repalcement.
Wendy.Hu
Sorry for my late reply.
I am not sure what are you going to do with the Xbee? Insert a BLE module? If you want to control the robot, only need to insert a BLE LINK (SKU: TEL0073-forum is updating, cant add link)to Xbee socket, upload code to the robot and the gamepad separately, build connection between the robot and the gamepad, then everthing is ok.
And the TX pin for serial1 and Xbee are all connected to D1 pin, when the BLE module is used, the TX pin will not be able to use.
In your previous reply, the main board you mentioned we dont sell separately. And If you can upload the code to the controller, it proves the bootloader of the main board is good. So I am not sure why did you want to burn bootloader and change 32u4 chip?
Of course, if the gamepad is a defective one indeed and under the warranty, you are entitled to require a repalcement.

2016-09-07 16:26:40 Hi
Sorry for my late reply.
I am not sure what are you going to do with the Xbee? Insert a BLE module? If you want to control the robot, only need to insert a BLE LINK (SKU: TEL0073-forum is updating, cant add link)to Xbee socket, upload code to the robot and the gamepad separately, build connection between the robot and the gamepad, then everthing is ok.
And the TX pin for serial1 and Xbee are all connected to D1 pin, when the BLE module is used, the TX pin will not be able to use.
In your previous reply, the main board you mentioned we dont sell separately. And If you can upload the code to the controller, it proves the bootloader of the main board is good. So I am not sure why did you want to burn bootloader and change 32u4 chip?
Of course, if the gamepad is a defective one indeed and under the warranty, you are entitled to require a repalcement.
Wendy.Hu
Sorry for my late reply.
I am not sure what are you going to do with the Xbee? Insert a BLE module? If you want to control the robot, only need to insert a BLE LINK (SKU: TEL0073-forum is updating, cant add link)to Xbee socket, upload code to the robot and the gamepad separately, build connection between the robot and the gamepad, then everthing is ok.
And the TX pin for serial1 and Xbee are all connected to D1 pin, when the BLE module is used, the TX pin will not be able to use.
In your previous reply, the main board you mentioned we dont sell separately. And If you can upload the code to the controller, it proves the bootloader of the main board is good. So I am not sure why did you want to burn bootloader and change 32u4 chip?
Of course, if the gamepad is a defective one indeed and under the warranty, you are entitled to require a repalcement.

2016-09-03 11:55:06 Forgive me, I provided the wrong SKU. The Arduino Shield you mention is actually what I'm using to receive the code.
The SKU for the controller is DFR0182.
http://www.dfrobot.com/wiki/index.php/W ... KU:DFR0182)
The tx output to the XBEE is stuck. This was part of a gift to my son, and now it's not working.
As a father and an experienced electronics tech, I see three things left to do:
1. Reflash the controller in hopes the bootloader is corrupt and it fixes the problem - Not likely but easiest thing to try.
2. Replace the main board with a spare. - I haven't received any response from your company regarding this.
3. Replace the 32M4 Chip - Involves a microscope and steady hands but I've done it.
Ultimately I'm still waiting for a honest response from DF. If you can't provide a technical support or a replacement board, just tell me and I'll buy from a different vendor.
Thank you for your time.
Murray Chris
The SKU for the controller is DFR0182.
http://www.dfrobot.com/wiki/index.php/W ... KU:DFR0182)
The tx output to the XBEE is stuck. This was part of a gift to my son, and now it's not working.
As a father and an experienced electronics tech, I see three things left to do:
1. Reflash the controller in hopes the bootloader is corrupt and it fixes the problem - Not likely but easiest thing to try.
2. Replace the main board with a spare. - I haven't received any response from your company regarding this.
3. Replace the 32M4 Chip - Involves a microscope and steady hands but I've done it.
Ultimately I'm still waiting for a honest response from DF. If you can't provide a technical support or a replacement board, just tell me and I'll buy from a different vendor.
Thank you for your time.

2016-09-03 11:55:06 Forgive me, I provided the wrong SKU. The Arduino Shield you mention is actually what I'm using to receive the code.
The SKU for the controller is DFR0182.
http://www.dfrobot.com/wiki/index.php/W ... KU:DFR0182)
The tx output to the XBEE is stuck. This was part of a gift to my son, and now it's not working.
As a father and an experienced electronics tech, I see three things left to do:
1. Reflash the controller in hopes the bootloader is corrupt and it fixes the problem - Not likely but easiest thing to try.
2. Replace the main board with a spare. - I haven't received any response from your company regarding this.
3. Replace the 32M4 Chip - Involves a microscope and steady hands but I've done it.
Ultimately I'm still waiting for a honest response from DF. If you can't provide a technical support or a replacement board, just tell me and I'll buy from a different vendor.
Thank you for your time.
Murray Chris
The SKU for the controller is DFR0182.
http://www.dfrobot.com/wiki/index.php/W ... KU:DFR0182)
The tx output to the XBEE is stuck. This was part of a gift to my son, and now it's not working.
As a father and an experienced electronics tech, I see three things left to do:
1. Reflash the controller in hopes the bootloader is corrupt and it fixes the problem - Not likely but easiest thing to try.
2. Replace the main board with a spare. - I haven't received any response from your company regarding this.
3. Replace the 32M4 Chip - Involves a microscope and steady hands but I've done it.
Ultimately I'm still waiting for a honest response from DF. If you can't provide a technical support or a replacement board, just tell me and I'll buy from a different vendor.
Thank you for your time.

2016-09-02 18:03:24 Hi,
It seems that you are using Leonardo to communicate with XBEE. So the switch should be at the 'A' side.Would you mind rechecking the switch in the middle of the board?
Angelo.Qiao
It seems that you are using Leonardo to communicate with XBEE. So the switch should be at the 'A' side.Would you mind rechecking the switch in the middle of the board?

2016-09-02 18:03:24 Hi,
It seems that you are using Leonardo to communicate with XBEE. So the switch should be at the 'A' side.Would you mind rechecking the switch in the middle of the board?
Angelo.Qiao
It seems that you are using Leonardo to communicate with XBEE. So the switch should be at the 'A' side.Would you mind rechecking the switch in the middle of the board?

2016-08-30 23:33:28 DFR0327 was the model number.
As an update: The controller worked fine when I powered it back up last night - for one power cycle. As soon as I power cycled the unit, it ceased to function after. Could it be a faulty bootloader?
Murray Chris
As an update: The controller worked fine when I powered it back up last night - for one power cycle. As soon as I power cycled the unit, it ceased to function after. Could it be a faulty bootloader?

2016-08-30 23:33:28 DFR0327 was the model number.
As an update: The controller worked fine when I powered it back up last night - for one power cycle. As soon as I power cycled the unit, it ceased to function after. Could it be a faulty bootloader?
Murray Chris
As an update: The controller worked fine when I powered it back up last night - for one power cycle. As soon as I power cycled the unit, it ceased to function after. Could it be a faulty bootloader?

2016-08-29 11:02:41 I ordered this controller for a robot project in the spring, just getting around to using it.
Got the code working on the XBEE's, everything was great....
Then TX out for Serial1 (PIN 21 uC, Pin 2 XBEE) started being eratic. Strings would not complete on the serial line. AN hour later it stopped working. It's stuck high. I've verified this right at the XBEE header. I'm also able to make the vibrate motors work via serial, in both directions (Swapping the XBEE's from controller to robot) so I'm confident that the problem isn't with the xbees.
I've tried using it as just a on/off pin and no luck. I've tried running off the usb programmer, as well as a stable 5VDC source, no change.
Unless you guys have some other ideas on how to troubleshoot, I'll likely need to order a new main board for the controller, something I see you don't sell separately....
Some help would be appreciated.
Thanks!
Murray Chris
Got the code working on the XBEE's, everything was great....
Then TX out for Serial1 (PIN 21 uC, Pin 2 XBEE) started being eratic. Strings would not complete on the serial line. AN hour later it stopped working. It's stuck high. I've verified this right at the XBEE header. I'm also able to make the vibrate motors work via serial, in both directions (Swapping the XBEE's from controller to robot) so I'm confident that the problem isn't with the xbees.
I've tried using it as just a on/off pin and no luck. I've tried running off the usb programmer, as well as a stable 5VDC source, no change.
Unless you guys have some other ideas on how to troubleshoot, I'll likely need to order a new main board for the controller, something I see you don't sell separately....
Some help would be appreciated.
Thanks!
