Advanced Search

FWIW, I do all of my development work (mainly QtPlasmaC) in VirtualBox, running MX Linux 23, which is derived from Debian Bookworm, and I've never seen these graphical anomalies. Same with the BM hardware at the plasma table.

Generally speaking, when these sort of things come up, it's almost always driver related.

I don't run the stock ISO of, in favor of MX Linux as I find it 10x easier to use. It might be worth making a MX Linux 23 VirtualBox and see if you can get it to show up there?

unknown wrote:

Just a guess........
If your touch screen comes up as HID (assuming USB) you may be able to modify the mouse properties in "control center" . Sorry I can't be of more help, as I haven't got access to my setup.

Thanks, I'll look into that and see if it makes any difference.

newbynobi wrote:

Looks like the screen is reacting with key events like a keyboard.
Like a keyboard repeats the key every X millis and store the number of events.

like moving the machine with a encoder and a fixed step. If you turn the hand wheel, the controller will count the encoder counts and even if you stop turning the wheel, the machine goes on moving until the calculated distance is reached.

I can unfortunately not tell you how to change that behavior. I would search for something like key repeat time.

I do use an older model of a  Faytech Touch and I am not able to reproduce the bhavior.

Norbert

 

Thanks, I think you may be right, if so I don't think there is much I can do about it other than change the screen.

 langdons post=322591 userid=41217
What the...

Weird.

Super weird.

Perhaps try a drifferent GUI?

Looks like a touchscreen issue?

Touchscreen configuration on Linux is kinda impossible, at least on Ubuntu.

What OS are you running?

It's the latest download version.
LinuxCNC 2.9.4 Debian 12 Bookworm PREEMPT-RT ISO

The spindle slider is an overrride slider like for feed and rapid override.
This does not set an absolut value like for the jogging speed.
If you have not entered an S word in MDI mode, the spindle starts at its default speed which is 350 = 100%. With the override you can increase this speed up to 120% (in your case), so up to 420 rpm. If you want 600 rpm you have to enter this in MDI mode or set a default speed of 600.

@Aciera,

Thanks, I'll try that if it doesn't work out doing the 3-way mux2 (velocity, orient, c-axis) config.

Kinda stuck at the moment as I realized my spindle motor was a contributing problem.  Once i put a heavy chuck on the spindle it became obvious while tuning the servo that the inertia ratio was really unfavorable.

I've got a more appropriate Yaskawa motor on hand, but getting the cables, 90VDC brake converter, and shaft bushing is taking a while for everything to show up.

Unfortunately today I saw the exact same display corruption on my real hardware.  No virtual machine to blame. Whatever is happening, it's definitely part of the QtVcp screen.  If you pop up a dialog for example, it will tint the black parts of the triangles.

Now to figure out a path to debugging this...

Good point, it does have a couple of controllers. I will clone the drive just in case and do some mix and matching on cables and controllers and see how that works out.

Thanks for the reply

Have to act on appTimePeriod message.
Check line two in this file github.com/dbraun1981/hal-cia402/blob/ma...le/ethercat-conf.xml and well you can copy that line to your file.
You can add line 4 as well if it isn't there already. Pay attention to placements, line 2 in the master line. Line 4 under slave, for the three drives.

The pin numbers on that label are the exact pin numbers on a parallel port, so enter those in the StepConf wizard.
As for spindle, almost all new VFD's will accept 0-5V or 0-10V that can be set, so setting it to 5V and using a resistor and a capacitor will give you roughly 0-4.5V of analog voltage from a 5V parallel port, or 0-3V from a 3.3V parallel port.

Send one to Rod, her can make it work easily as he has THCAD that turn 0-10V to frequency, and he is very detailed when testing stuff.
I do not have a laser (i do have a big box of lasers, but He-Ne ones at low power) so i can not help with testing it. I can attach it to a plasma torch and see how long it lasts with all the interference plasma causes, but that is it. Oh yeah, Rod can also test this, as he has plasma machines.

Failing hard drives will cause latency spikes for sure, despite appearing to work OK.
Bad PATA/SATA cable can also appear as failing drive, so it pays off to change the cable first.
If you do suspect a failing HDD controller, most boards will have 2 separate controllers, even older ones, so try the other one. Yes, there are many boards with 2 of PATA/IDE controllers, and there are many boards with 2 SATA controllers where usually one does also RAID.

Yes everything in the bios is off. The only thing that has changed in the pc since it was running the older version of PlasmaC without issue has been the hard drive. I can only think that either it has an issue or the controller has an issue, maybe that’s why the original drive failed.
I will try a different motherboard and HDD over the weekend

Thanks for the help

Thanks, I will take the practical approach and leave it alone.

I did catch that a bit afterwards, lol. thank you for keeping an eye out though. I tried to un-E-Stop, power button on and home all axis. No motor movement, drives are still in preop state. Have attached the resulting output.

Steve Cap