Femtofox Project

Configuration guidelines, power usage testing, RF transmit power testing

Update Feburary 25, 2025

My first round of tests are wrapping up. I am looking for a good 900mhz source with a known output level (I have one reserved in the next few days), until then take the TX power results with a grain of salt (+/- 1dBm). Consumption results should be solid, but for now I’d recommend a 5V supply until we verify the output levels off of 3V3. For anyone in the EU looking to stay under 500mW / 27dBm TX power, 18dBm appears to be at about 26.9dBm out, so somewhere in the 16-18dBm range should work well depending on your risk tolerance ;P

You can see my test results here :)

Femtofox is a project to create a Linux Meshtastic node based on the low cost Luckfox Mini SBC.

Configuration

Requirements

  • A femtofox board
  • A microSD card
  • A disk imaging tool, such as Rufus or Balena Etcher
  • Some sort of SSH+Serial client like PuTTY
  • A Meshtastic Client. iOS support is a WIP, but the Play store Meshtastic app works. I use contact to connect via the pure python Meshtatic CLI on Arch Linux. USB Serial configuration is available on the Femtofox Pro
  • FoxBuntu Install

    Follow the instructions in the Femotfox repo on flashing the foxbuntu image onto the LuckFox.

    The first boot can take up to 5 minutes to complete, and subsequent boots should take around 30 seconds.

    As of Foxbuntu V0.99, you can configure the femtofox via web browser @ https://femtofox.local:7681. If you have a FemtoFox Pro, you can connect over USB. Set the device baud rate to 115200 and press enter in the console window a few times if you don’t see anything. You should see the Femtofox logo, then be promted to set a root password. After this, you can enter $ sudo femto-config to begin configuring the unit.

    If you are having trouble with the femtox.local page, you can ssh into your femto with something like $ ssh femto@{UR_FEMTO_IP}. Find the IP on your LAN with NMap by running something like $ sudo nmap -p 22 {your IP}/24.

    Power Testing

    The Femtofox Pro equipped with the Ebyte E22-900M30S LoRa gateway consumed an average of 360mW on 3V3 and 400mW on 5V. This is amazing! These tests were performed with an ethernet/ssh port open, and with meshtasticd running with the default (max) transmit power setting. Further testing is required to investigate the difference in the peak power usage on a 3V3 and 5V supply. This is likely due to a limit on the output power of the LoRa module (which TRANSMITS up to 1.2W / 31dBm at max power according to my testing) at 3V3 volt, not higher efficiency. Results on this are coming soon, along with recommendations for improved decoupling and filtering to prevent the sagging on the 5V and 3V3 lines observed.

    Equipment Utilized:

  • Rigol DHO804 Oscilloscope
  • Keysight EDU36311A DC PSU
  • Keithly 2450 SMU
  • 4-Wire sense via SMU on Femtofox Pro 3V3-5V JST input,

    5V Power Consumption Results:

    Internet connected via ethernet, SSH port open, meshtastic running with 22dBm setting (~31dBm TX actual)

  • Min: 0.342W
  • Max: 3.154W
  • Average: 0.4W
  • RF Transmit Power Testing

    The Ebyte E22-900M30S LoRa module contains an internal amplifier, which amplifies the SX1268 22dBm max ouput level as high as 31dBm. These tests were performed to evaluate the actual TX power levels of the modules to help ensure compliance with local regulations (namely in the EU, which caps emissions in the LoRa band to a max of 500mW / 27dBm)

    Based on the LoRa Alliance LoRa gateway RF Testing Guidelines

    Equipment Utilized:

  • Mini-Circuits VAT-10A+ + VAT-20A+ Attenuator
  • Mini-Circuits ZX30-9-4-S Directional Coupler
  • Mini-Circuits ZX47-40+ Power Detector
  • NanoVNA V2
  • TinySA Ultra