Can’t connect from Android to Focbox Unity.
Android app tried from Google Play and APK from GITHUB (1.2.1) and also from Enertion site.
Unity firmware: 23.44
Focbox Tool on Windows works.
Any idea ?
I heard that 1.3 fixes this issue, but can’t find the APK, any link ?
My fried Unity Bluetooth module [spoiler]v1.1[/spoiler] kindly got replaced by Enertion. Now it manages to connect to the Unity via RX/TX again. Thank you!
The connection dropout was not fixed though by a new BLE module, which apparently is rumoured to be caused by the high polling rate of the Unity. Dropouts happen even with the official Unity Nexus app beta. So in other words, the bluetooth is still completely unusable on my end.
So I guess the only option left for me is to compile my own Unity firmware with lower Uart baud rate and flash the NRF52 module with Vedders NRF firmware and see what happens.
1- Going thru the guided conf. After clicking on the “Apply Updated Config”, can not continue to remote setup because “Ok” tap is gray out. Only hitting ESC key allows me to move on with remote setup
2- Remote calibration does not response to either throttle forward or backward. Nano remote was confirmed to be connected with solid red light on Rx.
3- “Hud Config” in setting: “Test ERPM -> RPM” did not return any values other than “0” after manually turning one of the wheel 10x as instructed.
Since I have another Unity, I’ve tested it.
Regardless the firmware, I am able to connect via Bluetooth perfectly fine, no issues.
Appears to be that the Bluetooth module of the first Unity is fucked Anyone had not so good experience with the BT module on Unity as well ? What can be done ? Is the first Unity completely useless now without BT ? connecting via cable seems to be working ok.
I currently have a support ticket waiting for advice on error:could not read firmware version make sure selected port belongs to focbox when connecting via android app. It originally worked fine and then just started getting this message. I too can connect fine by USB.
I think the BT module on the board is dead. It was dead from the start and never worked before. Enertion are ignoring completely on support tickets (no single response) in days/weeks. Don’t wanna slander, but sadly this is the case.
Issues resolved: when updating configs, Unity does not like it with the metr pro board on its comm platform. Switch back to their original comm board before updating configs. Re-install metr pro only after all configs are performed.
Hi, my unity keeps disconnecting and stops responding to commands. I’m trying to flash the firmware again in an attempt to resolve it, but this keeps timing out. When I start it up the error led flashes once. What could cause this?
My unity resets itself back to factory settings now and again. Batteries left plugged in. Is this common fault? Means I have to re run motor Detection and set battery type up.
There may be a new update but was current about a month ago. Will have to check. Weird that it holds settings when I disconnect batteries and charge them but a few hours between rides and it resets sometimes. Unless there’s something I’ve missed about holding power button for too long resets it ? That’s all I can think of