# General

The General settings window allows for configuring settings such as the device file of the temperature sensor as well as the modes for the I/O ports. In most cases, users should not alter any of the parameters in the General section unless instructed to do so by Phoenix LiDAR Systems.

![SpatialExplorer 4.X General rover settings interface](/files/-LTZT5pYES9aahkfjzVj)

![SpatialExplorer 5.X General rover settings interface](/files/-LpV3OWpkY6lU66IxVDZ)

## License

![SpatialExplorer License rover settings interface](/files/-LTZTuY0x-uXIa7wYh_N)

### License Key

Every system is configured and associated with a unique alphanumeric key that must be entered to associate the base station with the rover on the server.

## AutoStart/AutoScan

The AutoStart/AutoScan option will determine if the system and sensors will be manually or automatically activated.

![Enable AutoScan in SpatialExplorer](/files/-LTxnTH39YyM2j3-HM8i)

### System Startup

Determines when the navigation system will begin recording.

* Off: rover starts once SpatialExplorer connects
* Immediate: rover starts immediately after power up
* On LED Connection: rover starts as soon as a USB-LED is detected or SpatialExplorer connects.
  * Constant Green LED: rover system stable (GNSS, INS, Sensors)
  * 1 Red Flash: No camera data received by rover
  * 2 Red Flashes: No LiDAR data received by rover
  * 3 Red Flashes: No valid INS solution obtained by rover
  * 4 Red Flashes: No GNSS reception detected by rover

### Recording Camera / LiDAR data

Determines when the sensors (LiDAR/camera) will be activated.

* Manual: recording sensor data is controlled manually through SpatialExplorer
* Delayed: recording sensor data will start 5 minutes after GNSS reception is established
* Once Moving: recording sensor data will start once rover starts moving, then continues until shutdown
* Whenever Moving: recording Camera/LiDAR is active as long as rover moves

### Configure Satel Modem

Of importance in this section is the “Configure Satel modem on this port…” option listed under each I/O port. This option allows programming SATEL UHF modems directly through SpatialExplorer.

![Configure Satel UHF Modem interface](/files/-LTxoFIKnXEGGnxGVUHf)

#### Configure Pacific Crest Modem

Unfortunately if you have a Pacific Crest UHF Modem, you will not be able to program it directly from SpatialExplorer. To program a Pacific Crest UHF Modem, you must first insert the Pacific Crest USB Dealer Key into an available USB port on your computer. This will allow you to make changes to the UHF modem. Second, you must establish a connection to rover with SpatialExplorer. Third, you must open Pacific Crest's ADLCONF program on the same computer that is running SpatialExplorer. The last step is to connect to the Pacific Crest UHF Modem through ADLCONF using “localhost:5000” (no quotes).

The above procedure allows ADLCONF to connect to SpatialExplorer (as long as they are running on the same computer). SpatialExplorer then forwards the parameters defined in ADLCONF to the UHF modem transparently. This method works regardless of the method by which SpatialExplorer connects to the rover (ethernet, Wi-Fi, connection service).

### Minimum LiDAR Point Distance

This is the minimum distance between each displayed point. In most cases, we recommend setting this value to \~0.50 m to avoid any bandwidth/latency issues on the computer running SpatialExplorer.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs-6.phoenixlidar.com/spatialexplorer/acquisition/settings/rover-settings/general.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.