Hello Guest it is May 28, 2024, 03:42:17 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Steve Stallings

Mach4 General Discussion / Re: Using M2xx codes
« on: January 31, 2022, 08:11:20 PM »
The information you found is legit IF you are running MachMotion's custom profiles. The items described are not present in the standard Mach4 profiles from MachSupport.com installs.

Mach4 General Discussion / Re: How to execute MDI?
« on: December 14, 2021, 12:11:14 PM »
If you have selected the MDI tab to enter commands into the MDI screen, you will notice the button name changes to Cycle Start MDI and clicking on that button will run ALL the lines currently in the MDI window but will not resume the program.

Your new Velocity plot image shows the kind of pattern that is typical for a system.

You may still need to adjust the Velocity and Acceleration to match the capabilities of your machine.

It looks like you got the right settings. Remember to click on "Apply" to store the setting.

Your motor velocity plot looks strange because your acceleration is very low with respect to your maximum velocity. The motor cannot get to the requested maximum velocity during the simulated test interval.

A normal plot will look like a ramp up, a flat "cruise" zone followed by a ramp back down to zero.

The method that I offered should not require any configuration changes for your SmoothStepper.

The SmoothStepper provides additional places to configure all its pins and this often confuses people when both the Mach Configure Control and the SmoothStepper configuration offer duplicate ways to do things. You will need to know which pin is your direction signal if you plan to alter it in the SmoothStepper configuration, but that should also work.

You will find the "reverse" check box near the bottom of the Configure Control, Motors tab. In the list at the right side, you must highlight (not just check the box) for the motor that you wish to configure.

Security issues for plug-ins are much greater than for scripts accessing the API. The plug-ins require "signed" code with your companies credentials in order to be linked into the core of Mach4's code engine. A plug-in is the method needed if your device is the actual motion controller instead of using an off the shelf motion controller. Mach4 can talk to multiple I/O controllers but only one of them can be used for coordinated motion control.

LUA scripts have access to communications such as Ethernet or HID devices and can do low speed sensors just fine. LUA scripts can be run as macros triggered by M codes, or can run constantly in the background like a PLC program.

Mach4 General Discussion / Re: FTP Site Access Issue
« on: October 22, 2021, 08:48:48 PM »
Not sure that access method is still supported. Try using HTTP:


Mach4 General Discussion / Re: THC301d pin numbers
« on: October 14, 2021, 07:43:31 AM »
Here are the signals for the original THC-301 on Port 2. I expect that the THC-301D uses the same assignments.

E-Stop input                       Pin 10     Green check on Active Low
THC On output (torch fire)   Pin 15     Green check on Active Low
THC Up input                      Pin 12     Green Check on Active Low
THC Down input                  Pin 11     Green Check on Active Low

All of this relates to Mach3, and you have posted in the Mach4 section of the forum. Assuming you are actually still running Mach3.

Mach4 General Discussion / Re: E-STOP ESS PORT AND PIN number
« on: October 10, 2021, 11:01:50 PM »
The ESS can work with E-Stop on any pin, as can Mach. It is the the machine wiring and breakout board that determine which pin should be used. Port 1, pin 10 is a popular choice used by many breakout boards.