Hi Guys I have just done the upgrade on my K40 to a Mini Gerbil. I can finally use some real software.
I have been trialing lightburn and love it. My question is. If I hook up to my windows 10 laptop I can stream to the laser no problem. But when I connect to my Mac. it will connect but errors when trying to stream. It also behaves badly when jogging and homing. So must be a communication problem. But what is really odd, if I run lightburn in windows on a VM on my Mac it works fine. Any thoughts. Thanks Matt.
Can’t really offer much except to say that I can talk to TinyG, Smoothie, GRBL, with Lightburn on my Mac with no problem.
Do you have a specific error message?
Have you looked at the log?
No I was getting stream error in the console. I will track down the log and have a look
Are you sure you haven’t got another app open that is talking to that port?
I got excited I got home and had a slicer oper that could have been trying to communicate. But unfortunately no. Still the same issue. it is running the cutter but not doing the correct things.
This is some of the errors I get in the console
error:1
error:22
error:22
error:1
error:22
Starting stream
error:2
On or near line 0:
error:1
On or near line 3:
Stream completed in 0:00
ok
ok
ok
ok
Starting stream
error:1
On or near line 4:
Stream completed in 0:00
ok
ok
Starting stream
error:2
On or near line 0:
Stream completed in 0:00
ok
ok
Starting stream
error:2
On or near line 0:
Stream completed in 0:00
**I turned on the debug log. **
Here is the result
22:26:38.533 D: “LightBurn 0.8.07” “Fri Mar 1 2019”
22:26:43.630 D: Enumerating ports:
22:26:43.630 D: “starting” busy: false state: 0
22:26:43.631 D: Port: “cu.Bluetooth-Incoming-Port”
22:26:43.631 D: PID: 0 VID: 0
22:26:43.631 D: Manufacturer: “”
22:26:43.631 D: Description: “incoming port - Bluetooth-Incoming-Port”
22:26:43.631 D: System Loc: “/dev/cu.Bluetooth-Incoming-Port”
22:26:43.631 D: Serial: “”
22:26:43.631 D:
22:26:43.631 D: Port: “tty.Bluetooth-Incoming-Port”
22:26:43.631 D: PID: 0 VID: 0
22:26:43.631 D: Manufacturer: “”
22:26:43.631 D: Description: “incoming port - Bluetooth-Incoming-Port”
22:26:43.631 D: System Loc: “/dev/tty.Bluetooth-Incoming-Port”
22:26:43.631 D: Serial: “”
22:26:43.631 D:
22:26:43.631 D: Port: “cu.usbmodem4993185B39341”
22:26:43.631 D: PID: 22336 VID: 1155
22:26:43.631 D: Manufacturer: “tomeko net”
22:26:43.631 D: Description: “STM32F103C8T6”
22:26:43.631 D: System Loc: “/dev/cu.usbmodem4993185B39341”
22:26:43.631 D: Serial: “4993185B3934”
22:26:43.631 D:
22:26:43.631 D: Port: “tty.usbmodem4993185B39341”
22:26:43.631 D: PID: 22336 VID: 1155
22:26:43.631 D: Manufacturer: “tomeko net”
22:26:43.632 D: Description: “STM32F103C8T6”
22:26:43.632 D: System Loc: “/dev/tty.usbmodem4993185B39341”
22:26:43.632 D: Serial: “4993185B3934”
22:26:43.632 D:
22:26:43.682 D: Found port: PID 22336 VID 1155
22:26:43.682 D: Manufacturer: “tomeko net”
22:26:43.682 D: Product: “STM32F103C8T6”
22:26:43.682 D: Name: “cu.usbmodem4993185B39341”
22:26:43.697 D: Port open succeeded
22:26:43.731 D: “starting” busy: false state: 0
22:26:43.731 D: “switching to connect” busy: false state: 1
22:26:43.731 D: “Connecting…” busy: false state: 1
22:26:43.731 D: “Awaiting response…” busy: true state: 4
22:26:43.732 D: O: “24480a”
22:26:44.195 D: I: “6f6b0d0a6f6b0d0a6572726f723a310d0a”
22:26:44.196 D: I: “6572726f723a32320d0a6572726f723a32320d0a6572726f723a310d0a6572726f723a32320d0a”
22:26:47.100 D: got stream
22:26:47.100 D: S: 8 TB: 8 LC: 1 OK: 0 RC: 0
22:26:47.100 D: S: 4 TB: 12 LC: 2 OK: 0 RC: 0
22:26:47.100 D: S: 20 TB: 32 LC: 3 OK: 0 RC: 0
22:26:47.100 D: S: 4 TB: 36 LC: 4 OK: 0 RC: 0
22:26:47.101 D: O: “473231204735340a4739300a473120583132205933342046363030302053300a”
22:26:47.101 D: 36 bytes in 0.001 seconds, 36000 avg bytes per second
22:26:47.101 D: 4 lines @ 4000 avg lines per second
22:26:47.102 D: O: “4739300a”
22:26:47.103 D: I: “6572726f723a320d0a6f6b0d0a6f6b0d0a6f6b0d0a6572726f723a310d0a”
22:26:47.104 D: R: 8 TB: 28 OK: 0 RC: 1
22:26:47.104 D: I: “6f6b0d0a6f6b0d0a6f6b0d0a”
22:26:47.104 D: R: 4 TB: 24 OK: 1 RC: 2
22:26:47.104 D: R: 20 TB: 4 OK: 2 RC: 3
22:26:47.104 D: R: 4 TB: 0 OK: 3 RC: 4
22:26:47.557 D: I: “6f6b0d0a6f6b0d0a6f6b0d0a6f6b0d0a”
22:26:55.817 D: got stream
22:26:55.818 D: S: 8 TB: 8 LC: 1 OK: 0 RC: 0
22:26:55.818 D: S: 4 TB: 12 LC: 2 OK: 0 RC: 0
22:26:55.818 D: S: 20 TB: 32 LC: 3 OK: 0 RC: 0
22:26:55.818 D: S: 4 TB: 36 LC: 4 OK: 0 RC: 0
22:26:55.819 D: 36 bytes in 0.001 seconds, 36000 avg bytes per second
22:26:55.819 D: 4 lines @ 4000 avg lines per second
22:26:55.820 D: O: “473231204735340a4739300a473120583133205933332046363030302053300a4739300a”
22:26:55.822 D: I: “6f6b0d0a6f6b0d0a6f6b0d0a6f6b0d0a6572726f723a310d0a”
22:26:55.823 D: R: 8 TB: 28 OK: 1 RC: 1
22:26:55.823 D: R: 4 TB: 24 OK: 2 RC: 2
22:26:55.823 D: R: 20 TB: 4 OK: 3 RC: 3
22:26:55.823 D: R: 4 TB: 0 OK: 4 RC: 4
22:26:55.823 D: I: “6f6b0d0a6f6b0d0a”
22:27:00.472 D: 1 floaters
22:27:00.472 D: SpatialQuery build: 0
22:27:00.472 D: PathTree build: 0
22:27:00.474 D: Crossing time: 0 Output time: 1
22:27:00.474 D: Optimize by score: 0 ms
22:27:00.475 D: Protocol::GenerateCuts time: 0
22:27:00.476 D: got stream
22:27:00.477 D: S: 20 TB: 20 LC: 1 OK: 0 RC: 0
22:27:00.477 D: S: 4 TB: 24 LC: 2 OK: 0 RC: 0
22:27:00.477 D: S: 3 TB: 27 LC: 3 OK: 0 RC: 0
22:27:00.477 D: S: 3 TB: 30 LC: 4 OK: 0 RC: 0
22:27:00.477 D: S: 11 TB: 41 LC: 5 OK: 0 RC: 0
22:27:00.477 D: S: 4 TB: 45 LC: 6 OK: 0 RC: 0
22:27:00.477 D: S: 18 TB: 63 LC: 7 OK: 0 RC: 0
22:27:00.477 D: S: 10 TB: 73 LC: 8 OK: 0 RC: 0
22:27:00.477 D: S: 10 TB: 83 LC: 9 OK: 0 RC: 0
22:27:00.477 D: S: 10 TB: 93 LC: 10 OK: 0 RC: 0
22:27:00.477 D: S: 11 TB: 104 LC: 11 OK: 0 RC: 0
22:27:00.477 D: O: “473030204731372047343020473231204735340a4739300a4d340a4d380a47305834322e355938340a4739310a4731582d33322e354639303030533230300a4731592d302e3153300a”
22:27:00.477 D: S: 10 TB: 114 LC: 12 OK: 0 RC: 0
22:27:00.477 D: S: 10 TB: 124 LC: 13 OK: 0 RC: 0
22:27:00.479 D: O: “4731583635533230300a4731592d302e3153300a4731582d3635533230300a4731592d302e3153300a”
22:27:00.479 D: I: “6572726f723a320d0a6f6b0d0a6f6b0d0a6f6b0d0a”
22:27:00.480 D: R: 20 TB: 104 OK: 0 RC: 1
22:27:00.480 D: I: “6f6b0d0a6f6b0d0a6f6b0d0a6f6b0d0a”
22:27:00.480 D: R: 4 TB: 100 OK: 1 RC: 2
22:27:00.480 D: R: 3 TB: 97 OK: 2 RC: 3
22:27:00.480 D: R: 3 TB: 94 OK: 3 RC: 4
22:27:00.480 D: R: 11 TB: 83 OK: 4 RC: 5
22:27:00.480 D: R: 4 TB: 79 OK: 5 RC: 6
22:27:00.480 D: R: 18 TB: 61 OK: 6 RC: 7
22:27:00.480 D: R: 10 TB: 51 OK: 7 RC: 8
22:27:00.480 D: 13 lines @ 4333.33 avg lines per second
22:27:00.481 D: I: “6f6b0d0a6f6b0d0a”
22:27:00.482 D: I: “6f6b0d0a6f6b0d0a6f6b0d0a6f6b0d0a”
22:27:07.950 D: 1 floaters
22:27:07.950 D: SpatialQuery build: 0
22:27:07.951 D: PathTree build: 0
22:27:07.952 D: Crossing time: 0 Output time: 1
22:27:07.952 D: Optimize by score: 0 ms
22:27:07.953 D: Protocol::GenerateCuts time: 0
22:27:07.955 D: got stream
22:27:07.955 D: S: 20 TB: 20 LC: 1 OK: 0 RC: 0
22:27:07.956 D: S: 4 TB: 24 LC: 2 OK: 0 RC: 0
22:27:07.956 D: S: 3 TB: 27 LC: 3 OK: 0 RC: 0
22:27:07.956 D: S: 3 TB: 30 LC: 4 OK: 0 RC: 0
22:27:07.956 D: S: 11 TB: 41 LC: 5 OK: 0 RC: 0
22:27:07.956 D: S: 4 TB: 45 LC: 6 OK: 0 RC: 0
22:27:07.956 D: S: 18 TB: 63 LC: 7 OK: 0 RC: 0
22:27:07.956 D: S: 10 TB: 73 LC: 8 OK: 0 RC: 0
22:27:07.956 D: S: 10 TB: 83 LC: 9 OK: 0 RC: 0
22:27:07.956 D: S: 10 TB: 93 LC: 10 OK: 0 RC: 0
22:27:07.956 D: S: 11 TB: 104 LC: 11 OK: 0 RC: 0
22:27:07.956 D: S: 10 TB: 114 LC: 12 OK: 0 RC: 0
22:27:07.956 D: S: 10 TB: 124 LC: 13 OK: 0 RC: 0
22:27:07.957 D: O: “473030204731372047343020473231204735340a4739300a4d340a4d380a47305834322e355938340a4739310a4731582d33322e354639303030533230300a4731592d302e3153300a4731583635533230300a4731592d302e3153300a4731582d3635533230300a4731592d302e3153300a”
22:27:07.959 D: I: “6572726f723a320d0a6f6b0d0a6f6b0d0a6f6b0d0a6f6b0d0a6f6b0d0a”
22:27:07.960 D: R: 20 TB: 104 OK: 0 RC: 1
22:27:07.960 D: R: 4 TB: 100 OK: 1 RC: 2
22:27:07.960 D: R: 3 TB: 97 OK: 2 RC: 3
22:27:07.960 D: R: 3 TB: 94 OK: 3 RC: 4
22:27:07.960 D: R: 11 TB: 83 OK: 4 RC: 5
22:27:07.960 D: R: 4 TB: 79 OK: 5 RC: 6
22:27:07.960 D: 13 lines @ 2600 avg lines per second
22:27:07.960 D: I: “6f6b0d0a6f6b0d0a6f6b0d0a6f6b0d0a”
22:27:07.961 D: I: “6f6b0d0a6f6b0d0a”
This doesn’t make much sense. This is the first bit:
D: “Connecting…” busy: false state: 1
D: “Awaiting response…” busy: true state: 4
D: O: “24480a” ($H - this is the homing command)
D: I: “6f6b0d0a6f6b0d0a6572726f723a310d0a” (ok, ok, error:1)
D: I:6572726f723a32320d0a6572726f723a32320d0a6572726f723a310d0a6572726f723a32320d0a
(error:22, error:22, error:1, error:22)
So, that’s the standard GRBL homing command throwing an error, both an “expected GCode command” error and a “feed rate has not been set yet” error.
What kind of Mac are you using? Someone else using a new Mac with USB-C ports running through a converter had a bizarre issue along these lines where their machine would connect, but not fire.
From the debug log you’ve provided, LightBurn is sending proper GRBL commands, but it looks like the board is getting them garbled.
I’m just running a 2012 Mac pro running 10.14.3.
I still find it very odd that it runs under a Virtual machine on the same computer.
Could be a driver issue, perhaps. See if there’s an OSX driver for the Gerbil board, as that would be OS specific.
Did your use the VCP drivers from the Mini Gerbil site?
The card uses the FT232 serial/USB chip which has been supported under OS X for a while now.
That you can connect through a VM does seem to indicate that you are having a driver issue.
Try uninstalling the FTDI drivers, if you’ve installed them.
To remove the drivers from Mac OS X, the user must be logged on as root. Root is a reserved username that has the privileges required to access all files.
Start a Terminal session (Go > Applications > Utilities > Terminal) and enter the following commands at the command prompt:
cd /System/Library/Extensions rm -r FTDIUSBSerialDriver.kext
cd /Library/Receipts
rm -r FTDIUSBSerialDriver.kext
The driver will then be removed from the system.
Thanks did the uninstall. But still no joy. 
I may be stuck with using it with a pc. Don’t really feel like doing a clean install at this point. But it may be necessary. I might give my wife’s mac laptop a go and see how it works
I tried it on another mac running an earlier OSX and it worked no problem. So Now I just have to work out why it won’t work on my main mac. MMMM
Driver. Uninstall as per the instructions above.
Also run the HD through the disk check/verification, which ensures the right files are in place with the correct permissions.
As I said above I have done the uninstall. But it hasn’t helped. I will try the Disk check though 
Sorry Matt, I didn’t realise you had gone through the uninstall.
The whole situation with FTDI drivers was a total ball-ache for support worldwide 
How familiar are you with OS X internals? You managed to find the terminal, so that’s a good start… want to try something more complex?
I am pretty good. I have raspi pi’s for all my printers. So I tinker in the command line a bit. Just can’t sus this one. Must be driver. But don’t understand why the unistall didn’t help…
BECAUSE ITS SH!T 
You wouldn’t be the first to have this problem.
You did reboot it, didn’t you?
Yeah couple of times. Even tried the uninstall again but off course it couldn’t find anything
You could try re-installing the FTDI driver and removing the MacOS one. The issue seems to be that the two conflict with each other.
FTDI driver: https://www.ftdichip.com/Drivers/VCP.htm
Another guide for dealing with these: https://superuser.com/questions/1135730/how-to-release-reset-serial-port-ftdi-devices-mac-osx
1 Like
Good link! Thanks for that.
Thanks I will try that. Next chance and report back.
I actually have a not bad workflow happening at the moment. I have a pc laptop plugged into the laser and remote connect to the laptop on my mac workstation.