Advanced Search

That's an error in the configuration utility, you can fix it by globally replacing
"inm" with "inmux" in the hal file.

Great info as always. Thank you.

Setting up inputs now, getting an error on startup again related to inputs.  It states input pins do not exist.  Is this a common problem? Did I miss a simple step on configuring the 7i97t?

It says I cannot reply to the hardware survey topic in the announcements category and I can see no obvious way to vote. Am I just missing something?

Try in MDI:
M6 T1
M6 T4
etc.

LinuxCNC supports a wide range of hardware, including a number of obsolete ISA cards etc. 
In order to prioritise maintenance of the drivers (and possibly to retire some drivers) it would be useful to know what hardware is out there "in the wild"

Please fill out the survey below selecting any hardware that you use yourself, or have recently seen in use.

(Edit) The poll only appears to allow a single selection, but I have enabled multiple votes per user, so it may be possible to add data for several hardware devices. 

Just to come up with something, doesn't necessarily mean it is practical
- set f-error-limit to a lot
- get feedback position
- fast forward to feedback position (servo off)
- reset f-error-lim and re-engage the servo
Maybe this can be done in a g-code macro.

I installed the homing, the remap for racktoolchange based on the example does not work for me, it throws out some errors, if there is someone more expert, I will send the files and errors so that he can establish it, the change system is very simple, I have 6 pockets, two outputs that I connected to the hal and which work in mdi, one for tightening and releasing the tool, the other for locking... I have on each pocket an input for the inductive sensor that the tool is in the pocket, I have positions where x0 and six of the y position of the tool and the change is works on z-120mm from G53. thanks in advance    (this is when i try in mdi o<rack_change> call ....i changed pins in ini lock=1 flush i changed to clamp=0 all the same
 

A picture might help.

Why do you need to use a manual handwheel?

Wouldn't it be possible to move the axis solely via CNC control?

What is "The following error"? You don't print any error message after that statement.

An idea:
You could connect a rotary encoder wheel and configure LinuxCNC so it behaves exactly like the handwheel, but drives the axis via the motors and CNC, without directly, physically moving the axis itself. It'll also save your shoulder from the strain of turning the handwheel and allow ultra-precise movement too.

I'm sure that the functionality you describe is possible, but I'm sure there must be some easier workaround for this problem.

Cartesian axes:
Refer to movement of tool
Standing in usual operator position, e.g. in front of machine


For vertical machine centre
X+ tool moves from left to right
Y+ tool moves away from operator
Z is axis inline with spindle rotation. Z+ is moving up
(just like an x,y,z 3D graph)

Z is always inline with spindle, so axes naming is "different" for a horizontal machining centre or grinder.

I did a reeinstall removed the raspi part like hakan suggested and everything worked. I will try to connect my ethercat devices tomorrow
Thanks

My DMU50 looks kind of like this. That model is at least quite common i think.
 


Here's a fancy sales video of a 'newer' version of mine:  DMU 50 3rd. Generation

Sorry, this is a Button at the Probe Basic GUI

 

Furthere more where can i decrease the "G0" speed? 

 

Was ist "go home" ?
A button on the GUI?
Probably by editing that button from G53 to G54 Fxxxx ...

Hello,

today I did the steps from tommy`s link.
At the end i played around with the P and FF1.
After arount 50 different tests, slowly the hard errors dissapeared and at the end i found the best working configuration with P=15 and FF1 =1

So I configured this parameter on all 3 Axes and it works.
Only one last problem is the speed for "Go To Home"
Is ther a info where i can find the different settings for all moves?
Jogging Speed is OK and i can change ist via the GUI.
Homing Speed is also OK, but "Go Home" is far to fast.

Best regards
Jens 

Here is my config (with working Linear-Encoders​ & Closed Loop Stepper)
 
  ​​​​​​

Assuming it has analog servo drives and those work, you would need an analog Mesa card, preferably Mesa 7i97T as it has analog outputs and encoder inputs all on one card, and a few I/O for limits and relays.
It is an ethernet board, and there is no practical difference between PCI/PCI-E/ETH cards except ETH cards can be mounted wherever is suitable on the machine as the LAN cable can be quite long, while DB25 cables are limited to about 1.5m (there are 3m and 5m ones but will have to be very good quality to work).
-
The Maho should (or should not?) have some EXE boards that translate the signal from motor feedback to encoder pulses that Mesa can use. This is what i've learned fro reading here on the forum, i do not have a Maho.