Advanced Search

I just did and the script was ran successfully thank you.

however. I still get the same error message with apt ethercat and the mokutil --import


edit: I just rebooted and everything went through to the end, my modules are visible

thanks a lot for your quick support

Did you make the script executable?

I'm trying to learn and here's the summary
Information about Name Data type in Obj Direction Data type EEPROM Generator Associated function Description

IndexLatchEnable  uint8_t        UNSIGNED8       cb_set_outputs() Enable or disable Index Pulse latch
EncPos                 double         REAL32             cb_get_inputs() + MyEncoder.currentPos() Current position of the Encoder
EncFrequency       double         REAL32             cb_get_inputs() + MyEncoder.frequency() Frequency of the Encoder
IndexStatus          uint8_t         UNSIGNED8      cb_get_inputs() + MyEncoder.indexHappened() Status of the Index Pulse
IndexByte             uint8_t        UNSIGNED8       cb_get_inputs() + MyEncoder.getIndexState() Status of the Index
Velocity                double         REAL32             cb_get_inputs() Speed ​​of the system (calculated from the Encoder or other data)

I'm familiar with the orient function.
After receiving your explanation, I'll go back to metalmusings_encoder.comp to double check the bindings with the GPT explanation.

Components and pins:

Component metalmusings_encoder: This component represents the encoder's function related to the index signal.
Index-c-enable pin (bit): This pin is used to control whether the index-enable signal is on or off.
Index-status pin (u32): This pin holds the status of the index signal, indicating whether the index is latched.
Index-latch-enable pin (u32): This pin is used to latch the index-enable state to synchronize it with the correct position.
Main function logic:
Initialization:

This causes index-latch-enable to follow the value of index_c_enable , if index_c_enable Set to true (high), index-latch-enable will be enabled.
When index_latch_enable is true:

If index_latch_enable is set to true (when index_c_enable is high), it checks whether index_status is true.
If index_status is true (i.e., a jitter occurs on the index signal), it resets index_c_enable to 0.

This means that when the index signal is detected, index_c_enable will be reset to prevent re-jittering.
When index_latch_enable is false:

If index_latch_enable is false (i.e., not synchronized), the system will wait for index_status to trigger index_c_enable to true.

This means that index_c_enable will be set based on the state of index_status and wait for a jitter from the index signal.
Overall behavior:
When index_c_enable is true:
The system checks index_status. If index_status is true (i.e. the index is latched), index_c_enable is set to 0 to prevent re-latching.
When index_c_enable is false:
The system waits for index_status to be true to trigger index_c_enable again, which causes synchronization when the index signal is latched.

Summary:
This component handles the index-enable signal by varying the value of index_c_enable depending on the state of index_status. It causes position synchronization to occur when the index signal is latched, and when index_latch_enable is set, the system resets index_c_enable after a latch from the index, which allows position synchronization to occur at the appropriate time.

 

Hello

Here is my source.list:

deb deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
deb-src deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware

deb deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
deb-src deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware

deb security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware
deb-src security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware

 
apt-get update and dry run:

sudo apt-get update
[sudo] password for paul:
... removed due to link limitation                 
Reading package lists... Done                      
paul@mill:~$ sudo apt-get install --dry-run ethercat-master
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package ethercat-master

my Download folder with the file ecat.sh but the error with command not found:

cd Downloads
paul@mill:~/Downloads$ ls
ecat.sh
paul@mill:~/Downloads$ sudo ./ecat.sh
sudo: ./ecat.sh: command not found
paul@mill:~/Downloads$ sudo ecat.sh
sudo: ecat.sh: command not found
paul@mill:~/Downloads$
 
 

OK thanks, I will go for Debian 12.

Yea your right. My old plasma table was like that I had the slats curved. Although I may still be able to curve the slats with 4 points of contact vs 3 I'm not sure how much I like the idea of super short slats. I figure they will get burnt up on a high amperage cut. It's possible in the future I may starter cutting 200 amp cuts over a inch of material thick. Today I got the table moved and started to clean up. Purchased new bearings man they are not cheap. Makes me second guess buying such a pos and not buying a complete working machine from a auction but here we are. I may reduce the thickness of the water table to 3/16 from 1/4 inch. Its about 7000 lbs of material which gets pricey. I kindof want the strength tho so it can handle getting banged up. I am going to order the parts list Tommy put together for the control tonight and try to get it to run on the original dc servos for now. I gutted the z axis the linear guides were super frozen up I got them to atleast move with only a few lbs of force on em. Tommorow more lubing and cleaning. I was looking at the original motors and the drives seems I do not have a plug for y axis encoders only for x axis into the box with all the drives. Tommorow i will post more pictures. Just want to make sure it's possible before I go down the route of trying to save the original motors.

OK, in that case you will have to monitor both commanded position and reported actual position to measure the time it takes, then try some tuning if the result is something reasonable.
Perfect would be no delay at all, but that never is the case.
In any case, you should absolutely remove the fedback from the drives, tune the drives to work properly with feedback from stepgens, only after you get that working, then switch to drive feedback and tune PID and FF1 values.

Hi Tommylight

I am only using EtherCAT drives.
No Mesa or parallel port.

yes the encoders are reporting back, but to the drive, and the drive is sending the following info back to LinuxCNC
"actual-position" and "actual-velocity"

LinuxCNC is then sending out to the drive
"target-position" and "target-velocity".

fixed the logo problem. Can you show your calculation?

If you set the 'isOnSensitive' property, then the button will be disabled until the machine is on.

The mist button uses the mist_action property.

Thanks for the tip. Unfortunately I got the same result, and with the values looking good.

Finn

Are you sure you are running a real time kernel?

What does:

uname -a

report?
 

How much "problem" is there? What type of machine? Even in CNC boring heads with a single point cutter are still "a thing".

Maybe your axis are not exactly perpendicular?

Can you measure it simehow?
I had huge backlash on my 2nd hand machine, the rubbers of the couplers between ball screw and coupler were "disappeared".
Another thing I found is a damaged bearing that keeps the ball screw in place. Then the complete screw can move a little.

Happy trouble shooting

I installed debian 12 and then linuxcnc using the sudo apt install method on a computer that used to run linuxcnc on debian 10.

The jitter numbers are huge, around 50,000,000 ns.  On debian 10 they were more like 50,000 ns.

What happened?