-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't connect #4
Comments
Hello, If port is correct then close any other software, like UGS, that are using the port |
The port is not in use. I even rebooted. It looks like both your project and UGS use JSSC for serial, and UGS is working fine (the 7/23 nightly build anyway). |
Have you tried this ? Note for MAC users: You may need to create a "/var/lock" directory with write permission. To do this open the Terminal application and run the following two commands: |
Yes, UGS has the same suggestion and as mentioned UGS is connecting fine.
|
Do you have an official arduino with FTDI chip or a clone with the CH340 ? |
I have a Sanguino with a (version 1) USB-BUB from Modern Device. The chip has an FTDI logo on it. |
Hello, Did you manage to connect ? |
Hi, no I didn't. I've committed to using Universal GCode Sender so I've not tried again. |
Really sorry to hear that and really sorry to bother you |
115200 |
Hello, I have a Mac 10.13.1, GRBL 1.1f with Java 1.8.0_25. I get the following when I try to connect. There are no other options from the ones selected. I'm confident it's the correct port and it's functional. Is there any logging done? What could be wrong? My GRBL installation works fine with UGCS.
Thanks.
The text was updated successfully, but these errors were encountered: