MBX DRIVER FAQ

• After installing the MBX Driver software, we suggest running the MBX Demo program to ensure the driver is configured correctly and running properly.
  


• Initially, always configure the MBX device for polled mode of operation. In this mode, a memory range is the only resource that needs to be configured. Later, you can change it to interrupt mode.
  


• If you are experiencing problems with performance, make sure both the adapter card and the driver are set up for either polled mode or interrupt mode.
  


• In polled mode, the recommended polling rate to use for optimum performance is 20 msec. The interrupt mode of operation will provide higher message rates at the expense of higher CPU load. Low-end systems (such as 486 based systems) may provide a better overall performance with adapter cards configured to run in polled mode.
  


• Make sure the adapter card’s memory address is unique and does not conflict with other cards in the system. Check for error messages in the Event Viewer. They may aid in detecting hardware conflicts.
  


• Make sure that you are communicating through the right device.
  


• Make sure that you selected a unique node address for your device.

The next step is to configure a device. You’ll need to know the card’s memory address and interrupt. See the Configuration section for more details.

The two most common errors result from either a conflict with another device or the driver configuration not matching the card configuration. Verify that the card’s memory address matches the driver’s address. Also, compare the state of the interrupt jumper on the card with the polled/interrupt mode setting of the driver.

If the configurations match, there may be a conflict in the system or the card may be faulty. If possible, try a card that is known to be good in the system with the same settings. If errors still occur, try setting the card to polled mode and moving it to a new memory address (C8000, D0000, D4000, and D8000 are usually good addresses to try). Make sure you change both the driver and card settings.

Try setting the card to polled mode and moving it to a new memory address (C8000, D0000, D4000, and D8000 are usually good addresses to try). Make sure you change both the driver and card settings.

We recommend polled mode. Interrupt mode gives slightly higher performance, but it puts a greater load on the CPU. Finding free interrupts and worrying about interrupt conflicts may also be a concern. For the majority of applications, running in polled mode with a 20 msec polling interval will provide sufficient throughput. Whichever mode you choose, make sure the jumper setting on the card matches the driver setting.

There are two things to check. First, make sure the card is plugged into the network. Second, it’s likely that both nodes have the same network node address. Shutdown the system, change the card’s network address by changing the DIP switch settings (refer to the "Modicon IBM Host Based Devices User’s Guide" from Modicon), and restart the system. You should now be able to see all of the nodes.

The MBX Demo program uses the device number to determine which card to use. The Set Device Number option lets you choose which device the demo will use. If you are using some other software, contact the manufacturer for more information on using multiple cards.

Your adapter card may not support Peer Cop. Early versions of all host interface adapter cards do not support Peer Cop.

Since the TSXMBP100 and the PCMCIA 416NHM21234 cards use the same card ID, the operating system cannot tell them apart. However, the TSXMBP100 card uses different firmware and does not provide the full functionality of the PCMCIA 416NHM21234 card. Only the PCMCIA 416NHM21234 card is supported by this driver. Contact your Schneider distributor to upgrade to the PCMCIA 416NHM21234 card.