Advanced Search

if you want to try i added dedicated hal pin to the spindle encoder index, you can connect it to any input pin, and you can define in the config.h and also set the active level of the signal to active low or active high.

If the original manufacturer thought that is was important enough not to require homing to go to the trouble of fitting potentimeters I would be inclined to follow their lead.
I don't think it's a difficult thing to integrate.

I see you have two slaves with idx="0", that won't work.
List the indexes with "ethercat slaves"

There is another debug option or possibility. The output of "sudo dmesg" show a lot, at the end it may have info that can show the error.
Especially info messages from ethercat master and lcec goes there.

Good morning, I want to update my Qtplasma and would like to know if there is a step-by-step guide for doing so. Thank you.

QtPlasmaC updates - master (submitted by phillc54):

• start conversational shapes at origin
• uppercase conversational gcode
• make documentation and example g-code file references to adaptive feed consistant
• conversational block refactor
  • Allows run from line in conversational blocks.
  • All conversational work is in native machine units.
  • Adds interlocking for conversational shape buttons.
  • Renames column and row offset to spacing.
  • Sets default distance for column and row spacing.
  • Existing conversational shape files will be automatically upgraded when loaded.

You`re right. When I realized that it is a special customized Version I started everything all over again to go with the simplest version. I did what you proposed and compiled the cia402_homecomp. Than I mixed my working Beckhoff starting point files with the ones from dbraun. Unfortunately it still crashes:

wopass: load_the_modules cmd=<orig_loadrt lcec>
waitpid failed /usr/bin/rtapi_app lcec
/usr/bin/rtapi_app exited without becoming ready
insmod for lcec failed, returned -1

Shutting down and cleaning up LinuxCNC...
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
motion.c: Creating unlock hal pins for joint 4
LinuxCNC Ethercat crashed with signal 11
-- STACK TRACE START
0 /usr/lib/linuxcnc/modules/lcec.so(+0xfc8c) [0x7fc1af3e9c8c]
1 /lib/x86_64-linux-gnu/libc.so.6(+0x3c050) [0x7fc1b0303050]
2 /lib/x86_64-linux-gnu/libethercat.so.1(ecrt_slave_config_pdos+0x2f) [0x7fc1af3ad52f]
3 /usr/lib/linuxcnc/modules/lcec.so(rtapi_app_main+0x40a) [0x7fc1af3eaf38]
4 /usr/bin/rtapi_app(+0x10cd7) [0x56167d468cd7]
5 /usr/bin/rtapi_app(+0x1162e) [0x56167d46962e]
6 /usr/bin/rtapi_app(+0x11c2c) [0x56167d469c2c]
7 /usr/bin/rtapi_app(+0xc974) [0x56167d464974]
8 /usr/bin/rtapi_app(main+0x70f) [0x56167d46444f]
9 /lib/x86_64-linux-gnu/libc.so.6(+0x2724a) [0x7fc1b02ee24a]
10 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7fc1b02ee305]
11 /usr/bin/rtapi_app(_start+0x21) [0x56167d464861]
-- STACK TRACE END
Waiting for component 'cia402' to become ready.....Waited 3 seconds for master. giving up.
.Note: Using POSIX realtime

2971
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
lcec: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
motmod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
trivkins: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
homemod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
Note: Using POSIX realtime
tpmod: not loaded
<commandline>:0: exit value: 255
<commandline>:0: rmmod failed, returned -1
<commandline>:0: unloadrt failed
Note: Using POSIX realtime

Do you have any Idea what to try next?

Please disregard my last question!

I was overthinking this and glazed over the simple method that was right before my eyes.

As my question
Usually, no matter what system it is, the planner starts with speed 0 in planning.
However, in some cases, in order to improve work efficiency, if the motor and drive allow, I can set the machine to start planning at a speed of 50 (we think the servo can run up)
So how do I need to set it up? Does linuxcnc support this setting?

Yes it is missing.
Maybe you already have fixed it by now. It's not a standard component so you need to "halcompile --compile cia402_homecomp.comp" to put the .so file in you config directory.
It's daring to try to get the servo working using a custom setup, I wouldn't do it. I would start with the simplest config possible from dbraun1981 and when that works I would build on with other functions.
But i understand this is part of a complete working setup, so you need to find the cia402_homecomp, compile it and hope for the best.

Thank you kindly PCW for your reply.

This might be a very stupid question, but how do I implement the link you provided into MesaCT?

Do Just download the last hostmot2.c and mesaflash.c files and swap them into the mesa flash-master folder?

Excuse my ignorance!

j

If you are using a standard 100 PPR MPG, it will count up by 4 every detent
with a standard quadrature counter. It looks like you are using the software
encoder, if so , try setting encoder.0.x4-mode false.

First Question.

For a 1mm jog, I originally set my MUX40.in1 to 1.0. This was resulting in an exact 4mm jog each count. To fix this I need to set the scale below to 0.25. While I can do this and get the result I want, it bothers me that I have to use a ratio instead of direct number and will be harder to decode at latter dates. It seem arbritary that each count would be 4mm exact.

setp mux4.0.in1 1 (jogs 4 mm per count)

setp mux4.0.in1 0.25 (Jogs 1 mm per count)

net encoder-counts  <= encoder.0.counts
net encoder-counts => axis.x.jog-counts

Question is, where is the actual jog value recorded in LinuxCNC.? I cold find nothing in the .ini or .hal files that seems to indicated it would jog exactly 4mm each jog count.



Second question,

Per the below, I am currently using mux4 to determine the jog scale. But my MPG switch does is not using an encoder switch but instead has 3 simple outputs of which I placed into input 26 (1x), 27(10x), 28(100x)

I got everything to work but can not find any details in .hal how to use something other than mux4 logic to place the correct scale into the axis jog. This seems like it should be simple. More or less just want if one of those pins are true, the correct scale is selected. Below is partial code referancing the scale portion. Note. Only using pins 26 and 27 at the moment due to the mux4 requirements. Other than this, everything is working fine.

# This sets the scale that will be used based on the input to the mux4
setp mux4.0.in0 0.025
setp mux4.0.in1 0.25
setp mux4.0.in2 2.5

# The inputs to the mux4 component
net scale1 mux4.0.sel0 <= hm2_7i76e.0.7i76.0.0.input-26
net scale2 mux4.0.sel1 <= hm2_7i76e.0.7i76.0.0.input-27

# The output from the mux4 is sent to each axis jog scale
net mpg-scale <= mux4.0.out
net mpg-scale => axis.x.jog-scale

---

Basically want:

if Pin 26 true then axis.x.jog-scale == 0.025
if pin 27 true then axis.x.jog-scale == 0.25
if pin 28 true then axis.x.jog-scale == 2.5

Note that as the schematic says, there's an even/odd swap
because the schematic is for the flat cable, (which plugs on to
the reverse side of the FT4232H),  _not_ the FT4232H

github.com/LinuxCNC/mesaflash/commits/master/

Currently 3.5.13

After further testing and focusing on the Z axis, it is related to the limit switch. If I Z+ to the limit, then re-zero the non-zero value increase (G54). Each time I bump up to the limit switch, the value increases. Strangely, the actual (G53) remains the same (within a few tenths)

Also, if I "power off", meaning use the power button of the UI, and then power the system again, I can then correctly zero the Z. Meaning if I then press the zero Z axis, it will then set to 0.