Howdy all, with the unfortunate (I'm truly sad) shutdown of Openbuilds, I decided I need to get everything up to date with my backups in case something goes wrong. I have a backup Interface I bought in '21, with a firmware version 1.41 (It's an OG's OG) I just tried updating it to the newest firmware and it popped an error "Flash is too small" and then reboots. I am using the usb to load the firmware flash onto the interface - is there a previous version I need to load up first before the most recent? Thanks for any info!
Just went through previous posts in a Google search, I'm seeing that 1.41 can only be updated through control, so I'm going to throw it on my laptop and hopefully I can get something done that way. Will update in the future
Ok I've tried all my computers using the driver's from the interface x4 documentation on a fresh install of CONTROL and when hooked up The interface is shown on a com port but it's refusing to hook up. No matter what I've tried it on, it hasn't been able to connect. If I'm using this older interface on an older blackbox at v1.41 will it matter? Or should I strive to remedy this issue? I can't figure out why it's not connecting when it's showing up in the com ports.
Control "connects" to BlackBox. It won't "connect" to Interface. You use either Interface or CONTROL to run your CNC... Don't use the connect button... Use the Flashing Tool under Wizards and Tools Read the docs docs:interface:firmware-update-control [OpenBuilds Documentation] in detail And yes you need to use CONTROL if you are very far behind (also in the docs) docs:interface:firmware-error-partitions [OpenBuilds Documentation] And remember to review the docs on how things work on the newer firmware - wifi setup is via a CONTROL wizard these days docs:interface:wifi-setup-nextgen [OpenBuilds Documentation] Also good to review https://github.com/OpenBuilds/firmware/blob/main/interface/CHANGELOG.txt so you can see what you missed out on
So I screwed up and loaded the incorrect firmware onto the interface which then was confused and thought it was a black box. After 5 tries I was finally able to get the interface flashed with the correct firmware and thought I was in the clear. I am now stuck in device test mode and am having trouble with it recognizing the usb when it was working earlier when I tried to put the firmware onto it with the stick, so it's hanging. How do I turn test mode off? EDIT: I finally got test mode off by using a different USB stick and completed all the tests. Strangely, after it recognized the USB and had me put it in, out, then in again.... It doesn't recognize it now. *Shrug* I'll take what I can get.
Simply just flash each device from each correct tab and Indicates the USB port might be worn out or broken - sadly out of warranty by now - but look for a local electronics repair shop to solder in a new USB port for you Yes we check twice because worn ports sometimes works, sometimes doesn't - in/out then in/out double checks for you
This saga has more ups and downs than a championship football game lol As I'm stubborn, patient and refuse to give up, I kept beating on the various steps to figure out what was going on up until midnight and as we know, the simplest steps always work sometimes, so I formatted my drive and prepped it like it was a new USB....and now it works. I can't explain it, I'm not an electronics guy. I'm just happy that my 'normal' setup has been bulletproof since I put it together and I haven't had to do these steps repeatedly lol It's not a problem but now the only thing I need to do is figure out how to reset the Internet so I can connect. I'm getting the red wifi bars, but the address is all zeros and says 'not connected'. Not a big deal because I typically transfer files via USB. Logging in to the default 194 address doesn't fly, and the cfg file does nothing (I think this one is so old it predates the config thing) Thanks for coming on this journey of reawakening with me lol Undoubtedly I'll shake the interface or yell at it in a dead language and the Wi-Fi will somehow turn on. *shrug*
Yes, I read about that when I was trying to get the interface flashed and saw the Wi-Fi was handled through the connect. That's where I got the config thing from, I set everything up through there for the Wi-Fi. I don't know what to do with it once it's on the USB, I loaded it, turned on the interface and no internet. (Assuming it just sets itself up) and then when I open the USB and scroll to the config file on the interface, clicking the file does nothing. It beeps and nothing changes. I'm assuming I'm doing something wrong, technically this is way above my head so obvious solutions to many are beyond my understanding. I'll get it figured out, I'm just more used to YouTube walkthroughs than understanding jargon I'm unused to
Side question? I didn't want to start a new thread so I'll just ask here How do we go back to update 1.57? 1.58 messed up my Internet connectivity - my operating interface was connected fine to my wifi6 but now that I updated to 1.58 I no longer have connection to my home network. Both interfaces now say "no connection" with a red wifi symbol and all zeros as the address. Last week I was connected fine to my nighthawk system. The only change was updating
No difference in terms of wifi protocols (same chip on board, same antenna, always been 2.4b/g (older protocol, never did support Wifi 6), same firmware core down to the exact version of the ESP core etc) so just coincidence and "blaming the update" as observation bias. More likely just forgot to enter the SSID/password on docs:interface:wifi-setup-nextgen [OpenBuilds Documentation] Thats literally the only difference, instead if using a web interface to set the password, you place it in a text file on the USB. Thats all. Where it reads the ssid/password FROM then same connect code as always runs. Way way easier for non technical folks, and particularly with modern phones with Smart Wifi that disconnects AP endpoints without internet that messed with the web interface way. So a wizard to create the text file for them, was win win. Have an informed read through https://github.com/OpenBuilds/firmware/blob/main/interface/CHANGELOG.txt older versions of the firmware can of course be found in the same repository (commit history, browse files) BUT the version is not the issue... All you need is the right SSID/PSK, a router that supports 802.11b/g (compatibility mode on for wifi6 routers, mine creates a seperate fallback SSID for older devices for example) and the USB with the details plugged into Interface. Well and strong enough signal but that's sort of expected. Interface's antennas aren't the most sensitive and its inside the PCB case, so good strong signal If your router puts 802.11b/g on a different SSID, make sure to enter THAT SSID in the wizard.
Ok, got it squared away - the 1.58 update seemed to make my interface 'forget' it's settings for my slow side of my network. I had to log in to my Wi-Fi and set up a new 2.4ghz channel (we got fiber Internet recently and when the dude set it up he used my old network info) and after using CONTROL to set it up my interface is on the network. I've got my nighthawk satellite near the shop so I've got a nice strong signal too
