LIGHTBURN CAMERA K40 DRIVER
Missing Windows Driver: Win10 does not require a virtual com port driver however earlier versions of Windows do need a driver. USB plug is not making proper contact with socket – check for looseness. The USB cable is power only, it needs to be a USB data cable. Plug Mini Gerbil and other USB devices into PC directly, not via a common hub. Mini Gerbil is used with a USB hub, especially one shared with other peripherals like a USB camera. Incorrect Device selected in Lightburn – select ‘Gerbil STM’ Mini Gerbil is not compatible with K40 Whisperer
LIGHTBURN CAMERA K40 SOFTWARE
Wrong software – Mini Gerbil works with Lightburn, and some other software is possible (but unsupported). Power LED shines, but inconsistent or no connection to PC software Likely causes and their solutions (in recommended sequence) Return to Mini Gerbil debugging Symptom Detail For example if your X min endstop pin is inverted, change : alpha_min_endstop 1.Mini Gerbil debugging – no communication with PC software You can fix that situation by inverting the digital input pin in your configuration file. If an endstop is read as pressed when it is not, and not pressed when it is, then your end-stop is inverted. If an end-stop is reading as always pressed, or never pressed, even when you press or release it, then you probably have a wiring problem, check everything.
LIGHTBURN CAMERA K40 MANUAL
Now manually actuate the X endstop (press it if manual or use folded paper to interrupt if optical).Click on the Console tab, enter M119 in the text box (under the Macro buttons) and hit Enter on the keyboard.Click Next, click Finish, and finally click Okay.Make sure origin is set to FRONT LEFT and that “Auto Home On Startup” is toggled OFF.Click Next on “pick your laser”, click Next again on “how to connect”, and click Next once more.Open LightBurn and click the Devices button in the Laser panel the double-click your device.Make sure the machine is safe to mess around in and turn off the laser power off so the laser cant fire.Now let’s apply this to your situation and test your endstops: The above output means that the X endstop IS pressed and the Y and Z endstops are NOT pressed. When M119 is entered in to the console the controller will answer with the status of each endstop that will look something like this : X min:1 Y min:0 Z min:0 There is a command that allows you to debug this kind of situation : the “M119” G-code. Your controller must be G-code based and be supported by LightBurn, LightBurn must be able to communicate with the controller, and you must manually actuate and deactuate the endstops. There are a few prerequisites for this to work. If you have a Cohesion3D or other Smoothie based controller you can troubleshoot your endstops from within the LightBurn console. Sometimes endstops can cause some hard-to-find issues.