Submodule Troubleshooting
View some basic troubleshooting steps when activating Sonoran CAD submodules.
Last updated
Was this helpful?
View some basic troubleshooting steps when activating Sonoran CAD submodules.
Last updated
Was this helpful?
Sonoran CAD's core includes powerful built-in commands. These commands are entered into your server console.
Ex: A may ask you to send detailed logging information to them. They will give you the specific ID number to enter. (ex: 123)
Entering sonoran support 123 in your server console will send your plugin configuration directly to our support application.
Command
Description
sonoran debugmode
Enables detailed debug logging
sonoran info
Displays version and config information
sonoran support <NUMBER>
The NUMBER parameter will be provided to you by a support team member.
Ex: sonoran support 123 sends us your plugin information for help.
sonoran plugin <NAME>
Displays plugin information
Ex: sonoran plugin callcommands
Your community's subscription may have expired and failed to renew. Do a quick check on your to make sure your community version includes the submodule you are trying to install.
Be sure to follow the and guides thoroughly, depending on the specific submodule you are trying to activate.
Make sure you have not forgotten to enable the submodule in the plugin config file!
Enter sonoran info into your server console.
If the submodule you are having trouble with is listed as DISABLED, you may have forgotten to enable it in the submodule configuration.
The SonoranCAD core includes a powerful debug mode. Enable this by entering sonoran debugmode into your server console.
Debug mode will print out additional error information and JSON data for all API calls or push events.
For plugins that require your individual CAD user account to have the API ID set (live map, unit locations, panic, etc.) you can view this data in the console output.
The image below shows an API Call being made from the server to Sonoran CAD. This API call is type UNIT_LOCATION and includes all the data necessary.
If you're still having trouble, our dedicated support team is here to help.
Your framework or plugin config is not correctly named config.json. Ensure that is has been spelt correctly, is not config.json.json, etc.
You may need to open the file in a text editor to more easily see the file extension, and ensure that it is correctly named as config.json.
Sends important information for purposes.
Ensure you have set your using the value from the .
Ensure the APIID listed in the API call matches the .
Your community ID and API key is also listed in the debug API call information. Be sure that the are correct.
.
