Well, for metr module, I powered it up via connector (5V from Arduino). I used a little software instead of terminal. Check my link above.
Honestly your wiring looks a little sketchy to me. Did you try sending AT commands? Did that work? I’d clean up the wiring and make sure everything is soldered properly. I also used a different ccloader.exe called CCLoader_x86_64.exe. Did you try it several times with for example an Arduino reset it between? Maybe the old “turn it off and on again” works here as well.
@moderators : I feel like we went quite a bit off-topic here. Sorry @Ackmaniac. You guys should probably move this to its own thread.
OK I will. No off topic anymore.
Feel free to discuss this. Great when you can find a easy and reliable way to do it so that others can use the app again with Android 8.0 Didnt find the time to give it a try myself yet.
1 Like
Thx man! 10ch
Tested it myself and it works. You don’t need to solder the wires to the pins. Just take a needle and make a little hole at the pins. Then stick the wire in and hold it in place with your hand or with tape. Of course I fucked it up the first time by mixing up 2 wires (like a curse, happens every time). And I had the problem that I couldn’t use my original ports 26 and 37. Seems only low numbers are accepted so I had to change it to the number 2 in windows device manager.
2 Likes
Did you upload the sketch to the arduino? Just make sure it had no faults during writing
Yes everything works until I try to upload the firmware to the module. I will give it another try for sure.
Just check again your connections. Should look like this 
1 Like
Yes I know. I watched the video and read the tutorial 20 times. I think I maybe made weaker connection by soldering not properly so I will give it another try.
Just released a new version 1.101. Trying to automatically reconnect in case you lost connection in a couple of seconds.
3 Likes
Sweet. I was wondering, maybe it’s already like that but when you want to detect fault in the app and the Bluetooth it’s connected to the master VESC, does it actually check for faults also for the slave VESC or is it only possible for the master side? Same question in case you connect to vesc tool via TCP and move to the slave VESC via CAN. Thx
When you are connected to the master(CAN or directly doesn’t matter) then the app will check at start which slaves are connected and check for faults of all members. But after that first initial check it only recognizes the faults of the one you are currently watching.
1 Like
Ok perfectly good to know. Because I read the sometimes to detect DRV faults you need to spin the motor so I’m this case only the one directly connected can be detected. I was wondering if to allow the firmware upload through the app via TCP you would only need a faster baud than 9600. I also understand that you would need to modify each module via AT commands…which makes everything less friendly use.
Firmware upload works already. I was surprised as well. But the firmware uploads will only work with my firmware because there i use a default baud rate of 9600. The original firmware uses 115200.
Man you should highlighted it! Or an I the only one that missed it? Fantastic. I am using your firmware BTW. I guess it would just be just slightly slower. Next step for you would be make a VESC tool app version with your firmware 
Not that I need it, it’s just nice…
Hi, I just tried the new version. It worked for me a few times, but now it’s back to the bad behavior…however, I noticed one odd thing:
If I deactivate the location services on my phone, or just refuse to give the app the permissions to access the GPS, the bluetooth device list remains empty. If I had my board registered, it appears greyed out. Also, even with all the services activated and giving it the permissions, it still shows the “functionality reduced” prompt. Could it be a permissions issue?
Bluetooth low energy needs GPS permissions. Even if it doesn’t activate GPS. Don’t ask me why.
Well, didn’t know that, sorry. I’ll report if I find anything new, thanks anyway!
Update: I received the update 1.103 and now when the app is connected to the vesc a blinking message says “No storage folder found” is appering. I see in the logbook that the app created the new file although the messagge is always there. PLus the TCP connection is more instable, I could connect via CAN to the slave and also the motor and app writing/reading worked only sometimes. WIth the 1.101 I everything worked proberly. I just wanted to report to you @Ackmaniac. Thx!