RS-485 converters connected to a real RS-232 COM port on your PC do best in running the MS/TP stack. Although we have tested USB "dongles" and found they do "function", they perform poorly and result in a lot of network dropouts. (The ideal solution is actually a hardware RS-485 card plugged into a desktop PC.)

Follow the startup sequence shown on the startup page if you haven't already. This will get you through the initial "get connected" phase. IMPORTANT: A significant percentage of support calls come from people who simply did not read or follow this page!

Using the XP Converter? What do the LEDs tell you? The yellow LED should be on always indicating power is present. The green LED tells you communications are coming from the BB485XL. Diagnostic: Disconnect the PC from the XP converter, and power up the BB485XL. If the BACnet MS/TP network is wired correctly and power is on at the BB485XL, the green LED should be on/flickering (without the PC connected at all). The red LED tells you communications are coming from the PC. Diagnostic: Disconnect or power off the BB485XL, but connect the PC. Start the BAConfig.exe program, select the appropriate COM port, and click the Init Stack button. The red LED should be on/flickering (without the BB485XL connected at all). If you do not pass the above two diagnostics, stop here, and sort out the wiring problems before proceeding. You cannot proceed to configure the device without at least passing the above two tests. Once passing the above two tests, reconnect both the PC and the BB485XL. All of the LEDs should be mostly on (or at least flickering rapidly) if you are communicating. MAKE SURE you are connected to the BACnet port when attempting to use the BAConfig tool. The BACnet port is the NET connection next to power. The connector on top is LonWorks, and you cannot configure this device via LonWorks.

Trouble shooting the LonWorks device

You can communicate with the gateway without any LonWorks device present. To test all the way through, especially if you are uncertain of the LonWorks device, it is a good idea to start by installing the node using the Install request and service pin. If installation appears to be successful, use the Wink request to see if you get a response from the node.

Reliability codes, which indicate LonWorks errors, are the same for all types of BACnet objects in the Babel Buster 485XL gateway. These codes are as follows:

BACnetReliability ENUMERATED: normal(0) Vendor specific: no response, device query failed (64) no response, NV fail (67) configuration property fault (80)

Trouble shooting the BACnet device

Error codes returned via BACnet consist of an error class and code. The most common errors are listed below with class in parenthesis followed by code. Some applications will interpret these for you and provide a text description.

	(property) code 9	Invalid data type
	(property) code 32	Unknown property
	(property) code 37	Value out of range
	(property) code 40	Write access denied
	(property) code 42	Invalid array index
	(client) code 30	Timeout
	(client) code 31	Unknown device
	(object) code 31	Unknown object
	(service) code 7	Inconsistent parameters
	(service) code 10	Invalid access method
	(service) code 29	Service request denied
	(abort) code 4	Segmentation not supported
	(reject) code 4	Invalid tag
	(security) code 26	Password failure
	(resource) code 0	Resource error – “other”