Results 1 to 14 of 14
  1. #1
    Join Date
    Apr 2020
    Location
    Australia
    Age
    31
    Posts
    5

    Default Delta VFD CP2000 connection via ethernet

    Hey good day everyone.
    I'm trying to connect 2 Delta VFD CP 2000 using CMC-MOD01 modules to connect them to the router and manage them from the PC and or PLC
    By now, Delta DCI soft recognizes both of the modules without any problem. In fact I can see all the parameters of both of the VFDs using the monitor, its assigned IPs.
    Problem is when trying to use VFDsoft, as it needs COM address and its parameters but I don't have them, and I don't know if I'm missing any other component in order to make it work.

    VFDCP2000--CMC-MOD01--------------Router---------------PC

  2. #2
    Join Date
    Sep 2012
    Location
    York, North Yorkshire UK
    Posts
    6,434

    Default

    Hi Acu.tm,

    Quote Originally Posted by acu.tm View Post
    Hey good day everyone.
    I'm trying to connect 2 Delta VFD CP 2000 using CMC-MOD01 modules to connect them to the router and manage them from the PC and or PLC
    By now, Delta DCI soft recognizes both of the modules without any problem. In fact I can see all the parameters of both of the VFDs using the monitor, its assigned IPs.
    Problem is when trying to use VFDsoft, as it needs COM address and its parameters but I don't have them, and I don't know if I'm missing any other component in order to make it work.

    VFDCP2000--CMC-MOD01--------------Router---------------PC
    You should be able to talk to the modules, since you already have a connection via the IP address. The only other way as far as I know would be to use a serial port ! To use one you will need the com port address. Its likely that the software only understands one module at a time, so you will need two serial connections.

    All the com ports on a PC have a standard address, but it does depend upon how the BIOS assigns them.

    Look here.

    https://www.lookrs232.com/rs232/addresses.htm
    Best Regards:
    Baron J.

  3. #3
    Join Date
    Mar 2011
    Location
    Southern Flinders Ranges
    Posts
    1,536

    Default

    You probably don’t have the modbus addressing set up correctly

  4. #4
    Join Date
    Apr 2020
    Location
    Australia
    Age
    31
    Posts
    5

    Default

    Quote Originally Posted by BaronJ View Post
    Hi Acu.tm,



    You should be able to talk to the modules, since you already have a connection via the IP address. The only other way as far as I know would be to use a serial port ! To use one you will need the com port address. Its likely that the software only understands one module at a time, so you will need two serial connections.

    All the com ports on a PC have a standard address, but it does depend upon how the BIOS assigns them.

    Look here.

    https://www.lookrs232.com/rs232/addresses.htm
    thank you for you answer. In fact yes, I can talk with the modules and see some parameters of the VFD. What I cannot do is control it by now. I'm trying to do it first with the computer, and then to do it with a PLC program.
    So that's why I'm thinking if this module is suppoused to do this. I can even get to the IP address with the web browser and I can se a DELTA inscription but nothing else.
    VFD software will allow me to connect it only using a COM port, at least by now. In theory, module is a Modbus TCP Communication Card. But user manual ends after the configuration of the IP addresses and parameters view, and there's where i'm stuck now


  5. #5
    Join Date
    Apr 2020
    Location
    Australia
    Age
    31
    Posts
    5

    Default

    Quote Originally Posted by racingtadpole View Post
    You probably don’t have the modbus addressing set up correctly
    I thought about it, but if that were the case I wouldn't be available to talk with the modules. Am I right?

  6. #6
    Join Date
    Apr 2020
    Location
    Australia
    Age
    31
    Posts
    5

    Default

    Quote Originally Posted by BaronJ View Post
    Hi Acu.tm,



    You should be able to talk to the modules, since you already have a connection via the IP address. The only other way as far as I know would be to use a serial port ! To use one you will need the com port address. Its likely that the software only understands one module at a time, so you will need two serial connections.

    All the com ports on a PC have a standard address, but it does depend upon how the BIOS assigns them.

    Look here.

    https://www.lookrs232.com/rs232/addresses.htm
    Thanks for the answer. In fact, I can talk with the modules, config its IP, gateway and submask, and see some parameters of the VFD. But by now I haven't been able to control the VFD.
    VFD software will only allow me to configure a COM port instead of IP addresses, so that's why maybe I'm thinking if these modules are suppoused to control the VFDs via ethernet.
    In theory, these modules are Modbus TCP Communication Card. I followed the manual in order to configurate them, and got stuck just after it, when it comes the time to move to the VFD.
    I can even get to the IP address using a web browser and by now I'm only getting the DELTA logo in it but nothing else.

  7. #7
    Join Date
    Nov 2017
    Location
    Geelong, Australia
    Age
    57
    Posts
    2,651

    Default

    I know very little about Modbus, but sounds to me like you're mixing Modbus and serial tools.

    If its any help, you can get ethernet enabled serial devices. Plug the end device (VFD) via serial into the serial device, plug both the serial device and computer into ethernet.
    The computer sees the serial device as a local serial port (but communicates with it remotely via ethernet).
    We use Digi gear at work for printing labels to older serial-only printers from unix/linux servers, but I'm sure there will be cheaper options :
    https://www.digi.com/products/networ...device-servers

    If you're into a bit of messing around to save a few $$ then something like a Raspberry Pi that you can connect to the VFD's via serial and "share" those serial ports would be an option to look at.

    Edit: I've also used the Lantronix gear at work recently. Much better than the Digi stuff.
    Search on ebay etc for "serial device server" will give you a broader indication of what is around.

    Steve
    Last edited by OxxAndBert; 14th Apr 2020 at 05:27 PM. Reason: More info

  8. #8
    Join Date
    Sep 2012
    Location
    York, North Yorkshire UK
    Posts
    6,434

    Default

    Hi Guys,,

    Modbus, is a serial communications protocol, later changes allowed it to function using TCPIP.

    Fortunately I've never had to use it. From comments made in a previous post communications had already been established, since the device parameters could be seen but not changed. The software asking for com port addresses suggests that is looking for the device com port rather than the computer one. Possibly just the device ID. The Modbus protocol allows up to 256 devices on a bus, each device can see the request but only the device corresponding to to the request number will respond.

    HTH.
    Best Regards:
    Baron J.

  9. #9
    Join Date
    Nov 2007
    Location
    Near Rockhampton
    Posts
    270

    Default

    A quick read of a VFDSoft manual I found online suggests it might only connect via RS232 or usb adaptor installed on the PC. No mention of Ethernet that I could see.

    John

  10. #10
    Join Date
    Apr 2020
    Location
    Australia
    Age
    31
    Posts
    5

    Default

    I could talk with a DELTA representative and he told me the module is not suitable for this action.
    I will need a CMC-EIP01, and using COMMGR software by delta, it will generate me the COM port to connect it with VFDsoft. so easy!
    I hope this module works fine when I get it. Otherwise I will need to keep seaching.

    Thank you all

  11. #11
    Join Date
    Mar 2011
    Location
    Southern Flinders Ranges
    Posts
    1,536

    Default

    Quote Originally Posted by BaronJ View Post
    Hi Guys,,

    Modbus, is a serial communications protocol, later changes allowed it to function using TCPIP.

    Fortunately I've never had to use it. From comments made in a previous post communications had already been established, since the device parameters could be seen but not changed. The software asking for com port addresses suggests that is looking for the device com port rather than the computer one. Possibly just the device ID. The Modbus protocol allows up to 256 devices on a bus, each device can see the request but only the device corresponding to to the request number will respond.

    HTH.
    Because I'm a pedant at times...

    Only 255 Addresses available, 0 is the broadcast address
    MODBUS TCP is the IP capable and it differs somewhat from MODBUS RTU

    Carry on

  12. #12
    Join Date
    Mar 2011
    Location
    Southern Flinders Ranges
    Posts
    1,536

    Default

    Quote Originally Posted by OxxAndBert View Post
    Edit: I've also used the Lantronix gear at work recently.
    You will probably come to hate the stuff given long enough..

  13. #13
    Join Date
    Nov 2017
    Location
    Geelong, Australia
    Age
    57
    Posts
    2,651

    Default

    Quote Originally Posted by racingtadpole View Post
    Because I'm a pedant at times...

    Only 255 Addresses available, 0 is the broadcast address
    MODBUS TCP is the IP capable and it differs somewhat from MODBUS RTU

    Carry on
    Is there something subtly different about Modbus addressing?
    254 addresses on a normal network, 255 is the broadcast address.

    Resuming normal transmission........

    Steve

  14. #14
    Join Date
    Mar 2011
    Location
    Southern Flinders Ranges
    Posts
    1,536

    Default

    Quote Originally Posted by OxxAndBert View Post
    Is there something subtly different about Modbus addressing?
    254 addresses on a normal network, 255 is the broadcast address.

    Resuming normal transmission........

    Steve
    Nothing subtle about it. Modbus addressing is an entirely different animal to IP addressing, they are different protocols.
    Modbus TCP is, and I take a few liberties here making this statement because it is grossly oversimplifying, effectively a Modbus RTU transmission wrapped inside a TCP/IP packet. End result is a protocol within a protocol, again grossly oversimplifying it.
    Modbus RTU has address ranges 0-255 available,256 in total, Address 0 is used as the broadcast address.

    TCP/IP also supports 256 addresses. 0-255, 0 is a valid address, 255 being broadcast.

Similar Threads

  1. Ethernet motion control board choices ?
    By MasterSpoon in forum CNC Forum
    Replies: 14
    Last Post: 10th Apr 2019, 05:24 PM
  2. Simple VFD connection for multiple switch locations
    By jhovel in forum METALWORK GENERAL
    Replies: 0
    Last Post: 5th Jan 2016, 01:35 PM
  3. Connection Suggestion - A Centring Scope Wiring Question
    By Anorak Bob in forum METALWORK GENERAL
    Replies: 68
    Last Post: 12th Oct 2014, 10:37 PM
  4. MIG disposable gas bottle connection
    By Mick. in forum WELDING
    Replies: 6
    Last Post: 3rd Jan 2012, 12:17 PM
  5. Delta or Y?
    By BobL in forum METALWORK GENERAL
    Replies: 15
    Last Post: 28th May 2011, 01:33 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •