Skip to content

Production Flow

This document describes the production testing and manufacturing procedures for the RTK Base.

Teltonika Router Configuration

Individual Credentials

TELTONIKA routers now come with individual username/password pairs: - Username: Always admin - Password: Unique per device

QR Code Information

Each router has a unique QR code containing:

WIFI:T:WPA;S:RUT241_B826;P:Tj4t0HPe;SN:6002452780;I:864081068760201;M:2097274CB824;U:admin;PW:Eq3y6HXk;B:031;

Fields:

  • S: SSID (unique per device)
  • P: WiFi password (unique)
  • SN: Serial number
  • I: Modem IMEI (unique)
  • M: Ethernet MAC address (unique)
  • U: Router admin username
  • PW: Router admin password (unique)

QR Code Storage

  • QR codes stored at: rtkbase.prod.yamabikorobots.net/rtr
  • Can be retrieved from manufacturer or scanned at warehouse entry
  • Important: QR code is inaccessible when modem is mounted in RTK Base

Production Test Flow

Prerequisites

  • RTK Base powered on
  • Ethernet connection available
  • Router/modem installed (if configured)

Test Sequence

  1. Hardware Initialization
  2. Base boots into production test mode
  3. LEDs show initialization pattern

  4. System checks all hardware components

  5. Router QR Code Retrieval (if applicable)

  6. Base attempts to fetch router QR code when Ethernet IP acquired
  7. Identifies router by MAC address
  8. Collects router/modem information

  9. Waits for QR code before modem test

  10. Ethernet Detection

  11. Ethernet spy collects MAC addresses (ARP)
  12. Verifies link status

  13. Confirms DHCP assignment

  14. Modem Test (if equipped)

  15. Validates modem connectivity
  16. Checks SIM card status
  17. Tests operator registration

  18. Requires successful QR code fetch first

  19. GNSS Test

  20. Verifies antenna connection
  21. Checks satellite acquisition

  22. Validates position fix

  23. LED Verification

  24. Tests all LED colors

  25. Verifies blink patterns

  26. Final Validation

  27. All tests must pass
  28. Results uploaded to portal
  29. Production flags set

Production Test Mode

Activation

The RTK Base can enter production test mode via:

  • Console command: start_production_test
  • MQTT command (production mode only)
  • Factory configuration

MQTT Production Interface

When in production test mode, the base publishes to:

UI Display Topics: - production/base/{SN}/UI/USER-TITLE: Title text - production/base/{SN}/UI/USER-TEXT: Instruction text - production/base/{SN}/UI/INTERACT: Interaction command

Test Results: - production/base/{SN}/UI/test-report: JSON test results

Interaction Commands: - OK,CANCEL,PASS: Button options - TEXT;name: Text input with default value - LIST;a;b;c: Selection list

Example Interaction

Topic: production/base/{SN}/UI/USER-TITLE
Payload: Hardware ID

Topic: production/base/{SN}/UI/USER-TEXT
Payload: Enregistre: dev-board-batch-0\nVoulez-vous le modifier ? o/n

Topic: production/base/{SN}/UI/INTERACT
Payload: OUI,NON

Device Location

To locate a specific base in the warehouse:

  • Send whereAreYou to production/base/{HW_ID}/cmd
  • Base will blink all LEDs in Christmas pattern for 10 seconds

Hardware Test Mode

Activation

start_hardware_test

Features

  • Low-level hardware validation
  • Tests individual components
  • Does not perform router/modem tests
  • Production test restarts automatically after hardware test

Error Handling

Router QR Code Failures

  • Base can proceed without QR code (fallback mode)
  • Modem test can run with reduced validation
  • Logs indicate QR code fetch status

Common Issues

  1. QR Code Not Found
  2. Check MAC address matches database
  3. Verify QR code was uploaded to server

  4. Retry QR fetch manually

  5. Modem Registration Failure

  6. Verify SIM card installed
  7. Check antenna connections

  8. Ensure operator coverage

  9. GNSS No Fix

  10. Verify antenna connected
  11. Check for obstructions
  12. Allow more acquisition time

Production Flags

Flag Values

  • 0: Normal operation
  • 1: Hardware test mode
  • 2: Production test mode

Setting Flags

# Via console
set_serial_number BRRB000021

# Via REST API
POST /system?prodflag=2

# Via MQTT
Topic: base/{SN}/system/post
Payload: prodflag=2

Post-Production

Final Steps

  1. Serial number recorded in NVS
  2. Hardware ID assigned
  3. Production test results archived
  4. Device ready for deployment

Verification

  • Check serial number: get_serial_number
  • Verify hardware ID: get_hardware_id
  • Review test results in portal

References