Okay I managed to pair with the board BUT only with my old Samsung S4 running Android 7.1.2 and using Jacob’s VESC app ‘VESC Connect’. Scanning for the module inside the app instead of the phones bluetooth settings
Not desirable but it works. The battery on my S4 is terrible
@fottaz Looking forward to your findings!
Flashing ackmaniac’s firmware requires a bootloader and thus some wire thingy to accomplish, right?
My phone is discoverable, but that shouldn’t make a difference since the search happens from my phone not the other way around
try connecting it to the ackmaniac bldc tool, if bootloader is installed (90% of maytech have it installed), the software will tell you if it’s possible and will suggest to upgrade it.
So far so good, but the firmware is a little bit tricky. I went to the firmware tab and browsed to my downloads folder where the ‘ackmaniac-firmware.zip’ and unpacked folder are located. What file do I have to select?
I can not select the complete zipfile
I assume one of the following? VESC is version 4.12, installed firmware is 2.18
I’ve read that Roman programmed his modules or something so they work with his Metr app. But the things that I read about it on his forum were from some time ago. And there were all sorts of discussions about licensing so I thought (since fottaz’s website says it works with his modules too) he had made his app public and is earning some money through donations by now…
If you bought a module that wasn’t from Roman. It won’t work… No amount of looking into it is gonna change that. As you can’t add the mac address of your module into the software( metre.at)
I understand. But that is if your story about MAC addresses is correct.
I will not be making any decisions on what is correct for now and wait till fottaz has an explanation.
You can wait for fotaz all you want. He didn’t develop metre.at, Roman did.
I own two metre modules, and have tried doing simple renames of extra hm10 i haveBluetooth devices with “AT” serial commands to set the Bluetooth device name to match his “metr-XXX” naming. It won’t do anything even with the same name as another module. The only other option on these HM10s is to pull the Mac address off and use that to lock down connectivity within the application if you dont want people using an app without your module.
If you dont believe me, hook up your hm10 to a FTDI adapter, open the serial console in arduino IDE @ the baud rate of the module, run the AT commands to set the name, AT to set baurdrate (115200) and AT save.
Try all you want, you won’t get anywhere unless you can rewrite the Mac addresses
As well if you look at metre.at on google play you can see the version revision history. Roman publishes a new version almost daily. Anytime a new module is sold a new version is released to accommodate additional mac addresses. You really think he updates the software daily with bug fixes? Doubtful.
You won’t be connecting to the Metr app unless you purchased a module from the creator. He states this very clearly in his thread. Use @Ackmaniac firmware/app if you’d like to use your bluetooth module to change/monitor your vesc’s.
Guys take it easy. I fully understand what you are saying. I study computer science including hardware engineering so I know a few things about AVR/Atmegas and Arduino to say the least
I talked to fottaz and want to give him the opportunity to sort things out.
That’s all
I have read the full disclosure a few days ago but already had bought the module from fottaz while he stated it should work with Metr. I didn’t know at that time it was Mac address specific
Hm10s by default are non discoverable/pairing BLE UART over air.
They aren’t designed to be “paired” with. And shouldn’t show up in androids Bluetooth pairings. Older phones with pre bluetooth v4+ the BLE devices would show up. But BLE devices are not designed to show up in the Bluetooth pairings of android.
Alright so it seems. Thanks for confirming that
I will look into Android 8 vs BLE and report back here. Or do you have any insights into this issue, @Deckoz?
Indeed this is normal the HM10 low power bluetooth device. Any app designed for low powered bluetooth devices will see it and connect for you.
My Sony Z5 sees is but wouldnt pair, which left me scratching my head for a while. Opened up ACKMANIAC-ESC Monitor and bam, it found and connected to it instantly.
I have made some changes to the topic to be more aimed at the problem (Android 8 vs HM-10) since it has become clear that BLE devices aren’t supposed to show up in your phones Bluetooth settings.
It seems that Google is working on a fix for bluetooth, but mostly focused on BT headphones issues.
Same for Wifi, I have so many trouble with it, consuming a lot more of mobile data (issue also known by Google).
Do the 8.1 update correct some of these issues ?
My phone sticks to 8.0 and says that I’m up to date…
