@carl.1 i send you an email 8 days ago, could you please answer me #21171 ?
1 Like
Do you might know what’s going on here @carl.1 @CarlCollins @adrianenertion @barajabali or @Deodand ?
Any help would be greatly appreciated. 3 issues:
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.
I am also having trouble writing updated configs as per your first issue.
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.
2 Likes
yeah I was using the Metr Pro bluetooth module too.
My Unity switch also stop working, could no longer turn off no matter how long I press in. Did you get it resolved or found a replacement?
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.
Happened once to me randomly, hasn’t happened since. Updated your firmware?
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
2 Likes
Thanks for posting this finding.
Thats good to know
My switch died on me as well. I replaced it with Ulincos Momentary Pushbutton Switch U16B1 1NO Silver Stainless Steel Shell with Blue LED Ring Suitable for 16mm 5/8" Mounting Hole (Blue) https://www.amazon.com/dp/B01G00GHQY/ref=cm_sw_r_cp_apa_i_x9SsDb46X0FHW
2 Likes
FOCBOX Unity app on Android stopped working out of the blue. Just instantly crashes whenever I press connect. Any ideas? Already re-installed completely.
does anyone else have the problem that they can’t connect to the android app?
I get a BLE Error: ConnectionError
Hey @Deodand
I have some problems with new motors on the Unity and just want to be sure that the noise is not an electrical noise which is produced by the Unity trough the motor.
See/Listen here:
It is definitely not in the drivetrain itself. I get this when the motors and the Unity is warm (50 degrees or more) and after a few seconds (like in the video) on full throttle. I changed the motors (have 4 of them) but all doing this. I also think (not sure) it might be always just the right side of the Unity.
Is this possibly some noise due to cut down (current or temperature)? Or can the definitely say this can not be caused by the Unity?
Did anyone else experience some noise?