Advanced Search

This may explain things. 
control.com/technical-articles/a-look-in...-npn-and-pnp-sensor/
I'm not sure if your device can use negative and positive as a common.

Also have a look at some other ethercat documentation for wiring diagrams

Are you 100% sure this board is suitable for Linuxcnc.
If it's for an embedded application, I not sure if RPi s are certified for Industrial use, would be a better option, I'm sure it's suitable for ethercat.

Maybe 3rd time lucky replying.

1 Development tools & libraries to not appear to be install.
2 There seems to be a lot of x86 Linuxcnc binaries in the image.
3 Once Linuxcnc has been built, you will need the runtime libraries to suit, if these aren't available it will be a hard task (as these may require building from source)
There is a utility to convert deb packages to OPKG formats, so this maybe an option.

Unless there is a way to get a version of Debian arm installed it may be a very very hard battle. But Debian does support ARM64.

Here's some info:
forum.linuxcnc.org/9-installing-linuxcnc...parallel-port#303645

There is always the chance that lspci will show the card ports as "disabled", but it's usually the case that drivers aren't required and are aimed at the serial part of the chip, these chips have the ability to work as a serial port, parallel or SPI port (this I have seen as a reference design and not in the wild).

Linuxcnc doesn't use the kernel driver to talk to the parallel port card. It has it's own driver that talks directly to parallel. The only real call the the kernel driver is to ask for "exclusive" use of that port. Even if that call fails and the port address you give Linuxcnc does exist it will merrily go on its way.

As mention in my linked post there are a couple of methods to work out the port address.

I knew this topic would pop again in a week or 2 after starting that thread.

how?? i want to connect two pins from VFD ( spindle forward and reverse) and do you mean the common is the power input of the group ?

The outputs are probably NPN which means your load needs to go between  the output pin and ground and common will need to be +24V

Hi Grotius,
I have been trying to find out the physical meaning of curvature and how to imagin G2 continuity in higher dimensions. I have not been having much success in that endavour.
This recently published paper I have found claims to use splines for filleting in 5 axis: A Novel Local Smoothing Method for Five-Axis
Machining With Time-Synchronization
Feedrate Scheduling ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=9085380

I was hoping for some help to find some references on how to do filleting in higher dimensions to reduce the tangential jerk.

-automata

Im Still working away modifying the Hal file.

Went back to review RotarySMP's wonderful Maho thread and 90% of the answers i needed were right there in his HAL file.
I am stuck on a couple of points though.

I have copied the 2 sections below out of Mark's HAL and done what i thought were the required modifications.  The modified version of the code i found to suit the Deckel is half in german which is tough for a simple Aussie.

What files will these pins refer back to when opening linux CNC? at the moment unless i comment out like below it throws an error upon opening e.g. cant find pin FP4-gearbox.reducer-motor.
This will be due to a different naming syntax between the below and whatever file it references i would assume but i need to know what it is so i can modify correctly.


# --- GEARBOX CONTROL ---
#net sig_return_actual_speed     FP4-gearbox.spindle-speed-out   => motion.spindle-speed-in
#net sig_return_spindle-at-speed FP4-gearbox.spindle-at-speed    => motion.spindle-at-speed
#net sig_stop_spindle            FP4-gearbox.stop-spindle        => motion.spindle-on
#net set-gear-shift-start        FP4-gearbox.start-gear-shift    => hm2_5i25.0.7i84.0.2.output-05
#net activate-vorgelege_motor      FP4-gearbox.reducer-motor       => hm2_7i96s.0.7i84.0.0.output-00
#net activate-block2_motor      FP4-gearbox.midrange-motor      => hm2_7i96s.0.7i84.0.0.output-01
#net set-shaft-motor-lowspeed    FP4-gearbox.motor-lowspeed      => hm2_7i96s.0.7i84.0.0.output-03
#net activate-block1_motor  FP4-gearbox.input-stage-motor   => hm2_7i96s.0.7i84.0.0.output-02
net activate-spindle-twitch-cw  FP4-gearbox.twitch-cw           => hm2_7i96s.0.7i84.0.0.output-04
net activate-spindle-twitch-ccw FP4-gearbox.twitch-ccw          => hm2_7i96s.0.7i84.0.0.output-05

# --- GEARBOX CONTROL ---
#net sig_get_commanded_speed  FP4-gearbox.spindle-speed-in-abs    <= motion.spindle-speed-out-abs
#net sig_spindle_status       FP4-gearbox.spindle-stopped     <= hm2_5i25.0.7i84.0.2.input-19
#net sig_vorgelege_vorne        FP4-gearbox.reducer-front        <= hm2_7i96s.0.inm.00.input-02
#net sig_vorgelege_mitte        FP4-gearbox.reducer-center       <= hm2_7i96s.0.inm.00.input-03
#net sig_vorgelege_hinten       FP4-gearbox.reducer-back      <= hm2_7i96s.0.inm.00.input-04

#net sig_block2_vorne         FP4-gearbox.middle-front         <= hm2_7i96s.0.inm.00.input-05
#net sig_block2_mitte         FP4-gearbox.middle-center        <= hm2_7i96s.0.inm.00.input-06
#net sig_block2_hinten       FP4-gearbox.middle-back       <= hm2_7i96s.0.inm.00.input-07

#net sig_block1_vorne           FP4-gearbox.input-front         <= hm2_7i96s.0.inm.00.input-08
#net sig_block1_mitte          FP4-gearbox.input-center         <= hm2_7i96s.0.inm.00.input-09
#net sig_block1_hinten         FP4-gearbox.input-back       <= hm2_7i96s.0.inm.00.input-10

Thanks for being patient with me.

tommylight wrote:

Are the motors brushed DC or brushless, or steppers?
If brushed DC there are also "extreme limits" that also cut power to drives.

Well I’m getting rid of anything and everything VFD related here lol.  Its a 100% stepper system.  The drives are cheap all though the new spindle drive is pretty nice just is difficult to understand how to configure it and all.  I’m pretty sure the spindle drive has some kind of limits functionality that can be programed into it, maybe even an estop command can be sent to it.  As far the other drives they only take power and step/dir input.  

I’m staring to think go with kill all drive drives power including spindle drive but leave the control board running and also get it to receive the estop signal.

Also do you know of any good 220v relays that are din mountable that don’t hum loudly when they are on? 

Thanks

i bought this IO module and i have problem with the output ports, i am using out16,15,14 i connected 24V to power supply of this group ( second group ) and i connect my load to the pins and when i try to sent high signal the LED in the module turns on but there is no voltage on the output pin , when i measure the voltage its 0 on high signal and when low signal it gives about 7V

Bump as it seems it has been missed.

All drives that take step/dir or pulse/dir signals work with Mesa 7i96S and other Mesa boards, be it single ended or differential inputs as Mesa can do both.
And you can add a Mesa 7i85S to 7i96S and have 4 more stepper outputs, add a 7i84 and get 32 inputs and 16 outputs.
If you do add 7i85S, get also the required cable.
7i84 can be wired with a normal LAN cable cut in half.

In general, never ever switch of the DC side of things.
Leaving the controller on even on E-stop is a good advice as you can check what went wrong.
E-stop should kill power to drives and spindle, and must be considered as the last resort in case something goes wrong.
Are the motors brushed DC or brushless, or steppers?
If brushed DC there are also "extreme limits" that also cut power to drives.

For drivers with only one power input, I would kill the power input to each drive with estop.

Cutting power to control board only is not reliable way. What if stepper driver is faulty and runs away with no input? Need to cut power to the stepper driver.

Hi all
Not sure this is the right place to post my problem. So, moderators, feel free to move it to the correct place.

I have a small three axis router that has a tool length sensor sitting idle for the last few years. I want to make use of it. So digging up the forums, I came accross "examples/sample-configs/sim/axis/remap/manual-toolchange-with-tool-length-switch" to get familiar with it. This "sim" just worked on 2.8.4. runing debian buster.

I upgraded to bookworm and 2.9.2. Same "manual-toolchange-with-tool-length-switch" does not work anymore. OK, using gitzip, I downloaded the latest source from github , unpacked in a new directory and ran it again, to no avail. I positively verified that all files downloaded *ARE* really the same as on  github .

os: debian bookworm
LCNC: 2.9.2
user/group cnc:users
owner/group of manual-toolchange-with-tool-length-switch: cnc:users
when I run: "linuxcnc manualtoolchange.ini", I get the following errors (full messages attached)

• [GladeVCP.QTVCP.QT_ISTAT][WARNING]  INI Parsing Error, No DEFAULT_LINEAR_VELOCITY Entry in DISPLAY, Using: 25 (qt_istat.py:532)
  ... couple of similar warnings more
  Guess, as warning only ignorable
• [GladeVCP][DEBUG]  **** GLADE VCP INFO:    Not a builder project, trying to load as a lib glade project (gladevcp:205)
  Problem?
• gtk-builder-error-quark: manualtoolchange.ui:13:38 Invalid property: HAL_Table.n_rows (11)
  Problem?
• **** GLADE VCP ERROR:    With xml file: manualtoolchange.ui : 'gi.repository.Gtk' object has no attribute 'glade'
  Guess, that's where it fails?
• <commandline>:0: gladevcp exited without becoming ready
  Guess, my guess confirmed?
• Embeded tab command "halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -d -x 79691919 -u python/gladevcp-handler.py manualtoolchange.ui" exited with error: 1
  

How can I get this up and running again?
Any help greatly appreciated

greez chris