Advanced Search

This is not really LinuxCNC related but something I should have done years ago, 3D-printed T-slot covers. It makes it much easier to vacuum up all the chips of the table.

 

 

It took three iterations to get the profile right, here are the test pieces I went through.

 

Here is the complete set that I installed.

 

They are printed out of flexible TPU filament and took about 4,5 hours to print on a Bambulab P1S printer.
 

PCW wrote:

The 7I33 can just ..., not pin-by-pin as most newer Mesa cards can do.

 

Is there a better alternative to the 7i33- just in case?

How can I get the spindle indexed?  Setup at the spindle is different- the motor encoder (G5) is just wired to the amplifier and not accessible for me, but a second encoder for threading (G2) is driven by the spindle via a toothed belt (1:1)
Signals for G2 are similar to the axes encoder signals, Ua1/Ua1*, Ua2/Ua2* and the index Ua0 single (non differential)

Mechanical Setup:

 

Wiring of G2:

 

I have the spindle running with G2 as a feedback- this works fine but I will need the index for threading.
How can I manage this?   I tried to make the index visible in HAL Scope, but can not set the "index enable" (get an error message)

The encoder G2 is connected to the 7i33 as ENC02, as said works fine for spindle feedback so far.

Sigi

# The Step signal for my machine is inverted. I tried to remove the inversion from the step signal, but than the Stepper don´t move at all. Does that make sense??

please check your Opto-Outputs, perhaps they are too slow for the short pulses. ?!?!

EDIT: and please add you config

Hello
Im trying to include my own tab to flex gui touch (great wotks! Thanks to author!). I see that already there fsc_container which corresponds to /usr/lib/libflexgui/fsc.ui and now i wanna to add my own tab - for example i have some rs232 device to read some  parameters (thc, edm for example, device already connected to hal via user space component linuxcnc). And i dont understand how to include thc.ui to the tab like dsf / fsc ?

Deleted message because of wrong informations!

www.geraldonit.com/auto-mount-nfs-share-using-systemd/

My config, original non-auto line commented out new auto one below
#192.168.1.70:/exports/share /nfs/share nfs users,noauto,hard,intr 0 0
192.168.1.70:/exports/share /nfs/share nfs users,_netdev,auto,x-systemd.automount,x-systemd.requires=network-online.target,x-systemd.device-timeout=5s 0 0

Thanks for the response.

Changed the parameters in the /etc/fstab entry to:
defaults,x-systemd.automount,x-systemd.mount-timeout=30,_netdev,x-systemd.after=network-online.target 0 0

This works fine, thanks.
John.

"automount nfs but wait for interface to be up" is a google search phrase that brings up some good answers. Apparently there are some options you can add to fstab to help out.

My guess is that it's trying to mount the nfs share before the wifi interface is up.
So you may have to look through dmesg to see when the nfs share is being mounted and when the wifi interface is being brought up.
Do you have any issues trying to mount the share after the wifi network is up ?

There may be a way to do it via systemd that waits for the wifi network to come up, I've got a couple of ones that turn off the power related stuff for wifi, but only after the interface is up. Might be able to use the same mechanism to mount the shares once that interface is up.

I'd suggest this isn't a issue related to the Raspberry Pi platform but any situation where an nfs or samba share is automounted and the required interface isn't up at that time.