CHATFIELD
ChatField J25 adds a local radio and mesh communication layer to the smartphone your team already understands.
The phone is the control interface. J25 is the paired communication terminal. Bluetooth carries commands and received data between them. LoRa carries local team traffic between J25 devices. When the direct path is not sufficient, participating J25 nodes can help relay communication through the mesh.
This architecture is designed for equipped teams operating beyond reliable cellular coverage. It does not turn the phone into a satellite phone and it does not create public internet access. For buyer planning, J25 should be described as a phone-paired LoRa mesh communication device for no-cell-service team coordination, with PTT voice, text and voice messages, team location and offline maps.
ONE COMPLETE COMMUNICATION PATH
- Action on phoneA user starts PTT, sends a message or shares team data in the app.
- Bluetooth linkThe paired phone passes the local command and data to its J25.
- J25 terminalJ25 provides the radio connection between the phone workflow and the field network.
- LoRa linkThe J25 sends local team traffic over the configured radio link.
- Mesh pathA participating node can support relay when the configured network and field layout allow it.
- Receiving J25The destination teammate's J25 receives the local team transmission.
- Back to phoneBluetooth returns the received information to the teammate's phone for playback or display.
Range and relay behavior in plain language
When two J25 devices operate across open terrain such as plains, open line-of-sight routes or areas with limited hills, ideal communication distance can reach up to 10 km. In real projects, ChatField treats around 5 km as the urban-obstructed field-test distance. A configured mesh can use up to two participating J25 relay nodes where their positions create a useful path. Terrain, buildings, vegetation, interference, antenna position and how the device is carried still decide the final result.
The four technical layers buyers should understand
Smartphone app
The compatible phone remains the familiar operating screen for PTT voice, text and voice messages, team location, offline maps and the local SOS workflow. Team members do not operate J25 like a conventional walkie-talkie held to the mouth.
Bluetooth pairing
Bluetooth creates the short-range data connection between one phone and its paired J25. This separates the user interface from the radio terminal: the phone handles interaction while J25 handles the off-grid field link.
J25 and LoRa
J25 carries local communication between equipped users through a LoRa radio link. The field network is independent of a cellular tower or Wi-Fi access point, subject to the confirmed product configuration and local radio rules.
Participating mesh nodes
Each equipped teammate adds a J25 node to the local network. Mesh operation can create a multi-node path instead of relying only on one direct point-to-point connection. The useful path still depends on node positions and real field conditions.
What travels through the system?
The same architecture supports several team workflows, but each begins on the paired phone, moves through J25 and returns to the receiving user's phone.
Talk from the phone interface
The user initiates PTT in the app. The paired J25 carries the local transmission across the configured LoRa mesh path, and the receiving phone presents the communication to the teammate.
Send information that can be reviewed
Team members can exchange text or voice messages through the same phone-to-J25-to-mesh path, without requiring the public mobile network for the local communication link.
Exchange position information
Location data can be shared between equipped teammates so the phone interface can support local team awareness. The final positioning source and behavior must match the confirmed J25 configuration.
Use local tools beyond coverage
Offline maps are prepared for use on the phone without downloading live map tiles in the field. The local SOS workflow alerts equipped teammates; it is not a connection to public emergency dispatch.
WHY MESH COMMUNICATION MATTERS
More than a direct link between two devices.
In a point-to-point link, the two endpoints must complete the radio path directly. In a mesh communication network, participating devices can contribute another path through equipped nodes. For a professional buyer, this means team layout matters as much as a headline distance figure.
- Adding a device does not guarantee coverage; its location must contribute a useful path.
- Terrain, structures, vegetation, antenna position, interference and device placement can change performance.
- A route-based field test is more meaningful than one stationary open-area distance test.
What the system depends on—and what it does not provide
Required for operation
- A compatible phone with the ChatField app and prepared offline content where required
- One correctly paired J25 for each equipped teammate
- A confirmed radio configuration suitable for the destination market
- Sufficient power, appropriate carrying position and a tested node layout
- A representative field trial using the real route, team spacing, 5 km urban-obstructed range checkpoints and relay-node positions
Not part of the promise
- No public internet connection is created by the local LoRa mesh
- No universal range is guaranteed across every terrain or building
- Local SOS is not public emergency dispatch or satellite rescue service
- ChatField does not replace mandatory licensed, maritime or life-safety systems
- One certification or configuration must not be assumed to cover every market
How a procurement team should evaluate J25
- Define the market: destination country, intended use and required compliance evidence.
- Map the operation: route, terrain, structures, team size and expected spacing.
- Confirm the product set: phone compatibility, J25 configuration, accessories and document revision.
- Test the full workflow: pairing, PTT, messages, location, offline map use and the local SOS process.
- Record the network layout: device position, obstruction, interference and the nodes present at each critical point.
- Approve against acceptance criteria: use the buyer's real operating requirements before samples or volume deployment.
Buyer questions about the technology
Does ChatField J25 work when cellular service is unavailable?
The local phone-to-J25 and J25-to-mesh communication path is designed for equipped teammates beyond cellular and Wi-Fi coverage. The phone still needs to be prepared, paired and compatible, and the field network must be tested in the intended environment.
Is J25 used like a handheld walkie-talkie?
No. The phone remains the main interface for PTT, messages, maps and team information. J25 is carried as the paired communication terminal rather than held and operated like a conventional walkie-talkie.
Is LoRa mesh the same as satellite communication?
No. ChatField uses a local radio network between participating J25 devices. It does not use a global satellite communication service.
Does every message always use a relay?
No. The path depends on the participating nodes, configuration and field layout. A direct local path may be available; mesh relay becomes relevant when the network can use another participating node.
Why is there no single guaranteed range on this page?
J25 can reach an ideal communication distance of up to 10 km in open terrain such as plains, open line-of-sight routes or areas with limited hills. Procurement teams should use around 5 km as the urban-obstructed field-test distance and verify the planned route under representative conditions, including terrain, obstruction, antenna position, interference, device placement, relay-node layout and permitted configuration.
Read the mesh communication guide · Review off-grid deployment · Review J25 specifications · Request compliance documents