Advanced Search

I don't know if Probe Basic does it differently, but the probe I use with the Axis UI is configured as a tool in the tool table. The length offset then gets applied like every other tool

Marlie013 wrote:

I believe the drive enables are wired, it's the light blue wire hidden under the grey wires in the back.

Oh yeah, i could not see it as it is obfuscated by the rest of the wiring.
More pictures, following the wiring from one board to the other, and the other if they diverge, etc.
Also the back side of the board, if possible, would help.

I believe the drive enables are wired, it's the light blue wire hidden under the grey wires in the back.
I have no schematics, and am unsure where to look.
I'm trying to figure out the wiring off the original power distribution board, which is the last picture.

Apologies for the use of improper terminology, newbie here. So, I have a PrintNC machine with Probe Basic. For the most part the setup has been intuitive, and most of the questions i've had have already been answered here. The one thing I'm a bit confused about is probing, I have a tp06 probe, and I've been using it to find corners, bosses, bores etc. So one of the settings is the tip diameter of the probe, which is perfectly clear to me as to why it's needed. The one thing I cant figure out is, isn't the height of the probe also needed? In my mind, i can bring the spindle (no tool) down until it touches the spoilboard, and record the Z height at the point (Z0). Then I cant put the probe in the spindle, and lower it until the spindle touches the spoil board and record that Z (Z1). From there the probe offset is Z0-Z1 (or the other way around), My question is, where do i configure that probe offset? is it a variable in the .var file?

Seems interesting, but i have no clue when i'll have some time to test.
I have scratchers i build and use dmap2gcode for it modified to output M67 values, works perfectly fine for my needs, and also works for an UV laser i have collecting dust in the shop (makes to much smoke, unhealthy), so i am interested to see how much the results would improve.
My scratchers:
forum.linuxcnc.org/show-your-stuff/46752...ver-etcher-scratcher
forum.linuxcnc.org/show-your-stuff/37784...-or-any-hard-surface

First, do not power on the drives, if i ma seeing properly, the drive enables are not wired on the Mesa, so again, do not power on the drives.
Do you have any schematics of the machine?
If not, it will require a bit of reverse engineering to figure out.
About wiring and testing, see here:
forum.linuxcnc.org/10-advanced-configura...to-example-mesa-7i77

Good day.  I've created a PyQt6 app to convert an image file into rasterized M67 gcode output.  It renders .svg files to 16-bit depth; check it out: github.com/mj1911/img2m67

 

Try apt install r8168-dkms
You have to enable  non-free tree in sources-list.
As I wrote above, sometimes it not works with some kernel versions, but can work with the previous or next version (it means, for example, 6.12.xx not works, but 6.12.yy works).

Which driver should i go for?

The command "lspci -nnk | grep -iA3 net " 
tells me i have a "RTL8111/8168/8211/8411" , i read something about changing the driver to the 8168, but i'm unsure..

Other thing, if it is a bit thing to get it running, what do you think about these small computers for LinuxCNC?
They are not too expensive..
Lenovo tiny M92? Which CPU would you recommend at Least?
I learned the hard way to get a INtel-Networkchip, so i will definitly have an eye on this!

Hi Cmorley

I've done some more work on 3pcenter.
If you're interested, I have either a very minor fix for one function:

   def goCenter(self):
            c.mode(linuxcnc.MODE_MDI)
            c.wait_complete()
            c.mdi('g53 g0 z0')
            c.mdi('g54 g0 x'+self.dataX+'y'+self.dataY)
            c.wait_complete()
            self.w.pushButton_5.show()

or a fix for the entire file. It's more resilient to user errors.
X0Y0 can be executed at any time and from any position.
Test it if you like.

Hi!
I am trying to add the Mesa 7i97t card into my Anilam 1100 and I am so confused. I have (hopefully) wired the three servo drives and the rotary encoders correctly to the card, but I'm lost on what else needs to be connected. I'm specifically trying to figure out this group of 8 wires running from a PCB 801 board to a 90100289 REV A board. From my searching, I believe the 801 board needs to stay and the REV A board is the one I'm trying to take out, but I'm confused on where the wires go into the Mesa. I believe they go on TB5, but I'm lost on the order/what they do.
If anyone has advice or can point me toward a guide or something, it would be appreciated!!

I have learned so much about LinuxCNC, hal, and the linuxCNC community from this thread. Thank you.

In the end I was able to solve my problem with the following hal configuration...

# --- ESTOP configuration ---
loadrt and2 count=1
addf and2.0 servo-thread

# 1. Connect physical switch to the first slot of the AND gate
net estop-ext <= hm2_7i96s.0.inm.00.input-03
net estop-ext => and2.0.in0

# 2. Connect GUI toggle to the second slot of the AND gate
net gui-request <= iocontrol.0.user-enable-out
net gui-request => and2.0.in1

# 3. Feed the combined result back into LinuxCNC's safety gate
net estop-loopback <= and2.0.out
net estop-loopback => iocontrol.0.emc-enable-in

# 4. Use the loopback to fire your physical SSR
net estop-loopback => hm2_7i96s.0.ssr.00.out-00
setp hm2_7i96s.0.ssr.00.invert-00 true

Best,

Bill

The standard Realtek Ethernet driver has real time issues, this can be fixed by using the DKMS driver

No sure whet the definittive installation instructions are but doing a forum search for DKMS should help
 

Typical.
Your network card drops the connection.
Although it can be corrupted, more often it is caused by a bad kernel or a bad kernel module.
Try installing a different kernel version or dkms driver.

Hallo Forum!

Ich bin nun soweit die Maschine zu testen und die Achsen zu verfahren.

Mein Hauptproblem: Ich kann selbst im Dialog "Achsen tunen" die Kommunikation mit meiner Mesa-Karte nur für kurze Zeit aufrechterhalten. Die LAN-Schnittstelle blinkt dann nicht mehr und es geht nichts mehr.
Die 5V Versorgung habe ich schon gegen eine stärkere getauscht, hat aber leider nichts gebracht.

LinuxCNC habe ich noch nie gestartet ohne diese Fehlermeldung:
Operation Error: hm2/hm_27i92:error finishing read! iter=4730

Der Rechner ist ein alter AMD Athlon(tm) II X2 250 Processor. 4GB DDR3-Ram, alt, aber eigentlich ausreichend, hoffe ich zumindest.
Leider auch mit Realtekchip für Ethernet.

lspci -nnk | grep -iA3 net  gibt aus:
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 03)
    Subsystem: Foxconn International, Inc. Device [105b:0e22]
    Kernel driver in use: r8169
    Kernel modules: r8169

Ich habe bereits einen Kern isoliert mit "isolcpus=0,",
meiner Meinung nach sind die Jitterwerte auch eigentlich ganz io..

Irgendwelche Ideen?

Vielen Dank schonmal, Gruß, Thomas