How to view platform info with a browser and not login to the Niagara Ax station.

You have to know the platform user and password.

http://<ipAddress>:3011/platformInfo - this view provides much of the same information that is available through Workbench when looking at the Platform Administration view.

http://<ipAddress>:3011/qnx - this view is only available for JACEs which use the QNX operating system. This view provides much of the same information that is available through Workbench when looking at the spy pages.

How can you tell if Niagara Ax JACE is overloaded?

When using Workbench, right-click on the connected station in the nav sidebar and select View -> Resource Manager.

• The CPU usage should be less than 80% on a continuous basis.
• The heap.used should be less than 75% of the heap.max value. Execute garbage collection before evaluating the heap.max value by right-clicking on the connected station in the nav sidebar and selecting Spy -> util -> gc.

• For a SoftJACE ensure that the resource.total is less than the licensed resource limit. SoftJACEs are licensed for either a 10,000 KRU or 30,000 KRU limit. If actual station resources exceed 110% of the licensed limit for a SoftJACE, the station will fail to start.

If running AX 3.1 or later, when using Workbench right-click on the connected station in the nav sidebar and select 'Spy'. On the Remote Spy page select 'platform diagnostics' and then 'fd usage'. This displays a list of processes and the number of open file descriptors for each.

QNX-based JACE controllers are limited to 1000 open file descriptors. File descriptors include but are not limited to directories, files, histories, and socket connections. If the number of open file descriptors exceeds the limit, the station will behave erratically such as misreporting available file space, missing history collections, etc. A maximum of 800 histories per station is recommended to avoid exhausting the pool of available file descriptors.

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.