What can the second Ethernet port on the Niagara Ax JACE-2 and JACE-6 be used for?

Currently the only drivers that can be configured to use the second Ethernet port are Bacnet, ModbusTCP and EibIp.

The JACE does not act as an Ethernet router or switch, meaning it does not allow TCP/IP traffic to pass from one port to the other.

The second Ethernet port can be used to isolate a BACnet Ethernet or IP network from the primary LAN. All BACnet devices would be connected on the network segment that was connected to the secondary Ethernet port on the JACE. BACnet points that are proxied in the station could then

be viewed or commanded through graphics that are served up by the webService via the primary

Ethernet port.

The Niagara Network and the webService will be available on both network interfaces. With BACnet, you select which network interface to use on the link settings of the IP-port and/or Ethernet-port object under the BACnet network. With Modbus TCP the IP layer decides which network interface to use based on the IP address assigned to the Modbus TCP Device Object.

The second port must be on a different subnet. The second subnet cannot also have a default gateway - so you will be limited to one subnet on the second network interface.

How to set the BACnet server to TRACE in Niagara Ax

Right-click on the station in the nav tree and select "Spy".

 Then click "logSetup" to go to the screen for configuring logs.

Here you can set each of the various logs in your station to different levels of output - from None (no output), Error (only ERROR messages), etc. up to Trace (which prints diagnostic-level output useful for identifying problems when troubleshooting ).  The default level for all logs is Message.  Click the cell in the Trace column, and the row labeled "bacnet.server".

Then the station output will display trace-level messages for the bacnet.server log.  From this you should be able to see where the requests are coming from and configure the offending device properly.  In order to avoid unnecessarily burdening the station, you should turn trace debug off (by setting back to Message) when you are finished.

Note that log settings DO NOT persist across station restart, unless you click the Save To File link at the top.  This will save them to the /lib/log.properties file, which is read upon station startup to initialize the log levels.