Advanced Search

There are pins to change jog speed using counts (eg for encoder) and for using analog value (eg for potentiometer):
linuxcnc.org/docs/html/gui/gmoccapy.html...cities_and_overrides

I'm trying to execute an M100 from this toolchange subroutine, whithout M100 works. Here is the M100 and it works in MDI, what can cause the hang? 

#!/bin/bash
# M100 Orient Spindle (Homing function)
halcmd sets s-index-zero-for-ATC true
exit 0

 
 

Thank you Andy, but I can not gain access to the X-Motor or spindle- probably to the Z spindle and move the Z-axis, I will try. So jogging the X-axis slowly must do the job.
Sigi

Alex, try
nn being the number you want to set. There is also an upload. Sometimes it is better to do it outside of linuxcnc.
Check for SDO index:subindex using $ "ethercat -p 2 sdos"

Max, did you try to claim it with "AliExpress Seller Protection"?

Philip, the manual says it can be done see snippet here
 
You should be able to add PDO 0x60ff to the SyncManager listing in the config, I think.
0x60ff is also in rxpdo 1703,1704,1705 so one of them should work. I guess.

Glad it's all working now.

To change isolcpus you edit /etc/default/grub as root

Something like:

xed admin:///etc/default/grub

 or

sudo xed /etc/default/grub

and then in the grub file change this line

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

To something like:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash isolcpus=3 idle=poll"

(3 assuming you have a 4 core CPU)

When you have saved your changes, you run:

sudo update-grub

and then reboot

Also with RealTek MACs it's likely that you will need to replace the normal RealTek
Ethernet driver with the DKMS version (search the forum for DKMS)

One additional step to improve Ethernet latency is to pin the Ethernet interrupt
to the last (real-time) CPU

To get an idea of Ethernet latency, you can run this command:

sudo chrt 99 ping -i .001 -q -c 60000 (card_ip_address)

This will run for 1 minute and then print statistics
 (card_ip_address) is the motions control cards IP address





 

Hello, thank you for everything!!! Everything works, I would never have found the solution without your help. Milko

In pncconf this is set in the "Spindle Motor" page
in the "Range 1 Max RPM" and "Max Output" spinboxes
 

Output of the command
will be a great starting point, maybe it even works right away.

Is this a 16 IN/OUT module? Then set the halType to "bit" for IN and OUT
and it will automatically generate 16 boolean pins. Check in halshow,
navigate to pins, lcec, 0 and so on.

Hello,
To change the speed when using jog, you need to stop the movement and start the movement again. Is there a solution for this? I am using the gmoccapy interface.

Hi, I'm making a robot arm using linuxcnc.
I have a python interface that i'm playing with. I send the robot commands by setting the axis.L.eoffset-counts pins and the robot moves as expected.
I have a function that polls the robot for its position and waits until it reaches the desired position before sending the next point.
The position is read using the python interface 

but every now and then, the robot reaches its position and waits there for another few seconds before the function exits. I realized that the position feedback gets stuck at some value, and my console prints
I also tried reading the position through the halui.axis.L.pos-relative but the same issue happens.
I assume this is because the internal emcStatus buffer doesn't get updated for those 5 seconds of the main loop.

Why does the loop take so long? How can I debug that?

Good day Forum
Have a question on point scanning and data file creation. I'd like to scan a part log the xyz coordinates, compare them based on simple math , then adjust the g-code trajectory based on the lowest value of the scan. any suggestion ?

Kindly
 

unknown wrote:

Have you checked for backlash with a Dial Indicator, as opposed to a dial test indicator which can be difficult to setup to negate any cosine error. T me this sounds like a backlash/leadscrew related issue.
Many times an similar issue has come up similar to this, even tho the user had checked the mechanical side, it turns out upon closer inspection it is indeed a mechanical issue. Coil type couplers aren't worth much as they can wind up. Don't rely on the stepper motor to provide any fixed bearing support (as many 3d printers and cheap chinese mills do), use angular contact bearings, the non driven end of a leadscrew should be able to "float" laterally to allow for thermal expansion.
Even ballscrews have backlash, unless you are paying alot and I mean alot for ballsrews expect some backlash.
Missing steps could also be a cause. But if I were a betting man I would put a wager on a mechanical issue. The thing regarding mechanical issues is they can add up, a little here and little there and another bit there can end up as a nightmare.

Here's a document far more eloquent than I could describe.
rick.sparber.org/mt.pd

I am almost certain that this is not a mechanical issue. The fixed and floating bearing design for the ballscrews is what my machine has. I also don't use coil couplers. Not sure what the right english word is, but blieve mine are called spider couplers. But you are right, I first thought it was a mechanical error or broken cable, but when I started narrowing down the error I am more and more convinced that it's something in the machine set up. Ferror, Fmin, Deadband,... something in there... I think. 
 

Hallo zusammen, 

hier (PDF im Anhang) meine Übersicht zur Verkabelung der 7i96s mit den beliebten JMC Servos / Steppern. Ich habe die Übersicht primär für meine Maschine erstellt möchte diese aber hiermit auch anderen Anfängern zur Verfügung stellen.

Die Spindel habe ich noch nicht eingetragen da meine aktuelle Elte Spindel über einen festen Poti verfügt.
Hierzu gibt es aber ein ausführliches Video von Talla83 

Falls jemand Fehler im Schaltplan findet oder Verbesserungsvorschläge hat diese gerne hier ins Forum stellen. Ich werde die Grafik dann entsprechend anpassen.

Grüße und viel Erfolg
Erwin 

I am using LinuxCNC Rio. The machine came from a parallel port, but it's converted. I don't think it has anything to do with Rio, I think it's some sort of configuration error in the ini file. It is all much to repeatable for a mechanical issue.