Advanced Search

snowgoer540 wrote:

This sounds like an autorepeat issue I've experienced in the past.

To test if it is, open a terminal window, and enter the following command:

xset -r

Launch LinuxCNC and jog around. If the problem goes away, that's the issue and we can come up with a more permanent solution.

To turn autorepeat back on:

xset r

Did this yield any results yet?

Use the software Tommy linked to to burn the ISO to a USB stick.
check the BIOS is set up to allow booting from USB
Disable UEFI/Secure boot while you are there.
Plug the USB in and boot your PC which should load the installer from the USB

Error finishing read means that the time to read the Mesa card did not finish before the end of the servo thread cycle.
Usually, this will disable the Mesa card until reset or restarted.
Follow these steps. 
1. Uninstall Ethercat just in case (but could do this as the last step if required)
2. if you have a Realtek NIC, install the correct Realtek driver r8168-dkms or r8125-dkms
4. If Intel NIC, disable coalescing. type man hm2_eth and follow the instructions adjusting for your Mesa ip address
5. Set isolcpus = your_last_core in the grub parameters. The LinuxCNC ISO install grub_customizer to make this easy (sudo grub_customizer)
6. Set the CPU affinity on the IRQ used for the Ethernet NIC to be your_last_core (same as isolcpus)
7, disable EEE (energy efficient Ethernet)
8 set the governor to performance

Some of these settings don't persist on a reboot so you'd need to run a script on startup to lock them in 

der Fehler kommt erst, wenn ich auf ausführen klicke.

Der 'Ausführen' button ist in deinem Fall nicht von Belang. Der ist dazu da Hal-Commands, die in die Zeile daneben eingegeben werden, auszuführen.

]Wenn ich die Endschalter drücke, ändern sie nicht die Anzeige,

Solange die Pins der Referenzsignale sich nicht ändern wenn du die Schalter drückst kann das Refernzfahren nicht funktionieren.

Wenn nun plötzlich keiner der Schalter mehr zu einer Veränderung in der Halshow führt, dann würde ich stark vermuten, dass der Fehler in der Verkabelung oder der Elektronik (zb Mesakarte) zu suchen ist.
Also mal gucken ob sich an der Karte die Spannung am entsprechenden Eingang ändert wenn du die Referenzschalter drückst.

Hallo,

der Fehler kommt erst, wenn ich auf ausführen klicke.
Wenn ich die Endschalter drücke, ändern sie nicht die Anzeige,
was vorher der Fall war, als noch alles funtioniert hat.
Vielen Dank für deine Bemühungen
Karlhe

Thank you. I have the axis.viismach 5 axis working as a simulator. Still getting the additional vismach machine running, but the axis view is fine for what I'm doing (4th axis positioning). gmoccappy looks to be for touch screens? The QtDragon sure has a nice clean presentation. But I'm so used to the axis screen, from working in the shop, I'll probably leave the simulator an axis based version for now.

Thank you again. What a great forum.

Beside what Aciera and you already found, there are several under Vismach section of Axis GUI, gmoccappy and QtDragon have some for 4 and/or 5 axis, WoodPecker also has some.
And, Vismach also shows a machine working in 3D.

etcher.balena.io/

Pushed.
Thank you!

I am trying to  install the Trixie/Debian/linux cnc  image that RodW recommends. Can't seem to find the right steps. I have the mesa cards, 
HP core I5 computer with 16 gigs of ram and 1 tb hard drive.  I have been using computers for a long time but I can't seem to make any progress
doing this install. Suggestions?  Any help will be much appreciated. I have had the Plug and Go kit for a few years and would like to get it working for the control of an engraving machine I am building.  Thanks Jeff

Hi if someone could explain or give a link how to measure tool length using a ER20 and tool setter for first time to enter the length in the tool library , tool setter working using Flexgui with M6 remap working if there is a gcode example someone could show me ?

Thanks Fred 

Hi Cmorley

For a while now, the 50/100 "max velocity override" buttons and the slider haven't been working. It turned out the connections (signals/slots) had disappeared. I fixed the problem and also tweaked some minor things. The red LEDs in the two axis buttons were red instead of pink, like the other buttons. I removed the blank pages on the 4th and 5th axis buttons.

After much frustration, I finally have the gladevcp working with GMOCCAPY. All of the features I wanted to implement are working almost as expected.

At this point I find that when I activate the laser pointer from the gladevcp panel, then jogging is blocked regardless of which tab is currently active. It appears that when the toggle is active, it blocks all other functionality of LCNC. Once the toggle is deactivated, all features return to normal. Does anyone have insight regarding this issue?

Also, I googled how to close a floating vcp panel during shutdown and implementing a python handler for the GtkWidget "destroy" signal did not appear to work. Does anyone have an python example for implementation of the "destroy" signal in a gladevcp panel or have an example of how to close a vcp panel on shutdown?

Tommy: I finally found one as "sim.axis.wrapped-rotary". If you, or others, know of more I'd like to hear of them. But you're not missing anything I see, it's more my search skills that are missing.

Aciera's comment regarding adding a "!" to [DISPLAY] GEOMETRY line implements a rotary axis over a tilting spindle motion. That seems to be the missing link to get "axis" working for my implementation.

Thank you.

YES. I finally found a simulation model, sim.axis.wrapped-rotary, using XYZA. I added the line GEOMETRY = !AXYZ to [DISPLAY] and the axis display acts as it should for a rotary table on A. The "!" did the trick.

I loaded the vismach axis sim model. The axis display has the same problem as above, I'll try the "!" fix which I expect will also work here. The vismach display does function as I expected, moving part with table(s).

These should work for me. Thank you very much for the help. I will have to change units to inches and the envelope size of the machine before my code(s) will run. Also figure out how these simulations implement tool offsets. But thanks to you I see a light at the end of the tunnel.

THANK YOU!