Advanced Search

HerrNamenlos123 wrote:

According to your other posts in the link, you got the BTS7960 to work nicely with Mesa cards, right? Is there also an example of an Ethernet Mesa card that will work for this? I am not a fan of the parallel port in general and would like to move away from it, since most PCs (even older ones) don't even have it anymore and Ethernet is a lot more future proof.

How did i miss this ???
Mesa 5i25/6i25 and 7i92 are the same thing functionally, so the only change needed is 3 lines in hal and ini for it to work with 7i92 ethernet card.

-older original Samsung chargers work perfectly
-avoid cheap china ones
-most buck converters work, but vary voltage with change in temperature, so i set them at 4.7-4.9V.
-never use buck/boost converters to power Mesa or relays.

That should have been the first thing you said.
Open a terminal, navigate to where the downloaded file is located and type
sudo gdebi Name_of_file.deb
Replace name of file with actual file name, that should show more info.

Another thing I haven't quite understood yet is that with my old control system, when setting up a milling job with the 3D probe, I first probed the surface of the workpiece (Z=0), then the tool length sensor. Then the milling job was started. Each time the tool was changed, the changed tool was measured at the tool length sensor and the milling process continued. So I didn't have to enter a block height or a probe height. I did not have to measure against the machine table.

This should also be possible with Versaprobe, if I have read the instructions correctly. The tool measurement button in the Vesa probe tab is enabled. I probably simply overlooked it...

Peter

besriworld wrote:

Do you have an enabling signal to each servo driver?

 

Yes I have
They are deactivated as soon as the emergency key is pressed.
But it seems that the board moves the motors by itself without receiving a command from Linux CNC

I dug further into this issue yesterday and while I didn't manage to figure out the syntax highlighting issues I did however notice that the "Save as" button actually works when you start with a blank previously unsaved file.

It's just that the filename dialog that pops up doesn't have any path set so if you just type in a filename the file is saved relative to where the config is located for the current LinuxCNC session. I think a more user friendly approach here would be to prefill the path to the directory currently displayed in the file manager to left of the G-code editor.

I suggest you take a look at this post
forum.linuxcnc.org/27-driver-boards/5038...or-5a-75b-and-5a-75e

Your preview in PathPilot looks exactly like what I expected the preview in ProbeBasic would show.

I dug further into the issue yesterday and it seems that if you are at position X100 Y100 in G54 and switch to for example G55 the plot automatically goes to X100 Y100 G55 even though the machine actually hasn't moved at all.

This causes the first move done i G55 to be incorrectly represented in the preview as the starting point of that line will start in the wrong place.

I do that. "halcmd setp axis.z.eoffset-enable FALSE" , the value changes to FALSE but the maximum speed remains unchanged.

There have been a number of reports of people having problems with USB/phone chargers.
I would stick to a Meanwell MDR-10-5 (2 amp) or a bit higher... DIN rail mount or similar.

vre wrote:

5 ethernet ports would be perfect for mesa+ethercat+internet
or the version with 2 ethernet ports+1usb ethernet for mesa+ethercat+internet

Interesting. I was looking for a little router but had missed that. 6 ports total... and 4 are intel to boot!

I can confirm that this is an issue on both QtPlasmaC and plasmac2 in both LinuxCNC 2.9 and master.
I have been able to consistently observe it on metric configs but it does not appear to happen on imperial configs, this is with both configs run both a metric g-code and a imperial g-code.
It does not happen on PlasmaC in LinuxCNC 2.8, nor does it seem to happen on AXIS in LinuxCNC 2.9.
It also happens with all hole detection features commented out, a simple piece of code like below does not run the second G3 line on some holes:Adding a G4 P1 or a G0 X2.873 Y50.627 between the G3 lines appears to make no difference.

Currently I have no idea what is causing it...

In the meantime if you need to cut this job then changing the leadins to perpendicular should work.

 

Hi Chris,
thank's for your answer. Yes MAXPROBE is a negative number. I will change it to positive.

[VERSA_TOOLSETTER]
X = 441.4
Y = 57.0
Z = -1
Z_MAX_CLEAR = -2
# MAXPROBE = -20 ### negative seems wrong
MAXPROBE = 20

How should Z be defined? On my machine, Z=-1 is at the top.

Peter

Not sure as I do not use PathPilot but testing your gcode on my regular LinuxCNC install I cannot reproduce this.
This is what I get with G55 X-offset = 150:


 

ok, well - I think I'll close this thread and thank you very much for your support.
Unfortunately, I still don't understand certain connections, even though I'm not only active here in the forum. I have to look elsewhere for my questions. thank you very much