LarryM
March 18, 2016, 8:16pm
6
@JonUdell
Try reading through the following threads. The X-controller uses grbl version 1.0? which has some changes in the status report mask bits and display, so there are some differences from the information in the following threads.
I’ll try to take a look at the 1.0? release and see what the changes were and get back to you later.
Direct access to grbl.
You can interact with grbl directly to isolate problems at the low level.
To do so, you need to use a terminal type program to issue commands and get responses from the serial port that has the Arduino attached.
Some of the programs are HyperTerminal, Putty, UGS (limited access), and the Serial Monitor in the Arduino IDE, among others.
Make sure that you have the correct settings for the program that you use.
The COM port where the Arduino is attached should have the …
If you are having difficulties with your homing switches you can do a quick test with Grbl to see what the state of the homing switches is from Grbl’s point of view. NOTE: In order to use this procedure you need to have grbl Version 0.9j or later installed on your Arduino.
To do so, you use the Grbl status immediate command ? (question mark). This command asks Grbl for its current value of some of its state information. For the purpose of this article we are interested in the homing switch stat…
Looking at things from the grbl perspective, the term “limit switch” only applies for the X-carve if you use hard limits ($21=1) .
Looking at things from the grbl perspective, all other cases for the X-carve the switches are “homing switches”.
Homing switches allow soft limits ($20=1) to work. For this case the “limits” depend on having done the homing cycle and on the low end the limits are 0,0,0 and the limits on the high end are set by $130, $131, and $132. After the homing sequence the swi…