@Deodand it was asked earlier in the this by @lemntl but I can’t see where it has been answered
Does the Unity work with the AS5047 encoders ?
From what I can tell on V4 hardware you had to remove some input filters or change some components where V6 hardware the filtering was possibly done software side so worked without mod.
Being that the Unity is based on V4 hardware I’m guessing it won’t work out of the box or have you been able to do some kind of magic trickery to have it work ?
Any word on iOS/iPhone app for the go box unity? I know “it’s coming” but where can I watch and wait to get it ASAP? Having to unscrew my enclosure just to tweak things is $&@#. Is there a place I can watch for updates?
Hey all,
Im having an issue. On of my. Motors seems to be kind of cogging but its dofferent than “normal” cogging. Also its not all the time. It happened all of a sudden.
I screenshotted my config. I will upload a video as well
Hi. I am facing an unusual situation that whenever I try to configure my Unity through the Unity Tool. Every time i am done updating the config and I turn the board off, when I turn it on it does not function. It seems that the unity forgets all motor config and starts behaving as if the motors have not been configures at all.
I am only using the tool because the Focbox UI does not have an option of controlling input dead band. That is set to 15% by default in the UI hence the need to use the tool. I have to go back to the UI to configure my motors. Has anyone faced a similar issue?
Another issue I’m having is that whenever I’m drawing telemetry from the UART from the unity, I am unable to update config. As soon as I turn off my feather remote , I am able to write the config.
Have you reflashed firmware? It sounds like somehow your eeprom (non-volatile memory) isnt getting written correctly during the config write. What pwm freq are you running?