Advanced Search

Thanks for your help, I really appreciate it!

In the qt_auto_probe_tool.ngc script, I read the following:

The following workflow assumes using both a XYZ probe and a Z Toolsetter:
1 - Initial Setup: Before beginning the program, setup the Probe Tool as
having a zero z-offset in the tool table. (Non-zero tool lengths
for the probe tool can be made to work, but have multiple extra
steps required, and it is easy to have the tool offset interfere with
the remap coding and cause incorrect adjustments to your offsets.
This procedure assumes a zero length.)

It sounds as if the script documentation may be incorrect or perhaps previous codes changes have impacted the script?

Do you mean "G43 H99" ?? 
"G43.1" doesn't have an H parameter according to the online docs.

I have finally managed to get my 4 step/dir axis working, but still having trouble with the analog servo spindle drive. I get errors for addressing for the output
hm2_7i76e.0.7i77.0.1.analogout5 I have tried with .5. I have tried 7i77.0.2.
it keeps saying anything with that address doesn't exist,

  É possível conectar um codificador de alta frequência a esta placa nvem v5? para torno ou algo assim? orientação do fuso Não sei nada sobre esta placa

So I had some time to actually look at this:

#<_x>, #<_y>, #<_z> are relative positional values so your start position depends on whether you have g43 tool offset active or not.
The routine is set up to always return to the start position with G43 active so if your start position was stored in G49 then your spindle will always have to travel further up by the measured tool offset then where it started. This is why you are getting limit violation errors.

Just calling G43 is not the right way to go about it. If you have no tool set then the offset will just be zero and you'll be no better off.
Basically you need to start out by setting up your probe length in the tool table (ie Z offset for tool #99) and then do 'T99 M6 G43'  or, if your probe length has to be measured after each startup, you may want to use 'G43.1 H...'
linuxcnc.org/docs/html/gcode/g-code.html#gcode:g43

So really the same the others have already pointed out but it has taken me a long time to catch on.

Can you try in BIOS setting the PCI-E mode to GEN1 for that slot?

Last post is with sudo, the previous was not as can be seen by "permission denied" for capabilities.
Did you try setting the address and running LinuxCNC?

yeah, the big issue is generating tool paths. I have been working on it and I feel like I might have gotten somewhere with it.  It would be nice if there was a way to upload the lobe geometery and then pick the camshaft lobe arrangement by engine type and then hit grind. That's more of a UI side issue i suspect. 

Unfortunately, pin 8 is a disable input rather than an enable input so the
polarity of the 7I77 enable outputs are wrong (off until enabled). It may require
a relay with a NC contact driven by say a 7I77 digital output as drive enable.
(I think one relay will work for all axis by connecting all pin 8's together)
 

Hello Endian,after a lot of atempts, I am still not able to work with the servostar drives via profibus. I think I incorporated all of your hints (use of legacy mapping, sdo stuff) but unfortunately I does not work.Please, have a look. Thanks in advance, Franz

I was just able to fix the problem i wrote the wrong ip adress 10.10.10.11 .

Thanks for the reply anyway !

Sounds like possibly an IP address issue

What IP address did you select in pncconf and what IP address is set on the host?

ip a

will report the host IP address's

Yes, correct. 
Would adding a G43 to this make a difference? 
RS274NGC_STARTUP_CODE = G17 G21 G40 G80 G90 G94 G54 G97 G64 P0.025 S5000

I haven not seen this kind of issue but sometimes, motherboards with x4/x8/x16 slots
won't work with a X1 card. Also make sure that the 6I24 is jumpered for 33 Mhz clock
(and all jumpers match the default jumper positions in the manual page 4.

Hello !
I have a problem with setting up linux cnc i go thru pconf and when i want to run my configuration a get the next error message.
Debug file information:
Note: Using POSIX realtime
hm2_eth: rtapi_app_main: Connection refused (-111)
./deckel.hal:9: waitpid failed /usr/bin/rtapi_app hm2_eth
./deckel.hal:9: /usr/bin/rtapi_app exited without becoming ready
./deckel.hal:9: insmod for hm2_eth failed, returned -1
2097
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

Hole operations using parameters set from the GUI in subroutines.



JT