Advanced Search

I see what you mean about the tool touch off and that makes sense. I'll see about adding that in the morning.

JT

.002 motion from a 0.100 command is what you would expect
if you used 100000 as the step scale but the drive was set for
500000 steps/turn instead of 10000.

salue zusammen,
Ich bin gerade an den Probe Einstellungen per Taster und  3D Messtaster von der aktuellsten Version Probe Basic (Chris Polanski) auf LinuxCNC 2.9.3.
Nach einer 1:1 Kopie einer "metrischen Maschine" (alle Dateien) die grundsätzlich mit der Oberfläche von PB läuft habe ich auf der kopierten  Maschine  mit Touch Panel Oberfläche nur das "imperiale" System angezeigt.

Kann ich  die imperialen Anzeigen auf metrisch umstellen, und falls ja wo?
NB: Ich habe das China Handrad WHB048B-6 in der Maschine mit eingebunden  welches absolut funktioniert, aber die digitalen Anzeigen im metrischen System angezeigt werden.

herzlichen Dank für Euer Engagement
Claude

 

Those are terribly horrible results !
Was latency better before installing the DKMS drivers? Why and by who were you told to install DKMS?
If i recall correctly you had dropped link to Mesa board, but they were not from network issues, they were from huge latency issues, is this that topic?
Did you disable stuff in BIOS?
How much memory does the PC have?

Ok I tried the numbers suggested and I'm only getting .002" for a .100" request. I must have something in the driver itself thats not right.

tommylight wrote:

Use
latency-histogram --nobase --sbinsize 1000 --show
There are a lot of excursions out of the visible area.

first captured picture show immediate after running, the next one is after waiting for 1~2 minutes

Hi, there, I made a new configuration of my new machine. Nothing special: open-loop motors, ball-screws on Zaxis and Xaxis, dual helical rack and pining gear on Yaxis. I have used my previous HAL and INI that used to work fine with some modifications on a different machine but with similar hw. But the new machine is showing an error after couple of minutes after operating the machines.

command (EMC_JOG_CONT) cannot be executed until the machine is out of E-stop and turned on

I am running EMC2 on RPI5 4GB. I have attached my HAL and INI for better debugging. Does anyone know what could be the problem? I have never experienced this kind of error. Thank you very much in advance for your kind advices.

that is awesome, for some reason multi spindle swiss machine just popped into my head looking at that. I have been watching to many Tornos videos drooling lol

branch: using_os_path_join

 

the rio-setup gui is running directly on windows now
 

 Here screenshot of the plotter when I use Y and Y2 view. The reason why I want a label for each axis is that it is clearer and more transparent and I remember which axis I am working with. This Flex GUI uses Probe basic .qss
 
 

COFHAL wrote:

I am using the card designed by Hakan and it does not have a driver to make the differential encoder input. I have not tested the index yet, I have only tested the encoder with one that does not have an index pin. In the next few days I will try to test it with one that does have one.

OK.

I am using the card designed by Hakan and it does not have a driver to make the differential encoder input. I have not tested the index yet, I have only tested the encoder with one that does not have an index pin. In the next few days I will try to test it with one that does have one.

Do you have LATHE = 1 in the [DISPLAY] section?

I'm looking into why the plotter does not show the correct view for a lathe like Axis does.

The Diameter/Radius checkbox works with LATHE = 1.

JT

What Linux version?
What RT kernel?
Does
sudo lspci -v
Show the wifi card?
Any way you look at it, get a USB WiFi dongle, built in WiFi is PCI-E so can cause big latency issues when in use.
If you still want to use it, might have to install the latest RT kernel available for whatever your Linux version is.

All PC's in probably last 10 or more years like to have 2 memory modules as they can all do dual channel communication.
Some Xeon's and AMD can evem do 4 channels.
And yes, more memory improves latency, so 8GB should be minimum and there is no reason to have over 16GB for Linux and LinuxCNC if used for machine control only.
When possible, always choose 2x4gb or 2x8gb.