Advanced Search

Seems like outputs, but, clean the chips and the board so we can see numbers and copper lines.

Not me, despite really needing the money, i never charge for any help here or when initiated from here, and i am of no use for Probe Basic, yet.
For other things related to LinuxCNC, i am here often and daily, so feel free to shoot questions here.

Ah, it sounds pretty obvious once you think about it. Thanks!

Hi everyone,

My team is using ProbeBasic / Linux CNC on a 5-axis CNC milling machine we are developing.  We've got most everything up, but don't have the INI file for the machine working properly.  To be specific, we're getting a lot of out of bounds and tool change errors.  Many (most) of the example NGC files that come with LinuxCNC don't work.  We fix one thing just to run into another blocker.  We could use some paid help.

If you're interested, email This email address is being protected from spambots. You need JavaScript enabled to view it. with the following:

• Your name / email / phone
• Resume (highlighting LinuxCNC work)
• Your general coding / management style
• What time zone you're in
• Your desired rate

We'll get back you super soon.
Thanks so much!

yeh, pretty sure its the same as qrdragon. Define your probe as a tool and record the height as you would any other tool, I used T99 for the probe.

Hi, I run a Wood manufacturing company. We currently have about eight routers. We have done a significant amount of customization of our current equipment and are looking to shift to Linux CNC and build several machines from the ground up in the next year including a feedthrough four axis machine, and a CNC lathe. I’m looking for a consultant to help guide us through this process. We have an engineering team in house. We are based in Utah.  Proximity is nice, but not necessary. If you know somebody who might be a fit or would be interested yourself, I would love to hear from you. 

tuxcnc wrote:

In my opinion, Ethercat is a great solution for small machines that can use integrated drives.
I have mills where the individual axes are connected to the rest of the machine via a one patch cord and one power cord, and things like homing limit switches  or other sensors are connected locally to additional drive inputs.
Such a machine is simple to wire and, in my opinion, more reliable.
However, if all the control is to be located in one cabinet and long and multi-core cables are to be run, Ethercat loses its advantages for now. It's just expensive and difficult to set up, and what's best about it becomes secondary...

Nonsense. ethercat drives whole factories. The advantages of ethercat remain regardless of the size of the machine. Ethercat should be a more efficient protocol than mesa hm2 so it should have more efficient bandwidth utilisation. Linuxcnc won't care if you use mesa or ethercat

 

I am not sure if tcp will help here..see attached pic...maybe not clear but difference in green and yellow rectangle show difference between tool center and reusuting cut of a profile cutter where cutting edge is offset from center of tool..seems like b axis would need more z height to give correct cut on both sides of stock.
 

I hope these help! The wires pretty much go straight down from the REV A board to the PCB board. I appreciate you taking the time to help me!


 

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