JPAM_NEO_Telemetry
Telemetry is an important part of JPam_NEO development. It records and displays real data from the timer during tests, helping us understand what happens in flight and validate each new version.
At this stage, it is mainly a diagnostic tool. It can be used to check RPM, study governor behaviour, monitor signal quality and compare the settings sent by the app with what the timer actually does.
The application has two main uses: live telemetry for bench tests and setup, and a log viewer for reviewing flights or tests afterwards.
The tool may support more JPam_NEO versions in the future. Telemetry data will always remain separate from motor control commands.
This does not mean that every JPam_NEO timer will include telemetry. Some versions may be offered with or without it, and some may require additional hardware to collect or transmit data. The decision will depend on whether telemetry provides a real benefit without making the timer unnecessarily complicated.
What it can do
- Display real data collected during tests.
- Show live telemetry during bench testing.
- Open and review previously saved logs.
- Analyse the behaviour of the motor, ESC and timer.
- Compare target RPM with the RPM actually achieved.
- Detect configuration or communication problems.
- Help validate new firmware before it is released as stable.
Current status
Telemetry is already part of JPam_NEO_V4 development. It began as an internal tool for validating the RPM governor and has grown into a general tool for reviewing flights and understanding system behaviour.
Future work may extend it to F2G_pro, V5 and other versions where flight data or diagnostics are useful. Simpler timers will continue to prioritise easy construction, configuration and operation.
The Windows telemetry application is provided as a support and validation tool. It is not yet a finished product or a complete user manual.
Download
Download the Windows telemetry viewer as a ZIP file. Extract it to a folder and run jpam_neo_telemetry.exe.
Windows security notice
The application is distributed as a ZIP file. Windows Defender or your browser may display a warning when you download or run it.
Before continuing, make sure the file was downloaded directly from this official website.
Application areas
The application has two main areas: Live Telemetry and Flight Log Viewer. Live Telemetry displays and records data while the timer is running. Flight Log Viewer opens .jpam files so that a flight or test can be reviewed later.
Top Menu Bar
File: Opens or closes .jpam files and exits the application.
Open JPam File: Opens a saved .jpam log without requiring a timer connection. The app checks the file before displaying it.
Close File: Closes the current log without exiting the application or stopping live telemetry.
View: Switches between Live Telemetry and Flight Log Viewer without clearing data or disconnecting the timer.
Tools: Reserved for general application settings.
Help: Shows the application version and basic usage information.
Mode Selector
Live Telemetry: Shows data received directly from the timer. It is useful for bench tests, firmware validation and checks before flight.
Flight Log Viewer: Opens saved .jpam logs and lets you compare the configured values with what actually happened.
Data Sources
Simulator: Generates sample data so that the interface and charts can be tested without physical hardware.
Serial Port: Reads telemetry through a USB connection between the XIAO and the PC. This is the usual option for bench testing.
XIAO COM Port: Selects the Windows COM port assigned to the XIAO.
Refresh Ports: Searches again for connected serial devices.
Wi-Fi: Receives UDP telemetry through the timer's own Wi-Fi network. With V4, this provides live telemetry without a USB cable. Connect the PC to the timer network, for example JPam_NEO_V4_XXXX.
Connection & Session Management
Connect: Connects to the selected source: serial port, Wi-Fi or simulator.
Listen Wi-Fi: Starts listening for telemetry when Wi-Fi is selected.
Start Simulation: Starts the sample data generator.
Disconnect / Stop Simulator: Stops the connection or simulator but keeps the collected data available for review or export.
Arm / Start: Prepares a recording session after the timer has been identified. Recording starts when the timer leaves the SAFE state.
Stop Session: Stops recording without disconnecting the timer.
Clear Chart & Data: Clears the charts and recorded data for a new session.
Save JPam Session: Saves the session as a .jpam file, including timer identity, firmware, settings, samples, states and error flags.
Connection & System Status Indicators
No Data: No source is connected or no data is being received.
Connected, Awaiting Identification: The connection is open and the app is waiting to identify the timer.
Timer V4 Identified, Ready to Start: A compatible timer has been recognised and the session can be prepared.
Session Armed, Awaiting Spool-up: The session is ready and waiting for the motor cycle to begin.
Active Testbench Session: Telemetry is being recorded.
Incompatible Device: The device could not be identified or its hardware or firmware is not supported.
Timer State Flags: Shows the current timer state, such as SAFE, START DELAY, SPOOL-UP, OPEN FLIGHT, FINAL WARNING, DESCENT, EMERGENCY STOP, GOVERNOR, DEGRADED or FAULT.
Degraded and Fault States
DEGRADED: The timer continues the flight cycle, but cannot maintain normal governor operation—for example, because the required command exceeds the safe ESC limit. Output remains limited and telemetry records the condition.
FAULT: A critical condition, such as excessive RPM, low RPM, lost RPM telemetry, a stalled motor or an invalid configuration, has caused a safety stop. The saved data can be reviewed afterwards to investigate the cause.
Practical difference: In DEGRADED mode the cycle and recording continue with limited output. A FAULT causes a safety stop and requires the setup or hardware to be checked.
Fault Warnings: Shows the error reported by the firmware, such as Under-RPM, Over-RPM, Telemetry Signal Loss, Motor Stall or Config Error.
Flight Parameters & Configuration Profile
Start Delay: Time before the motor starts.
Flight Duration: Programmed duration of the flight or bench test.
Target RPM: RPM that the governor is trying to maintain.
Motor KV: KV value of the motor.
Motor Poles: Total number of magnetic poles, used to convert ESC telemetry into mechanical RPM correctly.
Battery Cell Count: Number of LiPo or LiHV cells used.
Ramp Profile: Selected acceleration ramp: Slow, Standard or Rapid.
DShot Limit: Maximum DShot command allowed for the ESC.
Live data and telemetry fields
Target RPM: RPM requested from the governor.
Measured RPM: Actual motor RPM read through DShot telemetry.
Optical RPM: Independent RPM measurement from an external optical sensor, when fitted.
DShot Output Command: Digital motor command currently being sent to the ESC.
Valid Frames (%): Percentage of telemetry frames received correctly.
PI Governor Status: Shows whether the PI governor is active.
Governor Error: Difference between target and measured RPM.
PI Correction: Correction applied by the governor to reduce the RPM error.
Working Point (Base Throttle): Base DShot command established before the PI governor starts correcting it.
Proportional Term (P): Proportional contribution from the controller, shown in Development mode.
Integral Term (I): Integral contribution from the controller, shown in Development mode.
Final PI Output: Calculated PI command before the ESC safety limit is applied, shown in Development mode.
RPM Plotting & Chart Features
Real-Time RPM Plot: Live RPM chart for the current test.
Flight RPM Plot: Complete RPM chart from an opened .jpam file.
Target RPM Trace: Curve showing the requested RPM.
Measured RPM Trace: Curve showing RPM measured through DShot telemetry.
Optical RPM Trace: Curve showing RPM measured by the optical sensor.
Legend & Trace Toggles: Lets you show or hide individual curves.
Time Scaling & Zoom: Zoom controls for examining a section of the recording.
Hover Cursor Data: Shows the values at the cursor position.
Elapsed Time: Time of the selected sample.
CRC & Frame Loss: Diagnostic information about damaged or lost telemetry frames.
Flight Log Viewer Metadata
File Name: Name of the open .jpam log.
Format Version: Version of the JPam log format.
Created By: Version of the telemetry app that created the file.
Timestamp: Date and time when the session was recorded.
Total Duration: Duration of the recorded flight or bench test.
Sample Count: Number of samples recorded.
Session Selector: Selects a session when a file contains more than one test.
Stored Parameters: Shows the configuration saved with the log.
UI Visualization Profiles
Basic Profile: Shows target, measured and optical RPM, flight settings, cycle status and critical faults. Internal controller data remains hidden.
Advanced Profile: Adds DShot output, telemetry quality, governor error, PI correction and the base working point. It is useful for setup and bench testing.
Developer Profile: Shows internal controller data such as P and I terms, PI output, counters and timing information. It is intended for firmware development and governor validation.