Hi, All:
Six weeks ago I purchased a Toque Board Street from DIYElectricSkateboards.com. When the board arrived: I switched on the power; the backlit LCD battery level display flashed for a split second, and then; the backlit LCD display went dark/blank. So I immediately contacted Dexter at DIYElectricSkateboards.com to determine what was wrong and how to fix it.
While I was waiting to hear back from Dexter: I turned on the Flipsky VX1 remote throttle and applied the scroll wheel. The motors groaned and the large, 110 mm wheels turned reluctantly. I did this a few times. And then the skateboard stopped responding entirely. (i.e., It was completely dead.)
When I heard back from Dexter: He informed me that DIYElectricSkateboards.com does not provide telephone support and insisted that I'd need to troubleshoot the problem over e-mail. So I decided to investigate a bit further by removing the battery tray and looking around to see if it was something obvious:
There wasn't anything obvious. But the skateboard did begin responding to the Flipsky VX1 remote throttle normally. So Dexter & I agreed that the backlit LCD battery level display simply needed to be replaced. So he sent a replacement unit. And I installed it.
But in the mean time: I realized that I needed a Bluetooth dongle for viewing telemetry data on my Android phone - So I purchased a METR.at Bluetooth dongle from DIYElectricSkateboards.com. Once it arrived: I was able to plug it in to the unused COMM port of VESC #0 and pair it with my Android phone. But the phone was unable to communicate with the VESC because the COMM port of VESC #0 had not been configured for UART communication.
I don't have a PC to devote to the task of configuring the VESC's. So I removed the Flipsky VX1 receiver from the COMM port of VESC #1 and inserted the METR.at Bluetooth dongle. This allowed me to communicate with the Torque6 VESC; to view the telemetry data, and; to change configuration settings of the VESC. But I was unable to configure the COMM port of VESC #0 to communicate with the Flipsky VX1 receiver. And now, when I swap the the Flipsky VX1 receiver with the METR.at Bluetooth dongle: The Bluetooth dongle continues to operate as expected. But the remote throttle still does not seem to be communicating the either of the VESC's.
I just want a working remote throttle and Bluetooth telemetry. Can someone please tell me what I'm doing wrong?
TIA,
Eric P.
Reno, Nevada
I thought that it might be useful to provide a few composite screenshots to illustrate the settings as they were when I began and the settings that I've changed:
APP CFG::VESC Remote::General, before:
APP CFG::VESC Remote::General, after:
APP CFG::General, before:
APP CFG::General, after:
Thoughts? Suggestions? Maybe something about how to place these images side-by-side so that they're easier to grok?
TIA!
Eric P.
Reno, Nevada
I've attempted to use the Setup Input Configuration Wizard: But it's unable to detect the throttle movement (i.e., Step #3)...
Ideas? Suggestions?
TIA!
Eric P.
Reno, Nevada
First of all this is all third party stuff and not VESC HW. So I don't know exactly how the remote works... If the remote is connected via UART (not connected via PPM port), you don't run the input wizard. In the case of UART the official VESC remote just needs pairing via VESC Remote Quick Pair. Not sure what Flipsky did there... You should get proper support via the vendor who sold you the ESCs and remote. The vendors makes profit on selling you the stuff and he should support you in consequence. If he didn't price in support, then he made something wrong.