Advanced Search

yes switch will be necessary but my pain was that mixing stuff ... and therefore I erase all switches out to separation possible cases of mixing...

I will try and let you know

thanks

The ? would always be Y. I havent worked on these for a while, but generally, axes stay the same when shifting between lathe and mill on mazaks, but geometry switches between diametral/radial.

Fun project! Integrex's are great machines!

Bonjour,

J'ai câblé un switch sur le pin d'entrée n° 11 de ma carte d'axes.
Je voudrais exploiter cette entrée dans un programme avec la condition if.

Comment faire pour affecter cette entrée à une variable utilisateur, par exemple 40 ?

La ligne pour cette entrée dans le fichier hal :
net din-01  <= parport.0.pin-11-in
La ligne du programme avec if
o100 if [#40  EQ 1]

Merci d'avance

 

Excuse my crude model of the Integrex, but could someone tell me if my axis naming is correct for a lathe configuration?
And how is the axis called with the "?". Of Course for a Mill configuration it would change. Would be happy for input

Hi all!

I have been trying to get a Z compensation thingy working for a while. 

github.com/scottalford75/LinuxCNC-3D-Pri.../master/compensation

I have gotten the script working, in the way that it is incorporated in LinuxCNC, and it reads my probe data, sorta. I have two problems with it.

First problem: It doesnt read negative coordinates in X and Y. It only understands lower left corner being zero in the gcode. Which is a problem, since my machine zero is in center of worktable, and i make all my gcode with zero in center. I have worked like that for ages, and i dont feel like changing my workflow. 

Second problem: The outputed coordinates only work from machine zero. It doesnt follow if i have a work offset active. 

Has anyone had the same problems? This is over my skill level, and i cant get it to work.

I am attaching a number of files. Compensation.py is the script i am using now. probe-results.txt has only positive coordinates and works. probe-results2.txt has both negative and positive, and does not work. Or, it works for a while if i only move in positive area, but after a while the whole compensation just dies and i have to restart LinuxCNC. Z_level_compensation.py is a file i found in another thread here, that i believe morley(?) has modified. It is based on the script i am currently using, but it looks like work offset has been fixed. I have not gotten this script to work on my system, but maybe someone can tell me how to fix my problems based on that. 


 

tommylight wrote:

Usually omitting or deleting lines with HOME_...._velocity in the ini file and editing the homing and limit lines in hal is all it takes,

It's usual to retain the lines, but set the two velocities to zero. Omitting probably works too (they will default to zero) but actively setting to zero looks less like a mistake. 
 

endian wrote:

I have not using any kind of global variables 

I think you are, look at line 159:

mode_selection is a static global in the code. 

I don't know for sure if that is enough to cause the problem? 

it looks like mode_selection should be a local variable (actually, make it a parameter so that you can debug using it)

Also maybe consider using a "switch" command on mode_selection rather than repeated "if (mode_selection == ##) "

timo wrote:

 because I might have damaged a drive or two without beeing aware of the importance of the wiring.

 
A cage-clamp terminal done up nice and tight with the cable not actually inside the clamp is a popular way to blow up a drive. Give the wires a good tug after tightening the clamps.

Kieran wrote:

How's the rigidity of the harmonic drive? 

It seems OK. The HD website quotes values for torsional stiffness, but to be honest I don't know what value would be appropriate for a milling machine, so the numbers aren't useful to me. 

But I frequently use it just as a handy way to mount round stock and have noticed no issues. 
 

Here's an example:

 

It's a bit tricky because you do need to use muxed encoders for all
encoders (because the 7I89 uses physically muxed encoders)

 

Does this help at all?
wiki.linuxcnc.org/uploads/orient.svg
It's one potential way to do it.

Probably .hal and .comp which is overflowing

Excuse me for mess in the component but it is in the working session ...

I am sorry

I will enumerate all hard code and

Is has behaviour as I described higher ... I am confused and I have feeling like something in the working session is mixing together but no way to find it out...

Please let me know what I am doing wrong

thanks
regards E..

My experience is limited, but typicaly getting from a scan to a usable model is the hard part. I would ask for a demo with a sample component and be sure it goes all the way to the point that you expet to use the scan.

Thank you that's a good idea, by coincidence i already started making myself familiar with vismach, cause i really don't wanna crash the machine. I try to start as soon as possible an make a crude 3D model of the machine to import it into vismach. But i still need to figure out how to do the virtual Y axis compound move. I think i need to paint a picture of the axis configuration of the machine to post it here. Cause i have a few questions in regards of the axis/joint names.

I spent a few hours yesterday evening in the workshop of a user who has duplicated the Marco Reps controller configuration, with an Rpi5 and Leadshine EL8 (as detailed here: github.com/marcoreps/linuxcnc_leadshine_EL8 ) 

The cia402 component is seeing an enable signal, and the cia-controlword into lcec is setting to 6. But nothing seems to be happening in the drives, and there is no position feedback when turning a motor shaft. 
cia402.opmode is showing zero, and that leads me to think that stat_voltage_enabled is zeroSo possibly no data is being seen from the drives?
command-line ethercat commands list 7 devices (all in pre-op) and the lcec component also lists 7 devices, so _some_ comms is happpening. 

It feels like some sort of drive-enable isn't happening? 

Any thoughts? I felt a bit foolish turning up as an "expert" and then being completely baffled. (first contact with EtherCAT)