Advanced Search

Normally, I use the vertical head, which bolts on to the Y axis. But If I remove that vertical head, there is a second SK40 spindle directly in the Y axis, facing straight forward, so in that configuration, Y become -Z and Z becomes Y.
Cheers,
Mark

in spindle mode, the stepgen velocity command comes directly from
the (perhaps scaled) spindle velocity. The stepgen feedback position
would be ignored in spindle mode. The joint feedback could be looped
back from the C joint commanded position this case. Finally, a homing
to index move would be done to re-synchronize the spindle position to
absolute C coordinates.

Hi Guys, thanks for you time.
I've been doing my own search, but without much look to find some tutorial that explain me how to configure files, I know that something may have to be change on hal and ini but after that no much idea. If you guys could explain me what file have to be re-writted or changed with some explanation would be appreciated . 

details: 
sim axis vismach 5axis.table-rotary-tilting
using vasmich "would like to design my own machine is that is posible"
7c80  "hm2_rpspi"
connection /dev/spidev0.0
linuxcnc 2.9.3
raspberry pi 4 

uname -a 
Linux pi 6.6.44-rt39 #1 SMP PREEMPT_RT Mon Aug 12 21:10:13 AEST 2024 aarch64 GNU/Linux


let me know if you need more details

thanks!!

I have another question: what control card are you going to use, mesa or a parallel port?

Next Monday I will send you the configuration to use this servo motor as a spindle, I don't have it here at home.

PCW wrote:

position feedback must be unconnected in spindle mode

That would be ideal. And how should I do that?

I read everything posted in the forum regarding UART settings and didn't find anything specific, so I also spent quite some time trying to connect the EC500 to the computer's COM port. However, I was lucky enough to finally make the connection via the serial port. To connect the EC500 and the computer, you need a suitable RS232 adapter and to connect pin 2 (RX) of the adapter to pin 3 of the EC500, and pin 5 of the adapter to the corresponding pin on the EC500. The terminal settings are 115200 BPS, no parity check, 8-bit length, ASCII. The important thing is that in this case, the UART is not using TTL levels (3.3 or 5 volts), but rather requires an adapter for RS232 voltage levels.

Ok, just did the flash using mesaflash. Seemed to have worked. Not sure what's up with mesact. It worked fine the first time I did it. Oh well, easy enough to do from the terminal.

sudo mesaflash --device 7i96s --addr 10.10.10.10 --readhmid
sudo mesaflash --device 7i96s --addr 10.10.10.10 --write name.bin
sudo mesaflash --device 7i96s --addr 10.10.10.10 --reload
sudo mesaflash --device 7i96s --addr 10.10.10.10 --readhmid

I have managed to get linuxcnc to stop when an alarm goes off, but the driver does not turn on the red LED, so I will never know which driver is faulty...

Thank you for the detailed walkthrough. I understand now how to set things up. Though it will take sometime.

But before that, when I run lsusb in terminal, it shows me "command not found". I have to run that through less /proc/bus/input/devices .. to see the unique name for my keyboard. After I add the loadusr command to my ini file in the HAL section, the keyboard button still doesn't show up in my HALshow (I am currently trying all of this on axisgui). It only shows up my gamepad. I tried to input the command directly into the HAL file, but it still doesnt show up. Am I doing anything wrong? As I feel 'lsusb' should have shown something in the terminal

I know this thread is old, but it shows up at the top in Google search when you're looking for "LinuxCNC skew". I'd like to say that the millkins.c works for me in LinuxCNC 2.8.4.

Steps:

1. Download the millkins.c file here: wiki.linuxcnc.org/cgi-bin/wiki.pl?Contri...y_XY_skew_correction
2. In LinuxCNC open up the terminal to compile/install the file. Replace code block below to where actual millkins.c file is located.

   sudo halcompile --install /path/to/millkins.c

3. The command above compiles and creates a millkins.so file located at /usr/lib/linuxcnc/modules
4. You can go ahead and close the terminal and now open up your hal file. Find the line (should be at the top) "loadrt [KINS]KINEMATICS" and replace with millkins info. Replace #.### in example below with your actual skew factor.

   # Comment out the kinematics in case you want to roll back and add the two lines after installing millkins.so
   #loadrt [KINS]KINEMATICS
   loadrt millkins
   setp millkins.skew #.###

5. That's it, but here is the big gotcha: This skew factor will not work when you are jogging! If you actually do a gcode command you should see it work.

Hope this helps for anyone searching this! This has been working great for me as I have a 4'x8' gantry and it is quite difficult to get this perfectly mechanically square. I have been squaring by offsetting the home position of my dual steppers on a single axis, but this is a nice alternative.

Yes, they are connected

No need, it should work as is.
Do you have enable wired to your drives?

I use Raspery on Pi5, there are no problems, it starts automatically without a password when the first power comes on. While the CNC is running and processing materials, a password login screen appears occasionally, but the CNC does not stop and continues to work. What causes this encrypted login screen to appear?

You could try using the 'hal_input' component and see what keys your keyboard offers. These can then be connected in hal to the .increse/.decrease pins of gmoccapy.
linuxcnc.org/docs/html/gui/gmoccapy.html#_hal_pins

example:

1. open a terminal and type:
2. find your keyboard in the output
example: 'Bus 003 Device 002: ID 17ef:608c Lenovo Lenovo Calliope USB Keyboard'

3. Add this to the [HAL] section of your ini file using one of the words from the keyboard identification from above to identify the device (for our example we use 'Keyboard')

4. Start your config, enter the settings page and click on the 'Halshow' button in the lower right corner

5. Navigate to pins/input/0/ and check if any function keys have been recognized:

 

6. In our example there are some function keys we can use (eg 'input.0.key-volumeup', 'input.0.key-volumedown')

7. Connect these pins to the relevant gmoccapy halpins in the POSTGUI_HALFILE (eg to control the linear jog velocity):

possible pins can also be found in pins/gmoccpy.
 

linuxcnc.org/docs/html/man/man1/hal_input.1.html