Anybus CompactCom - Questions & Answers

Read the most common questions about the Anybus-CompactCom

Q: What does the Software Development Kit (SDK) include? 
A: The SDK (Software Development Kit) is included in the Starter-Kit. The SDK is an Application Driver. This software is written in ANSI-C and the intention is that the customer shall port this code directly to his application. When using this Driver the application do not need any specific knowledge about the interface and the protocol (only the kind of interface needs to be known), the Driver handles everything else. When using the Driver the application need to call the timer system of the Driver cyclically, run the Driver cyclically, specify the length of the read and write process data, handle object specific acyclic requests (this includes ADI’s, diagnostics and Anybus information), setup the process data information and take proper action to warnings and errors that are signalled by the Driver.

Q: When I use the Anybus-CompactCom Driver, what does it need in RAM & ROM in my microprocessor system?
A: It depends a little bit on what processor and compiler you use, but in general you can estimate 16kbyte in ROM and 3 kbyte in RAM for the Anybus-CompactCom Driver/Software Stack in your microprocessor system.

 Q: The front panel of Anybus-CompactCom has only two LED’s. Is this enough for all networks? If a customer wants to mount LED on his carrier board, can he connect the LED signals from Anybus-CompactCom through the CompactFlash connector?
A: We have made research and found that for most networks, 2 LEDs are enough. EtherNet/IP requires 4, but the extra two LEDs will be in the RJ45 connector. Interbus requires 5 LEDs but for Interbus we are planning a M12 front which will allow more LED indicators. The LED signals are available on pins on the CompactFlash connector.

Q: Anybus-CompactCom does not have an address switch on the front panel. Does it mean that all settings for address and baud rate can be set from the application through the DPRAM /serial interface?
A: There is a special object in the Anybus-CompactCom where the address is written during INIT, so this means no switch on Anybus-CompactCom is needed. The Anybus-CompactCom will also support auto baudrate features (supported by the network). Its up to the customer if we have his user to set the address via a DIP-switch somewhere on his own electronics, or provide the address by other means, like a keyboard that might be available already on the product (quite normal on a drive for example)

Q: What kind of connector do I need on my product to connect with Anybus-CompactCom?
A: It is just a standard CompactFlash connector, a low cost connector available from many different vendors.

Q: What is the maximum power consumption for Anybus-CompactCom?
A: The Anybus-CompactCom platform in itself is designed to be extremely power efficient. The exact power requirements for a particular networking system will however vary a lot depending on to the components used in the actual bus circuitry. While most systems usually require less than 250mA of supply current, certain high performance networks, or networks which require the use of legacy ASIC technology, will consume up to 400mA, or in very rare cases even as much as 1000mA.

As an aid when designing the power supply electronics, the networks have been divided into classes based on their power consumption as follows.
• Class A: This class includes systems that require less than 250mA of supply current.
• Class B: This class includes systems that require up to 500mA of supply current.
• Class C: This class includes systems that require up to 1000mA of supply current.

Please see the Anybus-CompactCom hardware designguide, chapter Implementation guidelines A-5 for exact information on the requested networks.