Kinda want to change the title to that nowā¦
Excellent guide, I applaud you sir.
Bookmarked for when I DOH! Thanks and nice work, great content.
Thank you for documenting this!
Thanks a lot!!!
Could you please clarify the jumper connections between the connector on unity and the one on the St link. I am not sure I understand which is which in your small connection graphics
I intentionally left that out, as it could differ per version you have. This is mine, and the pin assignment is written on the stick.
I am soooo Happy that I found this Procedure You posted. I was almost resolved to give up on my project and wait for another Focbox Unity.
I have tried to recover messed up ESCās before with the STM Link V2 previously, but was unsuccessful.
Your Procedure was so Professional in appearance, and it showed the exact same ESC that I was trying to recover, the Focbox Unity, so it gave me the confidence to keep trying. It took at least 20 or 30 minutes trying to connect from the STM Link Utility program, but eventually it actually connected and now my Focbox is actually working!!! WOW!!! WOO HOO!!! YAAAAY!!!
I kept trying to duplicate the image from the STM Link Utility Program that you have in your Tutorial. Every so often, I would pull the STM Link module out of my Computers USB port, close the Program, then plug it back in and restart the program.
Eventually, I went to Target>Settings>Connection Settings>clicked on SWD, Clicked on OK, and waited for like 30 seconds for the window to become active again.
Then I tried to Connect and it actually worked!!
Thanks a lot for sharing the fruit of your Genius, You Rule Man!
Hope you stick around, Airwolf!
Iām glad my guide helped you
Hey, Thanks a lot Guys!
I finally went on a Test Ride on my new Board this evening, and it was pretty solid except for 1 issue I still need to resolveā¦
My new Board has a Halo Carbon Fiber Deck.
It has 2x Raptor 2.1 Trucks with 97mm Outwheels. I have 2 Focbox Unities controlled by split ppm powering the 4 Hub motors.
I bent two pieces of Steel Tube, (Square X-Section, 1/2" on a side)in to a sub-frame. The Steel Tube sub-frame parts, (which have lots of āLightening holesā drilled through them) run along the bottom of the Deck and bolts to the underside of the front and rear trucks using the same bolts as those that hold the trucks to the Deck.
I have a homemade 12S6P Battery Pack of Sony VTC5A batteries and donāt use a BMS.
I just have 1 issue left at this point. 1 of the 2 Focbox Unities just turns off for no apparent reason after a minute or two.
Tomorrow I am going to Reflash the Unity.bin file now that I know how thanks to DSluijkās excellent procedure. Then Iām going to try reuploading FW 23.44 again and if that doesnāt work, maybe 23.43 or 23.42.
The hub motors run fine when theyāre running, but after a minute or two, the Unity for the front wheels just turns off. It can be turned on again just be pressing the button. Iām not sure what to think of it, but any suggestions would be welcome, and if I figure it out, Iāll post some info about it.
Iām going to look in to the Error message that comes up which is: āSerial Port Error: The I/O operation has been aborted because of either a thread exit or an application request.ā
Have a Great day, I will return sometime soon : )
I tried again and again to connect to the device, no success
the stm32 module is connected to the PC, the unity leds are on but the connection to unity doesnt work
i try again ā¦
You might be able to try this. I didnāt have to do that, but you might.
Have you tried to put the unityās in a master slave setup instead of splitting the PPM signals? I donāt think this is a problem with the bootloader, but you might try to flash the firmware again.
Yes, I tried that too. A message indicating that device was not connected and suggesting to do it popped up.
May be my unity is fully bricked?
I ll bring my unity to a friend who can perform tests
Interestinglyā¦ my unity bricked after updating to 23.45. It worked for one hour, time to do motor set up and bench testing. Everything seemed OK when I switched off. It did not switched on again a few hours later.
Itās a 4wd setting, only the master unity bricked. The slave is still functional as seen by connecting to it by BT.
Master has a metr pro module attached. The metr pro module was also updated.
I had zero problem in 6 months using the previous fw version of metr and unity.
Conclusion : I want to revert to previous fw !!
Do you know where I can find an archive of previous fw versions of unity and metr pro? Is it possible to flash previous versions within unity app (windows or Android)
Is there anyway to do this to the fsesc 6.6? I canāt find instructions anywhere
@JoelM i sent a link to how I fixed my flipsky on your thread
Letās keep this one for unity users
Okay, my apologies