> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/transportation/getting-started/page-1.md).
# Get Started with the Transportation Gateway
Learn how to configure and install Verkada’s KGX61 Ruggedized Transportation Gateway
Verkada’s KGX61 Transportation Gateway connects Verkada products for transportation use cases. It natively integrates with Verkada devices to simplify setup, enable remote troubleshooting, and optimize data usage.
The KGX61 automatically recognizes connected Verkada devices, so you don't need to enter serial numbers or scan QR codes during setup. You can monitor data usage for each connected device and receive alerts when a device goes offline.
Key features include:
* View gateway status and GPS location
* Power the full Verkada camera line with 10 PoE ports
* Access a transportation-specific experience in Command
* Remotely wake the gateway to collect video when the vehicle is turned off
* Automatically recognize connected Verkada devices during setup
* Collect vehicle telemetry through OBD-II and J1939
***
### Set up Verkada Command
{% hint style="danger" %}
* You must create a [Verkada Command account](https://command.verkada.com/register) to activate and configure a KGX61-HW.
* You must be an Org Admin to configure a KGX61-HW.
Learn more about [Roles and Permissions for Command](/command/users-and-permissions/roles-and-permissions-for-command.md).
{% endhint %}
***
### Set up the hardware
Follow the steps to set up and install (wire and mount) the [KGX61](https://docs.verkada.com/docs/KGX61-ruggedized-transportation-gateway-install-guide.pdf).
***
## Troubleshooting
If a Verkada KGX61 is installed but not behaving as expected, start with a power cycle. Then use the Status LED to choose the next check.
### Power cycle the KGX61
{% hint style="warning" %}
The KGX61 has no external power switch and is powered by the vehicle electrical system. It does not accept Power over Ethernet (PoE) input. Most post-installation issues come from vehicle power, the ignition sensing circuit, or connectors loosened by vibration.
{% endhint %}
{% stepper %}
{% step %}
**Turn the vehicle ignition off.**
{% endstep %}
{% step %}
**Wait for the Status LED to go dark.**
{% endstep %}
{% step %}
**Turn the ignition back on.**
{% endstep %}
{% endstepper %}
If the gateway does not respond to an ignition cycle, press the Reset button behind the subscriber identity module (SIM) and Secure Digital (SD) card door. Loosen the security screw with the T10 Torx L-key to open the door.
### Check the Status LED
* **Solid orange**—The gateway is booting up.
* **Flashing orange**—The gateway is updating firmware.
* **Solid blue**—The gateway is running and online.
* **Flashing blue**—The gateway is running but not communicating with Verkada Command. Continue with Gateway is running but offline.
* **No light**—The gateway is receiving no power. Continue with Gateway has no power.
If a connected camera has no power, see Camera has no power.
***
## FAQ
### Gateway has no power
Is the vehicle ignition on?
The KGX61 remains shut down when the ignition-sensing circuit is not energized.
Has the fuse blown?
Check the 15 A fuse on the gateway power circuit.
Has the terminal block loosened?
Confirm the direct current (DC) input terminal block is fully seated. Vehicle vibration can loosen a connector over time.
Is the vehicle supplying stable voltage?
Measure voltage at the device, not at the battery. The KGX61-HW accepts 10–20 V DC and 20–30 V DC. Voltage sag under a high accessory load or during cranking can drop the supply below the minimum input voltage and reset the gateway.
***
### Gateway is running but offline
Is the vehicle parked somewhere without coverage?
Cellular signal is poor inside depots, maintenance bays, and parking structures. Confirm that the gateway comes back online after the vehicle moves to a more open location.
What do the 5G signal strength LEDs show?
All four LEDs lit means the signal is optimal. Fewer lights mean a weaker signal.
Is the SIM detected?
* **Solid white**—The SIM is detected.
* **Flashing white**—The SIM is detected and running.
Have the antenna connections loosened?
At the gateway, confirm the red-labeled coaxial (coax) cables are seated on the 5G SubMiniature version A (SMA) connectors. Retighten them with a 5/16 in or 8 mm SMA torque wrench.
Hand-tightened SMA connectors loosen under vibration. This often appears weeks after you install the gateway.
Is the antenna or its cabling damaged?
Inspect the roof penetration for seal damage. Check the coax where it passes through the roof panel for chafing or crushing.
***
### Camera has no power
Is the enclosure running hot?
The total PoE budget is limited to 120 W when the ambient temperature exceeds 122°F (50°C). In warm weather, a gateway in direct sun or near a heat source can cross this threshold and stop powering cameras that run normally when the gateway is cooler.
What do the RJ45 LEDs show for that port?
Check the link and activity LEDs on the affected PoE port.
* No LED / no link: the port isn't delivering power or detecting the camera. Check the cable and connectors, and confirm the camera is plugged into a PoE-capable port.
* Link/activity but the camera still has no power: the port may be passing data without supplying PoE. Check the gateway's PoE budget and move the camera to a known-good port.
Are the Ethernet cables secured?
Dress and secure the cables to the cabinet or chassis. Unsecured cables let vibration damage the connector pins.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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 following URL with the `ask` and `goal` query parameters:
```
GET https://help.verkada.com/transportation/getting-started/page-1.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.