Advanced Search

Probably doable if there is protocol documentation.

It is digital sl2-100 not xy2-100

If it's a digital XY2-100 interface, there's a hostmot2 driver

@Endian,

I am not ready with the .iso, but you can try this archive. Unpack it where you want.
Then : ./install.sh

I didn't test it on a fresh .iso so i can not confirm it works straight away.
After installing goto : ~/linuxcnc/cmake/configs and do : ./run_axis_9

At your own risk:
repository.qtpyvcp.com/repo/linux-distro/lcnc_archive.tar


 

www.forum.linuxcnc.org/27-driver-boards/...analog-galvo-scanner

Hello.
Knows anyone something about driving sl2-100 galvo scanner ?

Hi,

When I edited qtaxis.ui I found the new functions I added to the handler file in "signal editing  / slot " panel. Now I add another function to the handler file and I don't recall what I need to do to find it in "signal editing  / slot " panel... I know I could edit manually the ui file and that's work, but I prefer having it there.
Thanks.

Ronan

unknown wrote:

Linuxcnc complains about /usr/bin/kill not being there but it's under /bin/kill which might have to do with debian having /bin /sbin & /lib being links to /usr/bin /usr/sbin & /usr/lib/ and Devuan not taking that road.

 

That's something that is meant to have changed in Debian too, in fact LinuxCNC is being "told off" about it:
github.com/LinuxCNC/linuxcnc/pull/3388
 

Have you tried it with just hal_input?

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

Not really, as the system has no way to know if the user-defined codes are modal or not.

I don't think that "probe tripped during non-probe move" is generated by probe_basic (or by any GUI). It's built-in to core LinuxCNC.

There are a couple of INI settings in [TRAJ] that might be worth trying, though I don't think that they are quite what you want:

linuxcnc.org/docs/stable/html/config/ini...tml#sub:ini:sec:traj
(right at the end of the section, NO_PROBE_..._ERROR )

It seems likely that the problem is with the Fusion probe routine, though, are you absolutey sure that it isn't making a non-probe move into probe contact?

If you set up the HAL so that motion.probe-input is AND-ed with the motion.motion-type == 5 ( "probing") then you can completely bypass the error report. But it is an error indicatiing a genuiune isssue in most cases.
linuxcnc.org/docs/stable/html/man/man9/m...9.html#MOTION%20PINS

Sorry for the late reply.

I think that this woud be difficult, as the Hostmot2 main driver needs to know what to do with your new module.

The UART / PktUART drivers are provided with a "hook" with which the external comps can get access to the register data, so at the very least you would need to do that.

I think that you will need to find some other way to persist your changes going forwards, unfortunately. You can probably keep a patch file to re-apply your changes (which would be limited to a standalone handler for your module, and additions to hotmot2.h and hostmot2.c

I also don't see any way to avoid re-compiling LinuxCNC to include your code.

Are you sure that no-one else would ever want your module? From your point of view adding it to the main codebase would be cleanest.

Note that you also want to make sure that you avoid a clash with the "official" Mesa GTAGs ( github.com/LinuxCNC/linuxcnc/blob/master...tmot2/hostmot2.h#L94 )

Won't work, redirect of output is not done by superuser but by the invoking user.
Some solutions here stackoverflow.com/questions/84882/sudo-e...egedfile-doesnt-work

Which voltage divider setting is prefferred for a Hypertherm Powermax plasma cutter when connected to a Mesa THAD-10?
The options are 20:1 _ 21.1:1 _ 30:1 _ 40:1 _ 50:1
Is one preferred over the other for better resolution or response time?
 

@Grotious

Installation by following your steps is not finished well probably ...

Which files to patch ?

with your script \