Zephyr ANT+ Heart Rate Scanner

@MuhammadUzair16

Hi I am an embedded systems engineer with over 16 years of experience. I have extensive experience with nRF52/nRF52840 firmware, Zephyr/Nordic SDK projects, C radio drivers, watchdogs, queues, and products that need to run unattended for long periods. For your Nice!Nano scanner I would first review the current main.c and confirm the ANT+ channel/profile setup, then fix the receive path so the heart-rate pages and RSSI are logged reliably. After that I can add a watchdog, buffering/processing queue, drop-out handling, and clean diagnostics so you can see packets during testing without making the firmware fragile. I will keep the code commented and include a short README for rebuild/flash steps. One thing I would like to confirm is whether you already have the required ANT/ANT+ network/profile details in the code, or if the current implementation is trying to capture raw radio packets. Please contact me to discuss details.

@nintysix96

Rough estimates on the price and timeline above - real numbers come after we look at your existing code and talk through what you need. Your nRF52840 is flashing and booting fine, which means the hardware and toolchain are solid. The gap is in the ANT+ channel configuration - getting the Zephyr ANT stack to actually open a slave channel on the right network key and device type for a HR strap, then parsing the incoming broadcast pages correctly. You want this running 24/7 as a passive scanner, so stability is just as important as getting the first packet through. Here's how we'd approach this: - ANT+ channel setup: Review your main.c for the channel configuration - network key, channel type, device profile (HR = device type 0x78) and period. This is usually where the silence comes from. - HR data parsing: Decode the ANT+ HR broadcast pages (Page 0/4) to pull out the heart rate value and attach RSSI from the radio layer so you have both in each log line. - Stability layer: Wire up Zephyr's watchdog (wdt_feed in the main loop), add a k_msgq or k_fifo for packet processing so the radio callbacks stay lean, and handle channel drops with an automatic reopen. - Diagnostic logging: Clean LOG_INF output per packet with timestamp, HR value and RSSI so you can confirm reception in real time over RTT or UART. - README and comments: A short rebuild-and-flash guide plus inline comments on the non-obvious Zephyr ANT API calls so the code stays maintainable. Once we've had a quick look at your main.c and the board photo, we can send a proper written proposal with a firm price and delivery time. Want to jump on a quick call this week, or just drop the file here and we can give you an initial read on what needs fixing? Best, 96 Studio

@CliveMSoftware

I've shipped multiple Zephyr projects on nRF platforms and have hands-on experience with ANT+ packet parsing and radio configuration. I'll debug your main.c to identify why the ANT+ scanner isn't capturing strap broadcasts, implement robust channel scanning with proper radio state management, add watchdog timer and processing queues for bulletproof 24/7 operation, and build in real-time diagnostic logging so you can monitor RSSI and heart rate packets during testing. You'll get clean, well-commented code, a working device tree configuration for your Nice!Nano board, and a README covering build and flash procedures. I can start immediately and deliver a stable, production-ready firmware in 4 days.

@Lazarone1

hi! there... i understand this project needs both stable low level ant+ packet handling and long running reliability on the nrf52840 under zephyr. one important issue is correctly configuring the ant stack and parsing broadcast payloads with rssi in zephyr v3.3.1, and another is ensuring the scanner can recover cleanly from signal drops or runtime stalls during 24/7 operation. i have strong experience with embedded c, nrf52 development and wireless protocol debugging, and i can provide clean well documented zephyr based code with watchdog handling, reconnect logic and real time diagnostic logging. thanks.