Advanced Search

Now it has let me set it to 5 + Jog, and it displays correctly.

Lcvette wrote:

Sweet are you in the probe basic Facebook group?

Yes, I'm in the Facebook group.

Heh.. the very next search i did after replying lead me to the info that the displaylink driver doesn't handle touch, Linux kernals hud-multitouch does.

always something new to learn eh.. though its pretty obveous in hindsight

To be fair to Tommy, I've used this ISO successfully for a while now, this is the first issue I've come across and its not anything to do with linuxcnc, and sounds like I can resolve it.

In fact the synaptics displaylink drivers are only officially offered for ubuntu, while there is a community Debian option available, and the second computer I have that I set up a Debian build on is struggling to get the screen to show anything, where as this Mint ISO already allows the screen to display and operate with single point touch only, which would actually be sufficient for a cnc mill, but less refined than the screen could be.

This goes to show that there are pros and cons to all options and its not at all accurate to claim we must stick with Debian.

With that said, i am wanting to try Probe Basic, and being that this was developed for Debian may be the way i go, hence the aforementioned debian unit. 

To all that replied with useful information, greatly appreciated. Ill report back with results.

well strange.
If you are content to just ignore the warning that's fine, otherwise I would need you to find the qtdragon_hd_handler.py file from your system so i could see why it's different.

Sweet are you in the probe basic Facebook group?

Lathe was always laid out for 4 + jog and Mill for 3+ jog for best fitment, if you had 7 i can't imagine it looked very good, probably all smooshed up with no space. We fixed some formatting issues and that one was one I think where it wouldn't smoosh them together. But not it pushes the screen off the bottom.. so we are to the docs a recommended limit count.

OK, just got back from the shop, and we have results, pretty good ones, now i think i have to mess with some TCP parameters as some moves are not where they should be, but in general it seems it works, it is much better than any of my attempts to coerce Gemini.
Almost 3AM here, going to watch "A Brief History of Exploring Mars" by "Classic Aerospace History" on youtube, and maybe sleep.
Was a good day, finished a lot of things on a cnc router till 9PM, ate, went for a coffee, came back to this.
Been quite some time since i had such productive day, missed it...
Aciera, thank you.

ini配置中注释或删除这行试试POSITION_FILE = position.txt
具体作用http://linuxcnc.org/docs/stable/html/config/ini-config.html#sub:ini:sec:traj

As you probably know, I’ve been using Probe Basic Lathe for quite some time on a 200x400 mini-lathe.

Solved! In the old configuration, I had those 7 increments and it displayed correctly. I'm not sure if it's something related to the Trixie version. Thanks a lot!

I'm about to replace the bearings in my PM-25MV style mill. I've got a 1.8kW AC servo motor on the spindle that runs up to 4500 rpm.

Two questions:

For the bearings on the pulley shaft (the intermediate shaft that drives the spindle belt), should I go with C3 clearance or standard clearance?

What tapered roller bearings would you recommend for the spindle itself? 

Any advice from people who've already done this would be great. Thanks!

too many jog increments no more than 4 should be used + jog

I've been using Probe Basic for quite a while, both for my mill and lathe, always with a parallel port until now. I've just finished migrating both machines to Mesa.The mill is up and running fine, but the lathe is giving me some trouble after moving to Mesa and Debian Trixie. I'm running the dev version of Probe Basic, and the problem is that not all widgets show up.The sim config displays everything correctly, but as soon as I load my own config, some widgets are just missing. I've been around the Probe Basic file structure long enough to feel comfortable with it, but there's clearly something I'm overlooking.

I should note that I have a HP EliteDesk 800 G1 that could never run Ethernet cards reliably
 for more than an hour or so UNTIL I upgraded the kernel to 7.x

It also requires:

disabling irq coalescing
isolcpus=3
and pinning the Ethernet IRQ to CPU 3

With these changes, I never get dropped packets even after months of uptime
with a PC used for compiling, youtube etc etc