Advanced Search

Make a new QtPlasmaC config, make sure it works properly, only then try to do modifications.

From google translate

The commented out jogs are from the sample that comes with the card I am using.
Am trying to jog using the arrow keys on the qtPlasmac GUI.

The startup shows these as disabled as expected, and when each axis homes they become active.

If I press one the the axis value increments, and the display show the head moving in the corresponding direction, but the motors do nothing.

MDI command like G0X100 do the same

Open it, take some pictures on the inside, post them here ...........

You likely need to disable IRQ coalescing as described in the hm2_eth manual page

man hm2_eth

 

Hello all, could use some help.  Currently in the final throws of getting a new build up and running:
QtPlasmaC V2.9-238.314
Raspberry Pi5
Mesa IO boards
Sheetcam and associated post processors

I realized that my THC was active on holes, which then led me to see that M67 commands weren't working for my holes.  Further investigating showed the following:

• M67 is working as I expect it to if G1 linear commands follow in lines below
• When a G3 is encountered, it resets feedrate to 100% and executes the arc at 100%
• I didn't test G2 yet
• If an inline M67 is issued with the G3, it will execute the arc at commanded rate.  For example, have the following as one line of code:
  • G3 X0.0 Y0.0 I-0.2 J-0.2 M67 E3 Q50
• However, after executing the above correctly it STILL resets feedrate back to 100%

I don't believe this is the expected behavior, my apologies if it is.  If it is the expected behavior, can someone point me to a Sheetcam post processor that would format it as such?

Thank you!

That's why that's for Developers only that is why it's not running, is setup to run in a virtual environment only, follow the apt install instructions for install and all should work.

kcjengr.github.io/probe_basic/stable_quick_start_apt.html

I first tried installing using the guide but it seems part of the links are broken. I then eventually found the script to install it on git. github.com/Lcvette/qtpyvcp-bookworm-inst...r?tab=readme-ov-file

So I installed Debian 12 and followed the steps on the git. This is where I know I can get the dev version to launch, but when I set up my machine file, it just never launches. I will join the FB group going forward.

Yeah, at this point it's not worth my time to look into it, so I just used my USB adapter and it's working perfectly.
I'm planning on upgrading my VFD and spindle to a proper setup in the future, so hopefully I'll be able to use mesa_modbus then.

vre wrote:

Where can i buy both cards and thcad2 from europe in good prices ?

www.eusurplus.com
www.welectron.com/navi.php?k=324

-Get another mouse with better/thicker cable
-Put a ferrite "doughnut" on the motor wires just outside of the VFD
-Put a diode in parallel with the relay coil, mind the polarity

@gene_weber There is one Linux kernel at the heart of all of them maintained by the Linux kernel team. But there are with many different numbered versions and with a whole galaxy of different patches that get applied by distribution maintainers, as well as civilians like me and rodw.

If you just want a working PREEMPT_RT kernel with LinuxCNC, install rodw's image.

Hi,
I upgraded my machine from linuxcnc 2.8 to 2.9 and now I have a problem with probe_screen (from verser), because of my small monitor. Everything worked for 2.8, where I used probe icons for a 1024x768 screen. But the actual icons of the version for 2.9 do not include these, which leads to a gmoccapy gui that is larger as my monitor.
So my question is how to solve this:
Is there a way to reduce the whole probescreen with some commands?
Or does a reduction in icon size solve this? If so, to which size should they be reduced? I am not sure if I can use the old ones, have not tested yet, maybe that would be a third option, but it looks as if the one or other icon has been added.

Ooooh, wow! That worked like a charm Thank you so much!

Hi all,

This question is coming from me trying to better understand motmod. What about motmod makes so that this comp needs to create and manage its threads instead of having the "threads" module handle setting up threads and then loading motmod after?

So far I understand that threads need to be loaded in a particular order (fastest to slowest) and that motmod also ensures that the base and servo thread are integer multiples of each other. Besides this what other things does the motion planner need to guarantee about its threads to work properly?