Solutions
The Phyling embedded measurement chain
Sensors, modules, data loggers, network, cloud and API: we master the whole embedded measurement chain, from the custom sensor to the application, and it stays open to all your sensors.
How the Phyling measurement chain works
1The Maxi-Phyling
At the heart, the Maxi-Phyling: your versatile data logger. Built-in IMU and GPS, waterproof, it records at high frequency and synchronises all your sensors.
2It captures the movement
A Phyling force sensor (crankset, PI3D, studs…) plugs into a Mini-Phyling, which sends the force data to the Maxi over Bluetooth. A Nano-Phyling or a Mini-Phyling GPS can also send it their motion and position data.
3It sends your data
The Maxi transmits over Wi-Fi, through any field or lab network (Starlink, 4G router, phone hotspot), to the Phyling cloud: you follow everything live in the app.
4To your applications too
With the API, your field data also flows to your tools, your AI, your partner platforms… or on air.
5Live for media
For live coverage, the Phyling-LTE streams your data over 4G and Wi-Fi in parallel: the signal is never lost, ideal for media and broadcasts.
6The lab for R&D
In the lab, the Maxi-Lab adds 8 analogue channels, I2C inputs and synchronisation with your systems (Qualisys, Vicon, AMTI). The Maxi-Hub does the same and also hosts the Phyling app, to work locally, without internet.
7All your sensors
And the ecosystem is open, at the input as at the output: off-the-shelf Bluetooth and ANT+ sensors, watches and bike computers, heart rate, force and pressure sensors, lab systems… and all your applications through the API. Your sensor isn’t listed? We integrate it.
Phyling devices
A device for every use
The data loggers and modules that make up the measurement chain, from the field to the lab. Detailed specifications are in the technical documentation.
Field data logger
Maxi-Phyling
Built-in 9-axis IMU and 10 Hz GPS, Wi-Fi and Bluetooth, IPX7 waterproof. It synchronises all your sensors.
Live data logger
Phyling-LTE
Real-time streaming over 4G LTE-M and Wi-Fi in parallel, IMU and multi-band GPS, automatic catch-up after an outage.
Lab data logger
Maxi-Lab
8 analogue channels, I2C inputs and synchronisation with your lab systems.
Data logger + local app
Maxi-Hub
The Maxi-Lab inputs, plus the Phyling app hosted locally to work without internet.
Module
Mini-Phyling
20 g, 9-axis IMU and 6 analogue inputs for your wired sensors, Bluetooth and SD card.
Module
Mini-Phyling GPS
25 g, 9-axis IMU and 10 Hz GNSS in an IPX8 waterproof case.
Module
Nano-Phyling
6 g, 9-axis IMU at 200 Hz, USB-C and Bluetooth, standalone or with a Maxi.
Frequently asked questions
How long does a proof of concept take?
Thanks to our reusable bricks, a proof of concept usually takes 4 weeks. The timeline depends on the chosen sensors, the level of embedded processing and the mechanical constraints.
What accuracy can be achieved?
Accuracy depends on the sensor and its calibration. As a guide, force measurements are typically within ±1% of full scale with a suitable calibration. We set the tolerances and the test protocol together.
Can you integrate our existing sensors?
Yes. We adapt boards and protocols to integrate your equipment (strain gauge bridges, IMUs, temperature, CAN…) while keeping the target accuracy. Your sensor is not compatible yet? We integrate it.
Which sampling rates?
When recording locally, up to several kHz depending on the device and the number of channels. When streaming, Bluetooth suits modest rates (typically 100 to 200 Hz), Wi-Fi higher rates and LoRa low-frequency telemetry.
Where is the data stored?
Locally (SD card or memory), on a Maxi-Hub without internet, or in the Phyling app cloud. In every case you remain the owner of your data, with CSV and PDF exports and an HTTP and MQTT API.
Which software integrations do you offer?
Web app, Python scripts, Nolio and MTraining connections, HTTP, MQTT, CAN and Ethernet. We also build custom connectors.
A use case in mind?
Tell us about your idea: together we choose the right sensors, data logger and way to deliver the data. A proof of concept usually takes 4 weeks.