Messages

91

General Mach Discussion / Re: ESS/MX3660 and Estop issues?

« on: May 31, 2014, 12:02:29 PM »

All's well that ends well.

It's 2am an I'm off to bed. I've just finished watching Mick Rogers (Australian) win a mountain top finish stage in the Tour of Italy. What a ride!!

Cheers,

Peter

92

General Mach Discussion / Re: ESS/MX3660 and Estop issues?

« on: May 31, 2014, 06:19:45 AM »

Presumably you are using Pin 15 to inform Mach3 that an EStop has occurred?

If so, have you confirmed with a multimeter that the MX3360 is driving pin 15 correctly when the MX3360 Estop input is activated?

Peter

93

General Mach Discussion / Re: ESS/MX3660 and Estop issues?

« on: May 30, 2014, 08:47:31 PM »

Yes, you need to set up your Estop as Hood suggests.

The Estop needs to remove the power as you are going. It also need to inform Mach3 that an Estop has occurred. This can be done by using a ESop button's 2nd pole to switch a logic level signal that gets to Mach3 via the breakout board and through the SmoothStepper.

Cheers,

Peter

94

Modbus / Re: Lag between Mach3 and ModIO output turning on

« on: May 27, 2014, 04:47:03 AM »

Hi Sam,

No problems. You want to write BF( hex), or 191 decimal. In Binary it's 10111111

Made up of
101 ----------- 115,200 baud
     11 -------- 8 bits, 1 stop, no parity
         1 ------ Limit Error Flash
           1 ---- Unused
             1  - Check inter message gap


Write the value in then reset the ModIO, then change the baud rate to 115,200 in Mach3.

Cheers,

Peter

95

General Mach Discussion / Re: ATC macro for 8 slot toolchanger with auto probing.

« on: May 26, 2014, 06:40:25 PM »

Hi,

Get in contact with Scott Shaffer, He should be able to help you out.

Cheers,

Peter

96

Modbus / Re: Lag between Mach3 and ModIO output turning on

« on: May 23, 2014, 03:51:55 AM »

Hi Sam,

The baud rate is set in ModIO register 102. Have a look at section 6.2.3 on page 41. Once you change it you will need to reset the ModIO for it to take effect.

Cheers,

Peter

97

Modbus / Re: Lag between Mach3 and ModIO output turning on

« on: May 22, 2014, 08:47:59 AM »

Hi Sam,

The error light blinking indicates that the is a communication error. Once you change the baud rate on all the modios, you then need to change the baudrate in Mach3 to 115200 as well.

Whenever you change a config item in a ModIO, you need to reset it (or power cycle) for the ModIO to start using the change.

Cheers,

Peter

98

Modbus / Re: Lag between Mach3 and ModIO output turning on

« on: May 16, 2014, 10:50:27 PM »

Hi Sam,

The Brains only 10 times a second so there can be up to 100ms delay there.
For the Modbus side of things, it's running every 25ms. At 57600baud, that's approx 5760 chars max per second.

I'm assuming at you are using the write register command. So to write one 16 bit  register takes 11 bytes. The reply is 8 bytes, or 19 in total.  At 57600 baud thats 4ms per ModIO including the inter message delay.


 For 7 ModIOs that 28ms in total, over the 25ms schedule. I'm also not sure what Mach3 does in terms of whether there are delays between the commands to each ModIO. Since your total transaction time for 7 ModIOs is longer than 25ms. You may be better setting the cycle to 50ms.

Also, increase the baudrate in the ModIOs to 115200 baud. That may keep the transaction time under 25ms.

Cheers,

Peter

99

Modbus / Re: Problem with Test Modbus Function

« on: May 05, 2014, 03:33:14 AM »

Also, are you using a USB to serial converter? Some converters  wait for their buffer to fill  or a delay after no activity before passing the data on to the program (Mach3). Extending the timeout in Mach3 can sometimes cater for this.

Cheers,

Peter

100

Modbus / Re: Problem with Test Modbus Function

« on: May 05, 2014, 03:28:59 AM »

Basically, when you write to a config register, The ModIO stores the value in EEPROM. The chip takes time to program the value. Try changing the timeout to 200ms rather than 50ms ans see how you go.

The timeout is there to detect comms problems and needs to be set to 3-5 times the maximum round trip delay. The delay is composed of sending the request to the slave, the slave processing the request and then sending the response.

Cheers,

Peter.