FAQ - Anybus CompactCom 40-series

FAQ - Anybus CompactCom 40-series

• Q: What kind of connector do I need on my product to connect with Anybus CompactCom (Module)?

  It is a standard CompactFlash connector, which is available from many different vendors. A CompactFlash connector optimized for the CompactCom can be purchased from HMS.

• Q: Does the CompactCom 40-series support any additional communication interfaces than what is supported by the CompactCom 30-series?

  Yes, the CompactCom 40-series support SPI, 16-bit parallel, and Shift register communication interfaces in addition to the ones supported by the 30-series. 

• Q: Is the CompactCom 30-series fully hardware and software compatible with the CompactCom 40-series?

  There are minor differences in the hardware and software interface. Please consult Appendix B in the CompactCom Hardware Design Guide for more information about the differences.

• Q: What RAM and ROM resources are needed to be able to use the Host Application Example Code.

  It depends on the compiler and the target system, but as a guide line, the example code requires about 6kb of RAM and 16kb of ROM.

• Q: Can I use the same Ethernet hardware for all CompactCom 40-series supported Ethernet protocols?

  If the CompactCom Common Ethernet Module (CET) is used, the same hardware can be used for all supported Ethernet protocols. 

• Q: Are there any differences in the host application communication protocol depending on if I select the Chip, the Brick or the Module version of the CompactCom 40-series?

  No, the same firmware and the same processor is used for the Chip, the Brick, and the Module, i.e. there is no difference in the host application communication between the different types.

• Q: Is it possible to update the firmware in the CompactCom 40 from the network.

  For Ethernet based modules with IPv4 support (PROFINET, EtherNet/IP, Modbus-TCP, BACnet/IP) FTP can be used to download a new firmware image. EtherCAT and POWERLINK has protocol specific services for firmware download. HMS provides a Firmware Manager tool for easy firmware upgrade.

• Q: I have a CompactCom-equipped device built by a third-party company, which EDS/GSD configuration files should I use when I set up my PLC? And what data-related settings do I need to enter on the PLC side?

  These are questions that primarily should be directed to the party that integrated the CompactCom into their device, it is not something that HMS keeps track of or can provide information about. The software inside the application device alone decides what kind of process data setup to use on the network side, and also has the possibility to customize the identity that it will present on the network so we cannot say if one of our default description files should be compatible with a certain implementation, or what the corresponding process data map would look like.

  In the case that the application software lets the Anybus CompactCom run with its default HMS identity the example description files that we provide on the download page for each Anybus CompactCom should normally work, but configuration settings like the process data map is still something that is decided by the application-side software.

• Q: What is the maximum power consumption for Anybus CompactCom?

  As an aid when designing the power supply electronics, the networks have been divided into classes based on their power consumption as follows. Design your power supply according to the classification below depending on the intended networks.
  
  • Class A: This class includes network modules that require less than 250mA of supply current.
  • Class B: This class includes network modules that require up to 500mA of supply current.
  • Class C: This class includes network modules that require up to 1000mA of supply current. 
  
  Please see the CompactCom M40 Hardware Design Guide, chapter “A-7 Power Supply Considerations” for information about classification for the different networks.

• Q: Does the Host Application Example Code, that can be downloaded from the Anybus website, support both CompactCom 40 and CompactCom 30?
  Yes, both module series, CompactCom 30 and CompactCom 40, are supported and can be used with this code.
• Q: How is the IP settings configured for the Ethernet based modules?
  The IP settings (IP address, Netmask, Gateway etc.) can be configured either with the HMS IPConfig Tool (available on the Anybus website), from the Host Application in the Network Configuration object (04h), or with network-dependent configuration tools. Consult the CompactCom network specific guides for more information.
• Q: How can I upgrade the CompactCom firmware?
  The CompactCom firmware can be upgraded over the network (Ethernet based modules) or through the Host Application interface. Consult the CompactCom Software Design Guide and the CompactCom network specific guides for more information.
• Q: After powering on the CompactCom, are there any specific LED indications to look for to be sure the module is running?
  Normally no. The module LED:s are enabled after module initialization. The LED indications are network dependent, see the CompactCom network specific guides for more information.
• Q: What is included in the Host Application Example Code?
  The Host Application Example Code includes drivers for the CompactCom host communication protocols, together with an application example exchanging some data with a master on the network. See the Host Application Implementation Guide for more information.