Messages

171

Mach4 General Discussion / Re: SSR m7 serial

« on: April 13, 2021, 02:03:10 PM »

You can also use a Pokeys to control that SSR.  And that will also give you lots of expansion.  Pokeys operates on 3.3v so you have to use SSRs to switch higher voltages.  As for inputs, you need to use logic level voltage switches (like PNP or NPN prox switches) as well.  No mechanical switches on 3.3v inputs, as they will be noisy.

I really wouldn't use anything that is serial if you can help it.  Ethernet is way better in the long run. 

An example of a low cost PLC, Ethernet, 8 DC inputs and 6 relay outputs.  No SSR needed with the relays on the outputs.    It does require a 24v power source:

https://www.automationdirect.com/adc/shopping/catalog/programmable_controllers/click_series_plcs/click_plcs_(stackable_micro_brick)/plc_units/c0-10dre-d

The PLC isn't $12.00 like that serial modbus thing, but it is a more industrial solution.

Steve

172

Mach4 General Discussion / Re: Tool setter, M6, tool length offsets

« on: April 12, 2021, 08:04:51 PM »

The tool offsets are loaded into the dialog when the dialog is opened.  The dialog is not updated on the fly.  That tool offset dialog is meant for modifying the offsets within the dialog, not outside of the dialog.  Also, the offsets are not written (even if modified in the dialog) until you close the dialog with the X in the upper right hand corner or by pressing the "Quit" button.   I would not consider this a bug because it is just not how it works.  If you want something that is updated constantly, make a screen that displays the tool offsets from the G code variables.  So close the tool offset dialog and reopen it after the tool change/probe and see if the value is updates.  If the value does not update, then you need to further develop your M6 script. 

Steve

173

Mach4 General Discussion / Re: bug in dev. ver 700 and 703

« on: April 12, 2021, 07:43:21 PM »

For clarification, it has to be a screen set issue and the support guys should be able to help you out quickly. 

Steve

174

Mach4 General Discussion / Re: bug in dev. ver 700 and 703

« on: April 12, 2021, 07:42:32 PM »

Stuart,

Please call or create a support ticket for this.  You have phone support with your Industrial license. 

Steve

175

Mach4 General Discussion / Re: mcSignalWait issue

« on: April 11, 2021, 08:22:02 PM »

All position words (XYZABCUVW) require a position, otherwise there would be a G code syntax error.  The manual states that the positions given on the G28.1 block are ignored.  "G28.1 X0" or "G28.1.X150" should be no different than just pressing the Ref X button on the diagnostics tab.  All homing, whether from a button or via G28.1 is done on the motion controller.  Meaning all Mach does is ask the motion controller to home the axis.  So...  if you are experiencing strange homing behavior, check with your motion controller vendor. 

I tried mc.mcSignalWait() and it worked flawlessly.  Make sure you are not running an ancient build.  And are you checking your API return codes?  Because if mcAxisRefAll() returned mc.MERROR_NOT_NOW, then you would be waiting on a signal that would never come.  But if you didn't check the API return code, well... 

The GUI uses mc.OSIG_HOMED_X, mc.OSIG_HOMED_Y, mc.OSIG_HOMED_Z, mc.OSIG_HOMED_A, mc.OSIG_HOMED_B, and mc.OSIG_HOMED_C output signals to light up the axis homed LEDs on the screen, so they are working. 

Steve

176

Mach4 Plugins / Re: XHC WB04 plugin

« on: April 10, 2021, 07:33:00 PM »

You can find it in the latest dev build. 

http://www.machsupport.com/ftp/Mach4/DevlopmentVersions/

Get the highest number there. 

Steve

177

Mach4 General Discussion / Re: mcSignalWait issue

« on: April 09, 2021, 02:40:30 PM »

You can home with code.  See G28.1 in the manual.  Homing with G28.1 is the ONLY way to home the machine in automatic mode (not idle). 

G28.1 X0 Y0
G00 X1 Y1 (Both X and W will be homed by this point). 

If you are homing the machine from a script, you have to start the script from the idle state.  Otherwise the home operation will fail and you will wait on a signal forever or timeout.  But you would know this if you checked you API function return code, right?    Because the mc.mcAxisHomeAll() function would return mc.MERROR_NOT_NOW if you are not in the idle state. 

There are a few ways to check when the home op is done
1. mc.mcSignalWait() for each axis you are interested in.
2. mc.mcAxisIsHomed in a loop for each axis you are interested in.
3. mc.mcCntlGetState() in a loop.  Once you start the home operation in the idle state, the state will no longer be idle.  So you can wait on the state to go from idle to non-idle and back to idle if you want. 

Code: [Select]

local rc = mc.MERROR_NOERROR
rc = mc.mcAxisHomeAll(inst)
if (rc ~= mc.MERROR_NOERROR) then
    -- the mc.mcAxisHomeAll() function failed and we must NOT wait on a signal
    return
end
--  now you can use mc.mcSignalWait() or mc.mcCntlGetState() or mc.mcAxisIsHomed() to find when the home operation is finished.

Steve

178

Mach4 General Discussion / Re: Rtx64

« on: April 09, 2021, 02:07:35 PM »

You can use the KINGSTAR plugin on one Ethernet card.  That will be your EtherCAT network.  All EtherCAT devices will be driven from this card.  Then you can have a second Ethernet card to run other Ethernet devices like a PoKeys or a Galil RIO, etc...  This can be used to provide I/O for panel switches/buttons and other no-realtime inputs or outputs (panel LED indicators, etc..)

The important thing to note is that you cannot then wire a probe to the Pokeys and expect the KINGSTAR plugin to see the probe signals.  The same goes for any real-time switch like a limit or a home.  Most EtherCAT servo modules have some general purpose I/O on them that could be used for things like a probe/limit/home.  But you would need to look VERY carefully at your proposed device list to make sure.  Otherwise, you would need to buy some sort of EtherCAT I/O device. 

Steve

179

Mach4 General Discussion / Re: The machine can jog around, but nothing happens from MDI or GCode

« on: April 08, 2021, 04:12:43 AM »

There is an inhibit motion (like a program running), inhibit jog, and inhibit MPG.  If you implement a safety light curtain, you would typically route it to all three of those signals at once to stop everything.

Steve

180

Mach4 General Discussion / Re: Rtx64

« on: April 08, 2021, 01:07:22 AM »

Ahh...  here we go.  https://www.automationtechnologiesinc.com/products-page/mach4-ethercat-system  Those are packages.  One of probably many out there. 

Steve