Advanced Search

I can see the poll results, but for the life of me can't see a way to vote.
Perhaps a screenshot may help some of us Luddites.

Not the best suggestion if the user wants to be able to upgrade to 2.9 or 2.10.

Unless a user specifically wants to use the parallel or has an ancient PC it may not be the best suggestion .
It would also be worth noting that Debian wheezy is end of life, updates haven't been available for a few years. Also wheezy had Python2 so the upgrade path for Linuxcnc is rather limited.
So when recommending the Debian Wheezy ISO it would be best to mention these facts.

That fixed it.  

Are there plans to develop pnnconf further for support for the 7i97t?  All the manual changes have been working great. 

You should be able to create  component that sets feedback = commanded pos when the handwheel is engaged. the cia402 component does this...

To replace the above, in the text editor hold down CTRL and press H, it will open two fields at the bottom, type inm in the top one and inmux on the bottom one, then click replace all, click save, do NOT close the text editor, first test and make sure the config works, then close.

Did you check above the post?
I kept looking ...

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
 

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