We are aware of a small problem with the 6200 Designer software that, under certain (though uncommon) circumstances, results in dropping offline when the 6200 hardware is connected via Ethernet.

The two scenarios under which we are able to duplicate this problem are:

Network saturation (for example, CobraNet traffic):
By sending a large volume data such as broadcast CobraNet audio (multicast bundles) onto the same subnet as the 6200 and PC, we were able to make the unit drop off-line within a few minutes.

Using a repeater hub and deliberately adding network traffic:
Using a hub, it is possible to flood the 10 Mbit Ethernet port on the 6200 with more data than it can handle. We found we could force it to drop offline by one of the following methods: copying a large file from a network server to the PC running 6200 Designer; or by opening a remote desktop connection to the PC running 6200 Desginer (sending data-intensive screen updates); and using Windows Update utility while starting a transfer.

Most Ethernet “hubs” today are actually switches. The difference between a repeater hub and a switch is that a repeater hub sends traffic received at one port out to all other ports, whereas a hub intelligently looks at who the packet is intended for and sends it out to only the appropriate port(s). This is important because with a repeater hub, it is possible to have a collision that subsequently requires a retry. This will not occur when using a switch. (It is actually quite difficult to buy a repeater hub today, since switches are a superior technology and are replacing hubs in most manufacturers’ product lines.)