Advanced Search

So, I have 4 distinct problems that have come up switching and already working control to probe basic. Hoping some people can help.


1: i cant move the axes before homing. i need to be able to move them into postion and then home. i assume there must be a toggle somewhere for this.

2: the install process wiper out my ethercat driver somehow, and now it wont start on boot. i need to go and do it manually. It seems probe basic installed or updated other things along with itself. I need to un-update them.

3: when i shut off the machine (power button in linuxcnc) i get a lot of limit and joint errors. these were not in the axis setup. I feel like this is related to issue 1.

4: i have a 1680x1050 screen. i and scaling the output to force fit probe basic. this worked ONCE. and then after rebooting probe basic has scaled itself off to the right side and reports a resolution of 2077x1080.

Any help on any of these would be appreciated, thanks!

There are a few minor things that could be improved, of course in qtdragon.

1. The grid in the preview is in inches; it doesn't switch to millimeters when the machine is running in metric mode.

2. The "run time" window freezes when paused, but when resumed, the time is set as if it weren't paused. Shouldn't that be the case?

3. Manually switching between MANUAL MDI and AUTO modes is unnecessary in many cases and sometimes annoying.
For a long time, I've been using the "btn_start_clicked" function without checking if the machine is in the "auto" state. After pressing start, the machine switches to auto mode automatically, and it works very well.
I'd like the "file" button to work similarly.
After pressing "file," switch the machine to manual mode and open files. 

4. The physical keyboard's pause key only works in "auto" mode, so if the program is run from a macro, the machine is in MDI and pause doesn't work.
In the "on_keycall_pause" function, simply remove the appropriate condition.
The "btn_pause_clicked" function probably also needs to be corrected, because if the "spindle lift" button is active, then after resuming work, the spindle starts and lowers, but doesn't continue. In other cases, everything works correctly.

Yes you most probably can, as it is controlled by two parallel ports, see what port is wired to drives and remove it, wire drives to Mesa, then get an IDC26 to DB25 adapter cable and use that to wire the second port to Mesa, granted the encoders and maybe inputs are on it.

Hello, I have a—Belgian?—Gallic 16 NC lathe. When I acquired it, I removed the control system but left the spindle power unit in place. For the control system, I use Mach3 via two parallel ports, UHU drives, and DC servos. I can also turn in a quasi-conventional manner using two electronic handwheels. The whole setup worked well for years, but it is admittedly outdated. Now I have a fault in the original main power circuit. Although I have an old wiring diagram, the actual wiring is a chaotic mess. I am now considering overhauling the main power circuit to make it organized and installing a more modern control system. However, I need to be able to use the two electronic handwheels, as there are no mechanical ones. Does anyone have experience with a control system that is affordable (the machine is 35 years old and could fail completely at any time), supports two electronic handwheels, and doesn't come with a 1,000-page manual?
In my stock is a Mesa 7I96 Eth, can I use it?
Many thanks for any replies,
Hans

G'day all,

This is a question about Andy's lathe macros. I am getting a slight angle / coordinated facing angle although I set zero angle in the cut parameters. 



Is this finger trouble on my part, or a possible bug?
Cheers,
Mark

First of all thank you for the help
with your tips I managed to get a list of all the I/O pins and managed to test the inputs manually
I also managed to create and edit a qtplasmac config the way you suggested, now I can get it to run

I managed to get these things working:
-QtPlasmaC interface
-motion on all axis when jogging the machine
-external E-stop
-torch break detection switch
-machine enable output turning on a light

but im still having some problems:
- cant get a torch on output signal when I do a torch pulse
- the ohmic probe enable doesn't output any signal
-when I hit cycle start the G code pauses without moving the machine

what are the best ways to debug this situation and what should I be looking for?
all config files in a zip file below

Thank you again 

Hello everyone,
first of all, thanks to Wischi for the touch gesture version of gremlin.py — it works perfectly on my hardware (Melfas LGD AIT touch panel, LinuxCNC 2.9, Gmoccapy).

The only limitation for me was the one HansU already mentioned: with the mouse you can only rotate, dragging/panning does not work in any setting, because motion() returns unconditionally.

I'm attaching a version that is Wischi's file unchanged, with one addition: instead of disabling motion() completely, it now filters events by their source device. Only events that clearly come from a real physical mouse are processed — the event must not be pointer-emulated, the source device must be classified as MOUSE, and the device name must not contain "touch". Everything ambiguous is discarded, so the touch behavior stays exactly as in Wischi's version.

The background: many touch controllers expose a second X input device that does driver-level mouse emulation (mine shows up as "Melfas LGD AIT Touch Controller Mouse" in xinput list). Its events look like genuine pointer events to GTK — no emulation flag set — and those are what caused the original "preview only moves a couple of mm then stops" bug in the legacy motion() path. That's why the filter also checks the device name, not just the emulated flag.

Result on my machine:

Touch: unchanged from Wischi's version — one finger rotates (perspective view), two fingers pan and pinch-zoom
Real mouse: full mouse_btn_mode behavior restored — left rotate, middle drag/pan, right zoom (mode 0), shift+left drag also works
Since motion() is active again, the mouse button mode setting in Gmoccapy works again too
Tested on LinuxCNC 2.9 with Gmoccapy, capacitive multitouch panel. As before: just replace gremlin.py in /usr/lib/python3/dist-packages/ (keep a backup of the original — it gets overwritten on updates).

Changes:
1. Lines 40–50 — header comment (documentation only)
2. Lines 676–699 — new helper function _is_real_mouse_event()
3. Line 700 — motion() 

Dislexic

Its in Master branch.

May I ask how the project is going? Any update?

QEMU?

QEMM on Linux is more to my taste than Virtual Box in Windows. On Linux VB kept getting in a tangle over UEFI

Simple answer would be find the old image and do not change it, but no idea how or where or anything as i do not use RPI's.
From what i read here (hence the i do not use them as they are way to much trouble), there is something that needs to make GPIO active, but i do not recall what or how.

Take some pictures of ...everything and post them here.

This is the second time i am reading this, most if it is your statements, not questions, the only actual question i can find is about the dual Y axis, and that can be done in multiple ways, from using the same output for both, to have two separate outputs with two separate home switches and the added possibility of tramming the axis every time the machine homes.
The Mesa 7i96S should be all that is needed from what i gather, but you will not have position feedback to LinuxCNC and that is fine, but if you do want that and the drives have encoder outputs, you can add a Mesa 7i85 or 7i85S as it has 4 encoder inputs, and there is another one on the 7i96S for the spindle feedback.