Then its likely been damaged, recheck the page, paying particular attention to section 6.3.1 - you'll want to find what killed it before replacing it
I did nothing, added nothing, it was running fine then just stopped. What has it killed? is it my laptop or the controller, if it is the controller how do I fix it or replace the usb
Hi Peter $40=1 workaround will now allow me to continuously jog from home position. Will there be an update to take into account terjeio's comments? Thank you both for your help.
I have a Teensy 4.1 with GRBLHal. Control doesn't recognize the Teensy. Is there a setting to get Control to connect to it and if not, can this be added to Control?
I tried a BluePill with the same result, believe that CONTROL is looking for the USB ID of the BlackBox, though it will find a generic Uno/GRBL controller.
As a bit of a work-around, you could try compiling GRBL_HAL with a higher compatability setting: Compatibility level
Its quite easy: http://svn.io-engineering.com:8080/ Compatibility mode is on Advanced Tab. That said, we don't compile grblHAL with compatibility for our controllers. It works just fine without. We made CONTROL work with GrblHAL around V1.0.333 onwards (See OpenBuilds-CONTROL/CHANGELOG.txt at master · OpenBuilds/OpenBuilds-CONTROL ) We don't check for USB IDs or anything, we (1) try autoreset (Arduino/ESP32 style with DTR/RTS) - on boot Grbl sends its standard greeting (Grbl vX.Xx ['$' for help]) If that doesn't respond after a second or two, we try method (2) - sending Ctrl+X to reboot Grbl in case its running on a board that doesn't support Autoreset Again we wait for (Grbl vX.Xx ['$' for help]). If that also doesn't get a response we send "version\n" which is a Smoothieware command (legacy from when OpenBuilds used to sell Smoothieboards) and if we get the response it is smoothy, or timeout on the other two methods, we print out a "no firmware found" thing See OpenBuilds-CONTROL/index.js at master · OpenBuilds/OpenBuilds-CONTROL and OpenBuilds-CONTROL/index.js at master · OpenBuilds/OpenBuilds-CONTROL So if a 3rd party board is running 115200 baud, and accepts a Ctrl+X over serial and then reboots and prints the startup message - it should work
not the bluepill, the PiPico, responds like this [15:57:41] [ 3D Viewer ] WebGL Support found! success: this application will work optimally on this device! [15:57:42] [ websocket ] Bidirectional Websocket Interface Started Succesfully [15:57:43] [ update ] Checking for Updates [15:57:43] [ update ] You are already running OpenBuilds CONTROL 1.0.370 [15:57:51] [ connect ] PORT INFO: Port is now open: COM7 - Attempting to detect Firmware [15:57:51] [ connect ] Checking for firmware on COM7 [15:57:51] [ connect ] Detecting Firmware: Method 1 (Autoreset) [15:57:51] [ ] ok [15:57:52] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [15:57:52] [ connect ] Detecting Firmware: Method 3 (others that are not supported) [15:57:52] [ ] error:9 [15:57:55] [ connect ] ERROR!: No supported firmware detected - See docs:blackbox:faq-usb-connection-failed [OpenBuilds Documentation] for more details. Closing port COM7 [15:57:55] [ disconnect ] PORT INFO: Port closed bCNC connects into ALARM state which is expected because there are no limit switches connected. Ithink DTR is not resetting the Pico
It can not since that will kill the USB stack Many grblHAL drivers have "native" USB support meaning that there is no FTDI or similar UART <> USB chip that less capable MCUs needs (8-bit Arduinos, ESP32, ...). More info here. If the controller boots into, or is in, a "normal" state when connecting CONTROL seems to work fine, here is a log from a Pi Pico connection: ... [16:52:53] [ $$ ] $481=200 ;Autoreport interval in ms [16:52:53] [ $$ ] $484=1 ;unknown [16:52:53] [ $$ ] ok [16:52:53] [ $I ] [VER:1.1f.20230913ico CNC] [16:52:53] [ $I ] [OPT:VNMSL+2,35,1024,3,0] [16:52:53] [ $I ] [AXS:3:XYZ] [16:52:53] [ $I ] [NEWOPT:ENUMS,RT+,ES,SED,RTC,ETH,FTP,SSDP,SD] [16:52:53] [ $I ] [FIRMWARE:grblHAL] [16:52:53] [ $I ] [NVS STORAGE:*EEPROM 8K] [16:52:53] [ $I ] [FREE MEMORY:130K] [16:52:53] [ $I ] [DRIVER:RP2040] [16:52:53] [ $I ] [DRIVER VERSION:230828] [16:52:53] [ $I ] [DRIVER OPTIONS:SDK_1.5.0] [16:52:53] [ $I ] [BOARDicoCNC] [16:52:53] [ $I ] [AUX IO:0,7,0,1] [16:52:53] [ $I ] [WIZCHIP:W5500] [16:52:53] [ $I ] [IP:10.0.0.69] [16:52:53] [ $I ] [PLUGIN:WebUI v0.20] [16:52:53] [ $I ] [PLUGIN:SDCARD v1.10] [16:52:53] [ $I ] [PLUGIN:FS macro plugin v0.06] [16:52:53] [ $I ] ok [16:52:53] [ $G ] [GC:G0 G54 G17 G21 G90 G94 G49 G98 G50 M5 M9 T0 F0 S0.] [16:52:53] [ $G ] ok [16:52:54] [ connect ] Firmware Detected: grbl version 1.1f on COM30 [16:57:07] [ ] GrblHAL 1.1f ['$' or '$HELP' for help]
That would be part of it for sure yes. BlackBox still has usb chips (FTDI and later versions CP2102s) so that's what we have it built for.
Hello Peter, Can I ask you a ? I got Openbuilder going on a Mac OS 10.13 and trying to USB hook up our Genmitsu CNC 3018-PRO Router. No black box, just the Genmitsu board on back of the CNC. It reads : No supported firmware detected - See docs:blackbox:faq-usb-connection-failed [OpenBuilds Documentation] for more details. Closing port /dev/tty.Bluetooth-Incoming-Port That page is now gone. Do you know of the firmware or driver for our Mac? A download link? The read out code is below. Thank you, Andrew ---- [20:04:26] [ 3D Viewer ] WebGL Support found! success: this application will work optimally on this device! [20:04:26] [ websocket ] Bidirectional Websocket Interface Started Succesfully [20:05:05] [ connect ] PORT INFO: Port is now open: /dev/tty.Bluetooth-Incoming-Port - Attempting to detect Firmware [20:05:05] [ connect ] Checking for firmware on /dev/tty.Bluetooth-Incoming-Port [20:05:05] [ connect ] Detecting Firmware: Method 1 (Autoreset) [20:05:05] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [20:05:06] [ connect ] Detecting Firmware: Method 3 (others that are not supported) [20:05:09] [ connect ] ERROR!: No supported firmware detected - See docs:blackbox:faq-usb-connection-failed [OpenBuilds Documentation] for more details. Closing port /dev/tty.Bluetooth-Incoming-Port [20:05:09] [ disconnect ] PORT INFO: Port closed [20:07:35] [ network ] Starting network scan for: 192.168.1.1-192.168.1.254 [20:07:37] [ network ] Network Scan completed. Found 0 devices [20:09:47] [ connect ] PORT INFO: Port is now open: /dev/tty.Bluetooth-Incoming-Port - Attempting to detect Firmware [20:09:47] [ connect ] Checking for firmware on /dev/tty.Bluetooth-Incoming-Port [20:09:47] [ connect ] Detecting Firmware: Method 1 (Autoreset) [20:09:48] [ connect ] Detecting Firmware: Method 2 (Ctrl+X) [20:09:48] [ connect ] Detecting Firmware: Method 3 (others that are not supported) [20:09:51] [ connect ] ERROR!: No supported firmware detected - See docs:blackbox:faq-usb-connection-failed [OpenBuilds Documentation] for more details. Closing port /dev/tty.Bluetooth-Incoming-Port [20:09:51] [ disconnect ] PORT INFO: Port closed [20:10:15] [ network ] Starting network scan for: 192.168.1.1-192.168.1.254 [20:10:17] [ network ] Network Scan completed. Found 0 devices
Yes, that entitles the person to tech support, and it would just work. It contributes to CONTROLs development. Etc
You don’t need to justify yourself to me, I added the winky smiley to indicate it was a wind up. I guess it didn’t translate.
does the Genmitsu controller run standard GRBL 1.1? if not then CONTROL will not work, but bCNC might.
I was away over the weekend and when I came back today I powered the machine up. I checked the version of Control and it's 1.0.370 and this time Control connected to the Teensy 4.1. Alas...not all was going smooth. I tried the Probe and it worked perfect on the Z axis. I then run a cutting file, without having the motors connected, and none of the limit switches triggered. I then pushed the E-stop and it stopped the machine and disconnected the USB connection. I reset the E-Stop and the port was available again and I could reconnect Control to the Teensy. I turned off Control and ran IOSender and the limit switches were recognized with no problem. Nothin in the setting up of the machine was changed. BTW, the homing button in Control was grayed out. I can't recall if it was also grayed out when I had the Arduino Nano connected. I do recall that I used it once or twice a long while ago in a old version of Control.
Make sure to set Homing Cycle to something other than 0 If its just troubleshooting tab, check your report mask. Otherwise, check that Hard Limits is on
Yeah, my bad, I forgot that the setup is saved on the chip and not in Control. In IOSender it must be default and that's why I had the limit switches work. After I've set the parameter you've mentioned everything is fine. I still have a few issues, like the spindle PWM is only 3.3V on the Teensy. It must be a common issue since there is a board, wildly sold, that changes it from 0-3.3V to 0-10V. I have one coming today and hopefully it will rectify this problem. The last issue I have is with the E-Stop but I have to check if it's also in IOSender. BTW, If I home the Y axis, which has dual motors, will it square it or is there a setting I have to set? I have a limit switch installed on the A axis.
E-Stops MUST cut power. A software pause is useless when the router is busy degloving your hand, or your PSU is on fire. Real history... Not fun
As you've mentioned in the past, there are two kinds of E-Stop. One that shuts down everything, preventing just what you've said above, and one that works similarly to the Open Door switch. I HAVE BOTH!!! Now I want the latter to work as mentioned.
Fantastic - but just remember I can't remember all the thousands of people on here's specific setups (; - and will always advocate for others' safety. So take it for what it is thanks. Good luck
How mature is the fluidnc firmware support.. right now, I am having issues with the fluidnc tab and the configuraiton file showing errors due to random messages that the controller throws in the command line when Control reads the config (mpos idle and position location which appears randomly).
Still very much unstable FluidNC support · Issue #283 · OpenBuilds/OpenBuilds-CONTROL with tonne of todo work. We'd love to work on it but this whole year the Dev team has been occupied on an exciting new project, so have had not resources to dedicate to it yet.
I have a simple Control software question. I am using a router on my SainSmart CNC. When I am machining a complex file with a significant amount of lettering, the router constantly starts and stops as it raises up to the "safe Z" between cuts. I can't image this is good for the router. Is there a command that will just keep the router running constantly until the file is completed?
