GUIDE: Troubleshooting and Diagnostics with Chowmain RTI Drivers
How to Fetch Logs for RTI
To fetch the logs we need to do a little bit of config for the drivers first.
Driver Config
For each driver you want to log, go to the Driver Properties and look for the Debug Settings section at the bottom.
To Enable the logging we need to set the Enable Trace to active and make sure the log level is set to Debug. Cloud logging is option, but if there is a chance that there may be internet issues that can be enabled as well.
If you have Project Agent installed, please make sure to enable the logging on that as well.
To collect the logs you can use either TraceViewer, if you have it, or XP Diagnostics. The current onboard diagnostics is not suitable for this logging because it can't capture anything at startup.
Traceviewer
Please run TraceViewer and connect it to the processor first. If your processor shows in the devices list, select it and hit OK.
If the processor doesn't show in the devices list, type the IP manually and hit Use Manual.
NOTE: if you enter a manual address and hit OK, it willtry and connect to 0.0.0.0 and you wont get any logs. If you cee in the top menu card Connected - 0.0.0.0, then choose disconnect from the menu, and go through the connection set again, but this time hit Use Manual.
Once you are connected (and have configured the driver to enable logging), re-load the project.
See below for how log to log and what we need in the what to log section.
XP Diagnostics
The current onboard diagnostics is not suitable for this logging because it can't capture anything at startup, so instead we need to use the older version of XP Diagnostics. If you don't have it, you can download it here -> https://driverstore.rticontrol.com/driver/xp-diagnostics
To use it, you must first disable the Onboard Diagnostics, by making sure the Enable Onboard Processor Diagnostics System is unchecked.
Now you can install and use XP Diagnostics.
Add XP Diagnostics to your project and reload. The do the following
- Go to the XP Diagnostics page (its the processor IP address and can be accessed directly in a browser) and set the level of the driver to High.
- Hit save levels, then reload your project again
NOTE: DO NOT close XP Diagnostics, we need details from the start up process so you need to have XP Diagnostics running when you reload your project. It will automatically reconnect once the project has finished loading. Connecting after the project has loaded means we miss all the licencing, version and start up info which is critical in helping address your issue.
- Once you have some entries in the logs, hit Get Copy to save the logs
What to log
Regardless of which logger you use, there are a few things we need to see in the logs to help. The main thing is time. the drivers can take up to 10 mintues to send licence information, so make sure to capture at least 10-15 minutes of logs before saving.
Ideally, you should see something like this in the logs, which tells us that project agent has heard from the driver. If you don't see this please leave the logs running for at least 15 minutes before saving and sending.
2450116 07:53:27.328 172.16.1.121 (Project Agent) [DEBUG] (update_driver) DRIVER_LIST: [{"port":30686,"name":"rti-pushover","last":1758266611000...
The other important step is to try the commands you have having trouble with. Before you do this, give the driver a few minutes to completely load and get through hits setup phase. For some drivers this happens quickly, but for more complex driver it can take several minutes. If you keep an eye on the logs you will see that at startup there are many commands being sent, but after a few minutes it drop off completely. This is the time to try the commands that are failing. Please make sure to try 2 or 3 at least, so we have something to chase.
How To send the Logs
The absolute best way to get the logs to us is in a ticket. If you have an open ticket, just reply to that and attach the logs. If you don't have an open ticket, go to our website, click on Technical Support in the left menu, then Submit a Ticket. Please make sure to let us know what driver you are having an issue with and use the Attach a File option at the bottom to send the log.
Related Articles
GUIDE: Troubleshooting and Diagnostics with Chowmain Control4 Drivers
You may need to do these steps on both the affected driver, and any subdrivers or master/agent drivers Things to Try first Check the system is running the latest versions of all drivers. Ensure you're using a supported version of the Control4 OS. The ...GUIDE: Troubleshooting and Diagnostics with Chowmain URC Drivers
Overview These instructions walk through how to use the URC logging tool built into Accelerator 3. The instructions are written for using a project created in Accelerator 3 using tcm3 modules. Module Configuration Before you connect and look for logs ...HOW TO: License Chowmain RTI Drivers
This is a licensed driver and requires you to purchase a license for its continued use. Licenses can be purchased from the Chowmain Software Website. All Chowmain drivers come with a complimentary 90-day trial period, so you can install and test ...GUIDE: Beta Testing Chowmain Crestron Home Drivers
Overview This document covers the manual installation, testing and removal of Crestron Home beta drivers. If you want to replace the driver from the online database, or if it's not currently there, you can manually install the driver. There are a few ...HOW TO: License Chowmain URC Drivers
This is a licensed driver and requires you to purchase a license for its continued use. Licenses can be purchased from the Chowmain Software Website. All Chowmain drivers come with a complimentary 90-day trial period, so you can install and test ...