Advanced Search

If you're thinking about absolute encoders and upgrading the steppers, you can also look into ethercat servos, but the encoders would be pre-backlash this way.

I see now in my deb installation there is not hal_priv.h file ... is possible? I try to fin it on /usr or /share or other system folder witrh no result ... these can be? In github is present ... why not in my installation?

regards

Does the BOB (blue board with the big connector) have any LED on?
Is it plugged into a USB on the PC?

I receive these error when try to use my app written in c++ .... with c++14 linuxmint 22 and Lcnc2.10 ....

seems there are something not find (library or what else ....) but not understand what is it!! Lcnc is regular install and work .... so not understand what library need after these:

LIBS+=  -Iinclude -I/usr/lib/linuxcnc/canterp.so
LIBS += -L/usr/lib -lnml -llinuxcnchal -llinuxcnc -llinuxcncini -DULAPI -lposemath -Isrc/emc/rs274ngc


regards
 

the Probotix controller works well, it's the other one (The first pictures) that does not work. the wires coming to the motors are getting power but the voltage does not change when I try to jog. I'm wondering if whatever wires bring the move signal are not doing their job. Originally I thought maybe it was a programming error, but if the Probotix box works...

also be aware that any changes made will be overwritten if you decide t update down the road with a newer release of probe basic. it may be wise to use the user tabs instead and remain on the stock version if you want ease and simplicity down the road.

we will be implementing some changes that allow certain buttons to be changed via user settings to better fit with routers, such as the flood and mist buttons will be interchangable with vaccum and dustcollector or similar etc.

are you using the designer launchers on the desktop to start qtdesigner? this is necessary for the venv.

one of the users that builds his own debs posted this in the group chat.

You need to set the pin to output mode.
(all GPIO start-up as input pins)

setp [HMOT](CARD0).gpio.024.is_output true
setp [HMOT](CARD0).gpio.024.out false
 

Someone correct me if I am wrong but, in the attached INI file versaprobe is defined:USE_PROBE = versaprobeI just went thru this learning curve myself. When versaprobe is defined one should only use the
the "Probe" tab at the top. When on the "Probe" tab one can click the "Probe Type" button to cycle thru
each of the different probe screens and make settings from there. One of the screens has a "Go to Tool Setter" button.
This button when clicked will move Z to above the tool setter, then when configured correctly, moves the Tool to within
10 mm as configured from the same screen. Then it stops just above the tool setter. Then the button on the screen just to the right of the
"Go to tool setter" when clicked will touch off and stop above the setter. Then, finally move Z to above your work piece and "Touchoff workpiece" which is the button below the last one you clicked. 

The hint(hover) from the buttons may be worded differently as I am relying on memory.

Hope that helps.
 

Is there any more to that than adding the line:

setp [HMOT](CARD0).gpio.024.out false

to my halfile? looking at Hostmot2 doc page, it doesn't look like it has to be explicitly added as a gpio in the loadrt hm2_pci config="...etc"

but I'm not sure what else might be required. I've just tried the above setp line, ending it either 'true' or 'false', and still have no activity on P3 pins

Benb wrote:

Couple of months ago I installed Linuxcnc rip on an intel i5 4the generation it installed flowlesslly. Try not to skip any steps, take your time don't rush otherwise you will have start all over again.
[edit] OOPS just realized that you loaded linuxcnc. You must start with Debian 12 os only nothing else.
 

Hello Benb,
I have installed fresh Debian 12 and following the instruction in PDF,This is the result in first few commands

cnc@cnc:~$ sudo apt update
[sudo] password for cnc:
Ign:1 cdrom://[Debian GNU/Linux 12.7.0 _Bookworm_ - Official amd64 DVD Binary-1 with firmware 20240831-10:40] bookworm InRelease
Err:2 cdrom://[Debian GNU/Linux 12.7.0 _Bookworm_ - Official amd64 DVD Binary-1 with firmware 20240831-10:40] bookworm Release
  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
Reading package lists... Done
E: The repository 'cdrom://[Debian GNU/Linux 12.7.0 _Bookworm_ - Official amd64 DVD Binary-1 with firmware 20240831-10:40] bookworm Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
cnc@cnc:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
cnc@cnc:~$ sudo apt-get install -y build-essential autoconf libtool libtool-bin bison flex libssl-dev libelf-dev libacl1-dev
libncurses-dev dwarves fakeroot
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package flex is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  libfl2

Package bison is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package libtool-bin
E: Package 'bison' has no installation candidate
E: Package 'flex' has no installation candidate
E: Unable to locate package libelf-dev
E: Unable to locate package libacl1-dev
bash: libncurses-dev: command not found
cnc@cnc:~$



 

mein.hal

ganz am Ende habe ich eingefügt.
Dann bekomme ich beim Starten den Fehler:
Habe dann die HAL von Controller genommen dammit get es. DANKE !!!  

Yes, a bump in the center of a plastic chip usually means its been overheated/damaged.

 You might check that the 27 Ohm resistor networks (RN1,RN2,RN8,RN14)
are OK as well (all 4 resistors per network  = 27 ohm)
A short to a bad voltage can damage these as well.

in der hal einen Pin vom Controller mit einem 'motion.digital-in-xx' verbinden und im Logger einen entsprechened Log trigger einrichten:

Also zum Beispiel:
 

You need to set GPIO bit 24 low to get the TX3 output enabled

sudo mesaflash --device 5i23 --dbname2 7i52 --readhmid

should help with the pinout