Using NodeLogger for logging individual devices

Updated 2 weeks ago by Bryan Jones

First things first

Tip 'o the Hat to Michael Gay from NotABotYet for this clever little utility and for allowing it to be shared with the community.

NodeLogger is supplied by Telos Alliance with permission from NotABotYet as freeware. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

Instaling NodeLogger

NodeLoger is not an installer. It is just an executable that you can copy on to any Windows computer. You can download NodeLogger by clicking here.

Create a new folder under your Downloads or your Documents folder and copy this executable to this folder. Logs that are created are kept in the same location that you run the program from.

To run the program, just double-click on it.

Here are some examples of how you might use this.

Logging GPIO from a device.
  1. Enter the IP address of the device to log GPIO from. This could be a Node, a Driver, Z/IP One, iPort or ANY device that supports Axia GPIO. In this example we will use an xNode with two GPIO ports.
  2. Enter the Server Port. All GPIO is on port 93
  3. Check the "Log GPIO Activity?" box. In order to log GPIO activity, you must subscribe. Checking this box subscribes to the GPIO Changes.
  4. Supply a friendly name for the Log File Prefix. This will be used to produce log files with meaningful names.
  5. Click the Connect button. You will see some initial connection information displayed in the Window.
  6. At the direction of Axia you can send commands to the device using the Send option.
  7. The location and name of the logs being created are displayed here. Note that a new log is created for each day. Logs are just plain text and can be read with any Text editor. NotePad++ or VisualStudioCode are free ones that we like here in Support.
You can run multiple instances of NodeLogger at the same time. Click on the NodeLogger executable again and configure it to log from your next device.
Logging Console messages.
  1. Enter the IP address of the console.
  2. Enter the Server Port. All console messages from Quasar, Fusion, and Element is on port 4010.
  3. Do NOT Check the "Log GPIO Activity?" box. Unlike GPIO, port 4010 requires no subscription.
  4. Supply a friendly name for the Log File Prefix. This will be used to produce log files with meaningful names.
  5. Click the Connect button. No initial messages are shown. Any messages from the console will be logged. There is no way to filter messages. All console changes are sent.
  6. At the direction of Axia you can send commands to the device using the Send option.
  7. The location and name of the logs being created are displayed here. Note that a new log is created for each day. Logs are just plain text and can be read with any Text editor. NotePad++ or VisualStudioCode are free ones that we like here in Support.

Let us know how we can help

If you have further questions on this topic or have ideas about how we can improve this document, please contact us.


How did we do?


Knowledge Base

Powered by HelpDocs