Advanced Search

It would be about the same, but you would likely need to add 
some additional I/O cards for general purpose inputs and outputs.
(that are built in on the the 7I95T)

when this is done, this will be a huge optorunity for linuxcnc , how much of this code should be upstreamed to linuxcnc ?

i have realized a mixer for fluids with linuxcnc (linear axis and servos)

i have a question:

the mixer needs to be go up and down a certain time. i tried to use the time module, but everytime i try to use the calculated value in the while clause linuxcnc stops loading or hangs on realoding the program

#<z_mischen_start> = [#<_hal[time.0.minutes]> * 60 + #<_hal[time.0.seconds]>]

G97 S800 M03
o101 do
    #<z_mischen_elapsed> = [[#<_hal[time.0.minutes]> * 60 + #<_hal[time.0.seconds]>] - #<z_mischen_start>]
    G1 X270 F1000
    G1 X250 F1000
o101 while [#<z_mischen_elapsed> LT 4]

any ideas? i'm quite new to linuxcnc ....

thanks a lot !!!

Lars

Chris,

I'll fire up the mill later tonight and get a config dump for you.  And yes, I'm using a step/dir non-axis output to drive the ATC stepper.

Once you've had a look - it's complicated - I'll walk you through any of the atc-specific stuff that isn't clear.

Agree - the tool DB would be nice.  There are a number of features I'd really like to have that could be automated via a DB value:

• lathe front tool/back-tool backplot flips
• lathe main/sub spindle backplot flips
• multiple offsets for a multi-function tool like Siemens does
• Max RPM
• "Big" or 'Heavy" tools for carousels (nothing allowed next to oversized tools, or slow down carousel for high inertia)

If you are having SDO write failures you may need to disable EoE by rebuilding the IgH master from source. If you search the forum for "disable eoe" there are several post about it and what flags are needed to build from source without EoE.

Sorry to bother you some more. I happen to have a ton of cards I bought years ago lying around. Do you think a better solution might be a 7i80hd-25, use a 7i52s configured for 6x PWM output and 6 encoder inputs (only using 3 of each for now). I have a 7i44 and multiple input/output card options.

Your problem is caused by screw backlash

Typically this happens if you try to install Linuxcnc without an internet connection.
Always connect to the internet when installing the linuxcnc ISO

When you downloaded the script, you did not edit the file name to remove the .txt ending
It told you it could not find the file, ls would list the files

I think it will be difficult to meet all dependencies on Debian 10. Upgrade to Debian 12 Bookworm

Hi Tommy,

Yes, python related.

PyConfig_InitPythonConfig and PyConfig_SetString, are part of Python's new initialization APIs introduced in Python 3.8.

Try:
sudo apt-get update
sudo apt-get install python3 python3-dev python3-pip python3-venv

Hi,

Looks your sources.list is not ok.

$ sudo thunar

Then find and edit the ~/etc/apt/sources.list

# Fetch sources list.
$ sudo apt get update
# Check if source excists:
$ sudo apt-get install --dry-run ethercat-master

 

I have a problem when making round cavities or holes. In the axes corresponding to the angles 0 -180 and 90 -270 the dimensions are correct, but in the diagonals the dimensions are no longer correct, in the diagonal 45-225 the dimension is smaller and in the diagonal 135-315 the dimension is larger.

Hi Collins,

Today was a good day for coding. This morning still had a crash problem for the interpreter.
For the colors of the code i thought, RGB, red, green, blue.

Now the super imposed interpreter is running ok.

Added the realtime environment : base-thread & servo thread is loaded and running.

The servo-thread has now 3 motion components running. This is really cool.

libmotion_0.so -> produces motion for main interpreter (red)
libmotion_1.so -> produces motion for sub_0 interpreter (green)
libmotion_2.so -> produces motion for sub_1 interpreter (blue)

The idea is then to send the interpreter's gcode output to the motion components over the 1ms thread.
We do this over shared_memory.

Then we have to code the motion components. They will use the scurve and toolpath optimalisation as seen before.

The base thread has the libethercat.so component running soon.   This has ethercat auto configuration.

This is going to be a cool winter project.

There are a few questions, like what if sub_0 interpreter is a tool changer. The green tool cone is then not valid.
Depending on the machine configuration, the green and or blue cone must be replaced by something else?

codeberg.org/skynet/realtime_app/src/branch/master

I'll try to explain how the spindle-index-enable works.
This is the traditional syntax in hal to enable synchronization on index signal
linuxcnc.org/docs/html/examples/spindle...._synchronized_motion

net spindle-index-enable encoder.3.index-enable => spindle.0.index-enable

First look at what motion.spindle.M.index-enable says

spindle.M.index-enable I/O BIT
For correct operation of spindle synchronized moves,
this signal must be hooked to the index-enable pin
of the spindle encoder.

Then look at what the encoder's index-enable pin says
linuxcnc.org/docs/html/man/man9/encoder.9.html

encoder.N.index-enable bit i/o
When true, counts and position are reset to zero on the
next rising edge of Phase-Z. At the same time, index-enable
is reset to zero to indicate that the rising edge has occurred.

These three lines say a lot. This is the behavior the EtherCAT client tries to replicate.
index-enable is a I/O bit, that means read AND write variable. As mentioned, EtherCAT variables
are read OR write. The metalmusings_encoder component split index-enable in two variables
one read variable that forwards the value to the EtherCAT client, and one write variable
that when set will change index-enable, as specified above.

In the EaserCAT 3000 client, when Obj.IndexLatchEnable is set, i.e. when index-enable is set, it waits for the next Z-index interrupt, which then then zeroes the counters. This needs to be done exactly when the Z index happens, not any time afterwards. Because this happens in an ISR it communicates to the rest of EaserCAT with indexPulseFired variable. So in cb_get_inputs() when setting whether the index fired it will know that from this variable.
It is pretty indirect programming, but that is how I have been taught to communicate with ISRs.
Then it will set Obj.IndexHappened, which will go the the metalmusings_encoder component whioch will reset the i/o variable.

Not sure this clears things up, not so easy to write a good clear answer to this.