Advanced Search

Or you can help me compile and turn on WiFi. I use the AX200 wireless network card. Thank you.

Lcvette wrote:

Ok so you are using the probe as a master tool. I would advise against that, if you crash the probe you mist remeasure all tools after resetting the probe stylus with your method. Follow the method in the docs for best results so all tools measure from the spindle nose gage line. Then only the tool crashed or replaced requires remeasuring.

kcjengr.github.io/probe_basic/probing.html#probing-setup

 

After a long week of work I have finally been able to spend some time on the milling machine today...
I have tried to follow the steps in the link you posted but with the translation to my language it is a bit confusing for me.
What I have done is:

With the spindle nose I have reached my jaw and with a very thin paper I have touched 0.
Then I have mounted the 3d probe and I have touched the position of the probe at the same point and I have entered that distance in the tool table for the 3d probe

Then touching 0 with a thin paper I have done the same for the other tools.

I don't know if it is the correct way....

I have also been watching a video (I think it is yours) but I am not clear on how to do it either.  Probe Basic Tool Setter brief Tutorial (youtube.com)

royka wrote:

 
Also tested the 6.1.75 vendor kernel (with panthor driver), only after loading chromium and watching videos on youtube the latency raised a bit as you can see, but still very acceptable. Isolating all the fast cores improved that, but for me it's not worth it as it becomes noticeable slower.

For the rt-patch only a few had to be done manually for the serial 8250 driver because of some vendor edits.

Kernel/config
drive.google.com/drive/folders/1JglCIPKv...cjOvr?usp=drive_link

An easy way to install with gpu acceleration is to install the kernel on the image 6.1.75 with backported mesa from:
mirror.vinehost.net/armbian/dl/orangepi5/archive/
or
mirror.vinehost.net/armbian/dl/orangepi5-plus/archive/

Install the kernel with: sudo apt install ./linux*.deb
And link the Image file to the rt-kernel: cd boot; sudo ln -sf vmlinuz-6.1.75-rt23 Image

Where is the kernel source code for 6.1.75? I installed it and WiFi doesn't work. I plan to recompile it to turn on WiFi.

hello i get the following error when i run my ethercat configuration :

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.0~pre1+git20230208.f1270d6ed7
Machine configuration directory is '/home/precisonteq/linuxcnc/configs/KINS_2TILTS_COMPLETE_A_CASES/KINS'
Machine configuration file is 'cia402.ini'
INIFILE=/home/precisonteq/linuxcnc/configs/KINS_2TILTS_COMPLETE_A_CASES/KINS/cia402.ini
VERSION=1.1
check_config: Unchecked: [KINS]KINEMATICS=xyzab_tdr_kins
PARAMETER_FILE=xyzab-tdr.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=X Y Z A B
KINEMATICS=xyzab_tdr_kins
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./cia402.hal
Shutting down and cleaning up LinuxCNC...
*** xyzab_tdr_kins.comp setup ok
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
cia402: dlopen: /usr/lib/linuxcnc/modules/cia402.so: cannot open shared object file: No such file or directory
./cia402.hal:8: waitpid failed /usr/bin/rtapi_app cia402
./cia402.hal:8: /usr/bin/rtapi_app exited without becoming ready
./cia402.hal:8: insmod for cia402 failed, returned -1
46056
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

I installed the PyQt dev tools on this new 2.9.3 + bookworm PC and tried to open the *.ui file with the PyQt designer tool. It threw the same error. I can open this same ui file on my 2.8.3 + buster PC without any problems.
So something has changed in the toolchain that cannot deal with my "old" ui file.

In retrospect I should have started this tread in the PyQt section, but I cannot move it. If you are an admin, can you move it for me?

Yes, I considered that too, but that is a work around not really a nice solution. For instance I want my customers to be able to set a feedrate which makes sense, e.g. that is in the same order of magnitude as the actual expected cutting rate. However the incidental retracts need to be much faster.
The workaround approach would then be to set the desired feedrate two orders of magnitude greater that the expected feedrate, just to cope with the -1...1 limits of motion.adaptive-feed. Doable but not intuitive for my customers.
Also, setting the feedrate two orders of magnitude higher than the expected feedrate requires modifications to my feedrate control loop depending on the material and thickness. This would require an additional dail for my customers to tune, I do not want that. The simpler the better.
Up until now I managed with the -1...1 limits, but I think the control can be much better without them.

newbynobi post=89463 userid=3278Please find attached two files.
Just place both files in your config dir.

Than add the following lines to the [DISPLAY] section of your INI file.

EMBED_TAB_NAME = Spindle Button
EMBED_TAB_LOCATION = box_custom_4
EMBED_TAB_COMMAND = gladevcp -x {XID} -H spindle_button.hal spindle_button.glade


After starting your config you have spindle increase and decrease button.

Norbert

Hi,
I have resurrected this thread as it is just what I would like to have.
The respondent above provides the solution and clearly states what should go in the .ini file, but is not specific as to which configuration files should contain the lines provided in the two attached files.

He states:

"# just place                                                                                          
# - spindle_button.glade                                                                     
# - spindle_button.hal                                                                         
# in your config dir "

Where do these line go?

I presume the lines

"net increase spindle_button.btn_spindle_increase => halui.spindle.increase
net decrease spindle_button.btn_spindle_decrease => halui.spindle.decrease"

will be placed in the .hal file?

And lastly, where does the entire contents of the second file go?

I have attached a copy of the files referred to.
 

Many thanks for any help with this.
Dougal. 

File Attachment:

File Name: SpindleBut...0-13.txt
File Size:5 KB

Many thanks. Mesa through ethernet is clearly a much better solution as it will only require minimal wiring to a 37way breakout board to connect to my existing system. As I have a Pi 5 I will use that initially to set everything up and then consider the options. Out of interest what do you not like about the RPi?

Wenn ich für jede Achse einen eigenen Eingang definiere fährt die Achse auf den Endschalter und wieder zurück, in der Reihenfolge Z/X/Y. Nur über einen gemeinsamen Ausgang blockiert das Signal, sobald ein Endschalter aktiviert wird.

Hello,

Today I activated Kernel 6.1.0-11 Rt and immediately noticed something interesting that I hadn't paid any attention to before. My right mouse button, which I felt like I had to press for a long time before the context menu appeared, now works without any delays, Max Jitter is a good factor of 10 better.
Let's see what Qtdragon says about that.
I can't explain why the current kernel is so noticeable for me.

Best regards, Frank

I started ripping the electric apart yesterday. (damaged driver and Tommy tipped it)

• I do not really have any documentation for the brake out board and I wasted too much time with that thing already (fed up with it).
• One of the old stepper drivers is toast, considering how much the replacement costs it is not worth trying to investigate the pinout of a ribbon cable.
• Mesa 6i25 with a 7i76 plug and go kit is the way out. (in hindsight probably would have choosen one of the alternatives with network cable connection )

Plan for now:

• strip entire electric
• probably set the system up on the workbench to get the control running without mechanics.
• give the machine a (very) rough clean up. (if some motivation kicks in)
• See if I should replace the electric cabinet.

Hallo,

siehe hier meinen bescheidenen Beitrag

forum.linuxcnc.org/49-basic-configuratio...witches-on-one-input

Du musst die Achse wieder frei fahren, wenn du auf dem Schalter stehen bleibst, geht es logischerweise nicht weiter.

Viele Grüße Frank.

Thank you all. I finally got my servos working, but I'm stuck at implementing homing. I have read through the LCNC documentation on homing and more or less understand that part, but I don't get how to link that to the EtherCAT system, if I use the drive's internal homing mode, how do I select which mode to use? Or how do I configure external homing mode, I see that Rodw has made a cia402 home comp, how do I set that up?

My machine is a moving gantry machine with 2 y servos, all the servos have abs encoder. How should I implement homing on this machine? 

Ideally, I want the machine to be in a homed state and ready to use when LCNC starts and only need homing when the batter on the drives runs out by homing against a limit switch and then searching for the index signal (does that even work with 2 Y servo?). 

Edit: With Rodw cia402 home comp I was able to get the drive into a homing mode (showing 86ry) on the screen, but it does nothing.

While probing its also important to have predictable decceleration distances. Otherwise it is not easy to implement safety functions.

Im not sure where to place my thoughts. So maybe its wrong in this thread.

Best regards
Julian

Hello,

All my switches are connected in series as openers.

In the INI you have to assign a number for the pure sequence for the referencing for each axis "HOME_SEQUENCE = 0 for Z" and so on.
z-axis:
MIN_LIMIT = -202.0
MAX_LIMIT = 0.001
HOME_OFFSET = 3.000000
HOME_SEARCH_VEL = 30.000000
HOME_LATCH_VEL = 1.85
HOME_FINAL_VEL = -5.000000
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS = YES
HOME_SEQUENCE = 0
VOLATILE_HOME = 1

First important is Z so that the spindle doesn't scrape across the table.

And you have to make sure that the respective axis moves a little way away from the switch (move freely) otherwise the machine cannot recognize which signal is the next axis.

It gets a little more complicated with two drives per axis.

Best regards, Frank