Advanced Search

Pretty sure SheetCAM does that also.
I use Inkscape exclusively for plasma, it does not do tool compensation, but since we almost always do decorations, just adding 2-3mm in X and Y does the job perfectly.

Thank you for reporting back with the solution.

@JackRay,
Did you get this sorted?

Here is a retrofit using Mesa 7i95 and the same encoders used for feedback to Geckos and Mesa/LinuxCNC:
forum.linuxcnc.org/show-your-stuff/47357...ing-machines?start=0

Nolan2924 wrote:

have 3 Gecko 320X drivers ST-3V breakout board.  Most folks say that I Should of used7i77/7i77e and Daughterboard?

Those "most folks" are very wrong, as Gecko uses step/dir signaling/control while Mesa 7i77 has purely analog outputs.
-The correct board for Geckos without feedback to LinuxCNC would be 7i96S, but still, if you later want to add feedback to LinuxCNC you can get a Mesa 7i85 that connects to 7i96S and has 4 encoder inputs.
-The correct Mesa board for Geckos with encoders ONLY if you want to close the loop in LinuxCNC, would be 7i95 as it does step/dir with encoder feedback.

Friendly warning: You really need to know about wiring and electronics to make sure everything is on the same potential if you want to use the same encoders for feedback to Geckos and Mesa/LinuxCNC. This will not be an issue if you have encoders wired to Gecko and glass scales wired to Mesa/LinuxCNC.

No, analog output does not work for TTL inputs:
analog output = changing voltage from 0 to 5V
PWM = Pulse Width Modulation = pulses with changing duration, so 0 or +5V
-
The correct way would be to flash PWM firmware to Mesa 7i96S included in the downloads from Mesa website (specification tab on the 7i96S page), this will replace the 5'th stepgen with PWM.
If you do need all 5 stepgens, then a cheap BOB connected to Mesa IDC26 header will also work, but i do not know if that also needs flashing or can be used with software PWM.

Just some extracted lines, from my Mcode. Program gets aborted or continues, using tkinter  askyesno.


 

On the ec300 I measure 24V on OT1 to GND when set low, 0V when set high. (Strange. I expected it to be reverse, because of safety reasons...)
 I've tested it with and without spindle setting in HAL, because you don't have spindle configured in yours (it's not the problem).

Do you have any other usable and functioning output pins (other than the working steppers)?

What voltages do you read, if the outputs pulled low?

Thanks very much, cmorley! I will check it out asap.

I just tested this and an exit value other than '0' seems to stop gcode program execution but does not issue any message to the operator, which seems a bit surprising.


I have created a Pull Request to add a note about behavior on exit codes other than 0.

Thanks for bringing this up.

When you need to measure your tools after each change, like me, you could use my subroutine (for Probe Basic up to 0.5.4: github.com/TooTall18T/tool_length_probe / for Probe Basic 0.6.0 github.com/TooTall18T/tool_length_probe/tree/develop).

Or for Probe Basic 0.6.0 you could also do that:
M6 Tx
o<tool_touch_off> call
That starts the tool measuring routine from Probe Basic after the tool change.

For Probe Basic 0.5.4 and lower it is not that easy. I would then recommend to my routine. Otherwise you would have to maintain the settings twice.

 

Any particular reason for not using the more recent 'userkins.comp' template?

github.com/LinuxCNC/linuxcnc/blob/master...onents/userkins.comp

For switchable kinematics see:

github.com/LinuxCNC/linuxcnc/blob/master...onents/millturn.comp

@Johnbl,

It's up to Tormach themself to make it available in the first place.
I  won't publish it because of ethical considerations.

From the tormach source gpl2 licence :

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.


Enforcement Options
If the company continues to refuse or obstruct access:

Public Pressure:
Open-source communities are often vocal about license violations. Publicizing the issue (e.g., in forums, social media, or mailing lists) can sometimes encourage compliance.
    
Legal Action:
Open-source licenses are legally enforceable, and violations can lead to legal consequences, such as:
Termination of License: Many licenses state that violating their terms automatically terminates the violator's rights to use or distribute the software.
Lawsuits: In some cases, individuals or organizations (like the FSF) have successfully sued companies for open-source license violations.

This would indicate that the remap has not been setup correctly. Could you guys post your ini files that cause this error please?

what i was thinking was if you had a way to control clamping independently and had the pass through requirements you could have a tube feeder and not need a 24 foot long machine to work with a full length of tube. space saving in a good way i think.