Forum >Romeo BLE V1.0 None Responsive
Romeo BLE V1.0 None Responsive
Millar Mark 2016-05-29 09:36:32 13996 Views5 Replies I have a devastator tank chassis and a Romeo BLE controller. When using the PWM control mode sample code for testing I am getting problems with the robot becoming unresponsive and the motor controller continuing with the last command. I assumed this was power issue and have tried powering the setup with both lipo batteries and a 5A beach PSU. I also tried switching the motor power switch and powering the MCU separately with a USB cable, all with the same results of the controller becoming unresponsive.
I updated the bootloader to version 2 and updated the firmware to version 1.96 still with no luck. The MCU processes a few commands and then stalls. I have uploaded the sketch with both 1.0.5 and 1.6.7 IDE versions from windows 10. I am using a serial Buad Rate of 115200.
I updated the bootloader to version 2 and updated the firmware to version 1.96 still with no luck. The MCU processes a few commands and then stalls. I have uploaded the sketch with both 1.0.5 and 1.6.7 IDE versions from windows 10. I am using a serial Buad Rate of 115200.
2016-06-04 00:55:49 Well, we need to look into this issue. To make your project go on, we suggest you could use a Romeo(leonardo) with a BLE link, since the Romeo BLE is UNO which shares the same COM port with CC2540. That would be cause some trouble.
For return and refund, you could visit this page. https://www.dfrobot.com/index.php?route= ... urn/insert Leff
For return and refund, you could visit this page. https://www.dfrobot.com/index.php?route= ... urn/insert
Leff 2016-06-04 00:14:58 I tried an i2c link to the romeo, with the same thing occurring. When the motors go full power the connection randomly stops (requiring a hard restart to get control back). Again the motors latch to their last input command i.e. the motors continue to run. Could there be some sort of grounding issue between the MCU and the motor controller. I even disassembled the devastator tank chassis and moved the motors away from the MCU, just encase.
I have never had this issue with the other romeo versions that I have (that's why I thought it could be the cc2540 chip). I only got this romeo BLE version to play with the BLE link. If I cant get this sorted I will swap it out for a adafruit feather. Millar Mark
I have never had this issue with the other romeo versions that I have (that's why I thought it could be the cc2540 chip). I only got this romeo BLE version to play with the BLE link. If I cant get this sorted I will swap it out for a adafruit feather.
Millar Mark 2016-06-02 01:24:14
The problem is when using the motors, Originally I thought there was a power drain causing the MCU to reset that's why I tried powering it separately. Could the motors be interfering with the CC2540 chip or the BLE receiver? I know that the version 2 of the bootloader was meant to help with, that is why I updated before my original post. Millar Mark
- I have updated the romeo with the version 2 bootloader and AT+VERSION= 1.96
- I am already using a Baud rate of 115200
- Motors are connected correctly
- Tested the uno via serial and BLE no problems at all
The problem is when using the motors, Originally I thought there was a power drain causing the MCU to reset that's why I tried powering it separately. Could the motors be interfering with the CC2540 chip or the BLE receiver? I know that the version 2 of the bootloader was meant to help with, that is why I updated before my original post.
Millar Mark 2016-06-01 04:03:11 The blink example is working, and the motors are working, the wiring is as shown in your example.
When watching the rx led on the board, it still flashes when a command is sent over serial but the board stops not responding.
It will process a few commands and then just become unresponsive. I testing with your sample code "PWM Control Mode", and get the same problem when the motor power switch turned to off with the MCU powered by USB. Millar Mark
When watching the rx led on the board, it still flashes when a command is sent over serial but the board stops not responding.
It will process a few commands and then just become unresponsive. I testing with your sample code "PWM Control Mode", and get the same problem when the motor power switch turned to off with the MCU powered by USB.
Millar Mark 2016-05-31 01:06:52 Hi
Were you according to the following link to do a connection?https://www.dfrobot.com/wiki/index.php?title=Devastator_Tank_Mobile_Platform_SKU:ROB0112
I guess that maybe your connection was wrong, so do you have a picture about your connection? But now i will give you some advices to do a test firstly.
You can test the motor and controller separately , make sure whether be burned out.
First, dont connect the motor, and upload a Blink to the board to ensure that the board is good; and then you can let the motor directly connect power to ensure that the motor is good. Wendy.Hu
Were you according to the following link to do a connection?https://www.dfrobot.com/wiki/index.php?title=Devastator_Tank_Mobile_Platform_SKU:ROB0112
I guess that maybe your connection was wrong, so do you have a picture about your connection? But now i will give you some advices to do a test firstly.
You can test the motor and controller separately , make sure whether be burned out.
First, dont connect the motor, and upload a Blink to the board to ensure that the board is good; and then you can let the motor directly connect power to ensure that the motor is good.
Wendy.Hu 