Hello, Trying to update my interface's firmware today, I got the message: Update failed Not enough space Can you give me a heads up? Thanks
As a followup, trying to Flash through the Control software on my PC, using your supplied usb-c cable to connect the Interface to the computer and following the instructions from the wizard, it doesn't recognize the usb connection saying that it's "Waiting for USB". Can you help because I think I'm on the right track but... Don't know...
The usb cables supplied with the box are only power cables. You need a data cable. INTERFACE CNC Touch Controller
Not sure about this. The cable I used to access my phone to transfer files, to and from my computer, does the trick with it so, logically, that same cable, that I consider as being more than a power cable, still does not allow transfer or communication between the Interface and the computer. Any thoughts?
There's enough of us out here that received power only cables that its valid to mention it. Ok so now that we know you have a data cable, have you installed the FTDI drivers on whatever computer you are using?
Having to install an FTDI Driver (https://www.ftdichip.com/Drivers/CDM/CDM21228_Setup.zip), it did the trick. I went to the GitHub repository and downloaded the Firmware.bin file needed (https://github.com/OpenBuilds/firmware/raw/main/interface/firmware.bin). Going through the Control Wizard procedure to Flash the Firmware, it did recognize a COM4 port. I then proceeded to choosing the Firmware.bin file I had downloaded and then, clicked the flash button. The Flash procedure went ahead but at the end of the Flashing process, it gives a: [ Firmware Upgrade ] A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header [ Firmware Upgrade ] [exit] Hooking the Interface back to the CNC, it seems that the update did not take. Not sure how to go ahead with this but, I guess I'm sticking to Firmware v 1.41 until an other solution comes up. Thanks
It sounds like you didnt hold the mode button and press reset after you clicked flash. docs:interface:firmware-update-control [OpenBuilds Documentation]
Thank you for hanging in there with helping me. I will try this tomorrow and I'll check back in. Thanks for taking the time to help.
No problem. I had similar issues so I understand. While you're hanging out tonight, read the docs. Its a new product so Peter has been updating them regularly with everything we are finding out.
After a careful read on my part and a sincere raising of my hate to Peter, the section explaining the process to fix my issue (Firmware Update Method 3: Update via OpenBuilds CONTROL) is the important one. Being more of a visual learner and after being spoiled by your past approaches using videos to explain your instructions, I feel that this section does need a video showing a split screen demonstration showing on one side a view of the Mode and Reset buttons being press and on the other, to show the process on the computer, using the Control Wizard. What's important here is the sequence of when you press the Mode button, when you press both buttons simultaneously and when you can let go of the Mode and the Reset buttons. This sequence may confuse others and this video could be the key to make this process clear.
Hello again, this is the next day. I initially tried to update the Interface module using the pushing of the Mode button, pressing of the Flash button on the computer screen, then immediately pressing the Reset button still pressing Mode and I got the screen that you see attached to this message. As I unplugged and replugged the Interface, to my surprise, it gave me a dark / blank screen. Hoping the Interface didn't become a Brick, I decided to follow Peter's advice to do the update using the Jumper method. Sorry to say, after moving the jumper and going through the same Flash procedure, I got no change with the same messages that I'm showing you in the screen shot. Placing back the jumper in its Run position and replugging the Interface to my computer, the monitor is still blank. My conclusion is either the Firmware.bin file that I sent was not correctly downloaded to my computer and what went to the Interface was junk or something else is wrong. Still armed with tones of patience, can you still guide me here? Thank you (BTW, the USB-C cable that came with the Interface is indeed not the right one because my own one did the trick and yours had the computer not detecting any COM ports)
Well Well Peter, I downloaded your link by right clicking it and choosing save link as... Then, I changed the name of the file because the download name was Firmware (1).bin and having to respect the 8.1 naming format, changed it to Firmwar1.bin . And low and behold, the champagne is out and the update worked. Now stepping back, here is what I think happened... My first download of Firmware.bin was bad (and I know why and I'd jump out a windows before I tell you why). The second download of the file I was trying to use was in the non 8.1 file format which I think was the issue. So now, I can leave you alone and let you go back to work thanking you for your patience and help... Stay safe....
So, just did a test flash here: All the detail: 1) Install CONTROL 1.0.275 (Use the Only for Me option during the install) - as per bug OpenBuilds/OpenBuilds-CONTROL 2) Click Wizards and Tool, Firmware Flashing Tool 3) Connect Interface via USB cable 4) Select "Latest v1.43" from the list 5) Select the correct port from the list 6) Put two fingers of your left hand on the buttons on the side of the Interface, index on MODE, middle finger on RESET 7) Hold down MODE 8) On screen, click FLASH 9) Immediately, click Reset 10) Flashing starts, as soon as you see a couple percent done, release MODE 11) Wait for it to Finish 12) If it doesn't reboot into firmware, click Reset again
Bug Find alternate Write location for firmware.bin · Issue #179 · OpenBuilds/OpenBuilds-CONTROL makes it a little unfriendlier for you, so just uninstall, reinstall as "only for me" and it will work without having to manually download images
- I don't think that "(Use the Only for Me option during the install)" is necessary, I used the other and it went fine. - I didn't touch the "4) Select "Latest v1.43" from the list" - 9) Immediately, click Reset.... Should be modified to... 9) Immediately, Hold down Reset.... To respect the phrasing you used in Step 7 Good job Peter
No it wasn't fine, you had to download the Bin, instead of having the nice built in "Use latest" option available where it downloads it automatically Which is so much nicer to have No, you HOLD MODE, so when you CLICK Reset (short press) and it comes out of Reset, the ESP sees MODE is being held down, knows to enter Bootloader. If you HOLD RESET nothing will work because it is then in the "reset" state, not a running state.
