LoRa mesh communication
Evaluate how participating devices exchange local team information without depending on cellular data for the radio path.
LORA MESH · OFF-GRID COMMUNICATION DEVELOPMENT
DISCUSS A DEVELOPMENT PROJECT ↗
J28 · NEXT-GENERATION DEVELOPMENT PROGRAM
J28 smart LoRa mesh communication development program
J28 is a planned next-generation off-grid communication device direction for professional teams, distributors and product-development partners. It is not presented as a commercially available or certified product.
IN DEVELOPMENTNO PUBLIC PRICE · NO ONLINE PURCHASE · NO COMMERCIAL AVAILABILITY CLAIM
DEVELOPMENT RENDERING · NOT A PRODUCTION-UNIT PHOTOGRAPH
The J28 program explores a more self-contained smart PTT and LoRa mesh device while preserving the core requirement: local team communication beyond dependable cellular coverage.
A development direction, not a finished specification sheet.
The current J25 uses a paired smartphone as the main interface. J28 is being considered as a separate next-generation direction with more selected interaction available from the device itself after initial setup and binding.
Screen workflow, radio configuration, battery, enclosure, accessories, firmware, app dependency, compliance scope and production timing remain development-controlled.
J25 AND J28 ARE SEPARATE PRODUCT PATHS
Do not use development information as a current product quotation.
Buyer questionJ25J28
Commercial statusCurrent sample and B2B quotation pathDevelopment program only
User interfacePaired smartphone remains the interfaceMore direct device interaction under evaluation
Public FCC evidenceJ25 FCC ID 2BVP9-J25 and public reportsNo J28 FCC claim published
Public priceQuotation-controlledNo public price or checkout
Buyer next stepRequest a sample evaluationSubmit a development requirement
DEVELOPMENT TARGETS UNDER EVALUATION
Define the operating workflow before locking the hardware.
These are development targets, not final product specifications or guaranteed functions.
Selected screen-based workflows
Determine which PTT, message, location and alert tasks should be available directly from the device.
Initial setup and extended functions
Define which configuration, map, account or management tasks remain in the companion-phone workflow.
Professional team coordination
Translate route, terrain, team spacing and shift requirements into measurable prototype acceptance tests.
OEM and ODM scope
Align brand, enclosure, packaging, app, firmware, accessories and destination-market needs before design freeze.
Test and compliance planning
Build the verification, field-test, quality and market-document plan around the final configuration—not the rendering.
PROPOSED SYSTEM LOGIC · SUBJECT TO DEVELOPMENT
The buyer requirement determines the final interaction path.
- 01Initial setupDefine device identity, team, channel, configuration and any required phone-based administration.
- 02Operator actionEvaluate which PTT, message, location or alert tasks should be initiated on the device.
- 03Local radio pathPlan the permitted LoRa configuration and the participating device layout for the target market.
- 04Team receptionConfirm how the receiving operator views, hears, acknowledges or escalates the information.
- 05Field acceptanceTest the prototype on the actual route before any production-readiness decision.
DEVELOPMENT GATES FOR PROCUREMENT
Commercial availability begins only after the evidence is complete.
Requirement definition
Destination market, user roles, workflows, environment, team size, volume and customization scope.
Prototype definition
Hardware, firmware, interface, radio, battery, enclosure, accessories and development responsibilities.
Engineering verification
Functional, radio, power, mechanical, environmental and quality checks against written acceptance criteria.
Field evaluation
Real-route testing with the intended team layout, obstacles, movement and operator workflow.
Compliance review
Market-specific testing and documentation matched to the final hardware and radio configuration.
Production readiness
Approved bill of materials, quality plan, packaging, lead time, commercial terms and release decision.
DOCUMENT AND CLAIM BOUNDARIES
J25 documents do not certify J28.
The J25 product PDF, FCC ID 2BVP9-J25, FCC grants and J25 reports apply only to their identified model and scope. They must not be used as J28 certification, specification or commercial-readiness evidence.
Not yet published for J28
- Final technical specification
- Final production configuration
- Commercial release date
- Public certification or test-report set
- Approved public price or checkout
Required before release
- Design and configuration freeze
- Engineering and field validation
- Destination-market compliance review
- Quality and production-readiness approval
- Approved quotation and payment scope
OFFICIAL DEVELOPMENT RENDERINGS
Form-factor studies—not production photographs.
The images show the current visual direction only. Materials, controls, dimensions and final appearance may change.
HOW A B2B DEVELOPMENT DISCUSSION STARTS
Bring the field problem before discussing price.
J28 has no public checkout. Any feasibility study, engineering fee, prototype cost, tooling, certification budget or production price must be defined in a written development scope.
- Share the market and use case.Country, field environment, team roles and the communication problem.
- List required workflows.PTT, message, location, map, alert, device-screen and phone-management priorities.
- Define the commercial framework.Estimated volume, branding, development ownership, target timing and budget range.
- Review feasibility.ChatField confirms what can be evaluated, what remains unknown and the next engineering gate.
J28 questions from procurement and development teams
Is ChatField J28 available to purchase?
No. J28 is presented as a next-generation development program. This page intentionally provides no public price, add-to-cart button or online checkout.
What is the difference between J25 and J28?
J25 is the current phone-paired LoRa mesh communication product path for sample evaluation and B2B quotation. J28 is a separate development direction exploring more selected interaction from the device itself.
Are the functions on this page final J28 specifications?
No. They are development targets used to organize buyer requirements. Final functions, hardware, firmware, radio, battery, enclosure, accessories and timing require engineering confirmation.
Does FCC ID 2BVP9-J25 apply to J28?
No. FCC ID 2BVP9-J25 and the public FCC files identify model J25. They must not be represented as J28 authorization or compliance evidence.
Can an OEM or ODM partner influence the J28 direction?
A qualified partner can submit market, workflow, volume, branding and technical requirements for feasibility review. Acceptance of a development project depends on scope, resources, timing and commercial alignment.
How is a J28 development project priced?
There is no public J28 price. Feasibility work, prototypes, engineering, tooling, certification and production are quoted only after the written development scope and responsibilities are defined.
DEVELOPMENT INQUIRY
Start with the market, user workflow and field problem.
Tell us the destination country, operating environment, required functions, estimated volume and development target.
Product document portal
Download product information or review compliance evidence.
Use the public product PDF for initial buyer evaluation. Review model-specific certification scope before deployment in a destination market.
PDF
First-generation public product document
ChatField Product Introduction
Download the English product introduction currently available in Shopify Files.
Download PDF ↓ CERT Model-specific public evidenceFCC & Compliance Center
Review FCC equipment authorization evidence and the documented battery and transport scope.
Review certification evidence →