Host Engineering Forum

General Category => ECOMs and ECOM100s => Topic started by: jarmstrong on November 06, 2007, 02:08:57 PM

Title: Yaskawa MODBUS
Post by: jarmstrong on November 06, 2007, 02:08:57 PM

Have you heard of anyone using a HO-ECOM100 as a MODBUS client to Yaskawa SMC4000 acting as a master? I am trying work through Yaskawa's reference manual, but I am becoming uncertain if there is light at the end of the tunnel.

Title: Re: Yaskawa MODBUS
Post by: Greg on November 06, 2007, 04:24:56 PM

Haven't used H0-ECOM100 as Modbus TCP client to the Yaskawa SMC4000, but there is a .PDF file that you need, right here:

http://www.hosteng.com/FAQFiles/ECOM.htm#FAQ0038

The .PDF file shows the mapping for ECOM100s using Modbus TCP as Client or Server.

Title: Re: Yaskawa MODBUS
Post by: klange on May 02, 2008, 10:24:02 AM

I am presently using a Yaskawa SMC 3010 controller with an H-2 ECOM100 of four machines

I use Modbus to transfer set points and error codes

Inputs and outputs are used start and stop motion.

I had latency issues with trying to start and stop motion with Modbus

There is light

Title: Re: Yaskawa MODBUS
Post by: Controls Guy on October 20, 2009, 04:15:04 PM

Quote from: jarmstrong on November 06, 2007, 02:08:57 PM

Have you heard of anyone using a HO-ECOM100 as a MODBUS client to Yaskawa SMC4000 acting as a master? I am trying work through Yaskawa's reference manual, but I am becoming uncertain if there is light at the end of the tunnel.

"Client" and "master" mean the same thing.  If the PLC is initiating the Modbus transactions and the drive responds, the PLC is the master and the drive is a "slave".  If the drive is initiating and the PLC responding, that seems like an odd configuration.