Reach M2 LTE Modem APN Setting

Reach Module / M+ / M2 Hardware integration
1

I’m using a Reach M2 on v31.8, below is a report from my device. My goal is to have a USB LTE modem replace the role of a WiFi connection. The LTE modem I have and would like to get working is a Soracom Onyx. I chose this one because it is Linux compatible (per the “Hardware Integration” page of the docs), and it is, I tested it out on Ubuntu. Plugged it in, set APN, had to turn on roaming, then I had connection. Easy.

Not so on the M2, apparently. Haven’t found a way to get the M2 to talk with the modem. I even went as far as poking around in the M2’s OS via SSH, but the emlid user has absolutely no privilege.

I believe the issue is there is no setting in the Reach panel for APN settings. My understanding is that the other Emlid receivers with integrated SIM and 3G have these networking settings in Reach panel. Why not the M2?

Appreciate any guidance in these trying times.

Blockquote

Simple system report 
app version: 31.8-r0
current_network:
  ip: 192.168.42.1
  security: wpa
  ssid: ReachForTheSky:7E:77
enabled: true
mode: hotspot
base_mode:
  base_coordinates:
    accumulation: 30
    antenna_offset: 3.175
    coordinates:
      height: 114.656
      latitude: 38.20106811
      longitude: -85.74630429
    mode: fix-and-hold
  output:
    io_type: ntripsvr
    settings:
      lora:
        air_rate: 9.11
        frequency: 902000
        output_power: 20
      ntripcaster:
        mount_point: '***'
        password: '***'
        port: 2101
        username: '***'
      ntripsvr:
        address: '***'
        mount_point: '***'
        password: '***'
        port: 2101
      serial:
        baud_rate: 38400
        device: ttyEXTS0
      tcpcli:
        address: localhost
        port: 9001
      tcpsvr:
        port: 9000
  rtcm3_messages:
    message_1004:
      enabled: false
      frequency: 1
    message_1006:
      enabled: true
      frequency: 1
    message_1008:
      enabled: false
      frequency: 0.1
    message_1012:
      enabled: false
      frequency: 1
    message_1033:
      enabled: false
      frequency: 0.1
    message_1074:
      enabled: true
      frequency: 1
    message_1084:
      enabled: true
      frequency: 1
    message_1094:
      enabled: true
      frequency: 1
    message_1124:
      enabled: true
      frequency: 1
    message_1230:
      enabled: true
      frequency: 1
bluetooth:
  enabled: true
  pairing:
    discoverable: true
    no_input_no_output: true
    pin: '***'
camera_trigger:
  duty_cycle: 20
  enabled: false
  period: 2
  reverse_polarity: false
correction_input:
  base_corrections:
    io_type: ntripcli
    settings:
      bluetooth:
        send_position_to_base: false
      lora:
        air_rate: 9.11
        frequency: 902000
        output_power: 20
        send_position_to_base: false
      ntripcli:
        address: '***'
        mount_point: '***'
        password: '***'
        port: 2101
        send_position_to_base: false
        username: '***'
      serial:
        baud_rate: 38400
        device: ttyEXTS0
        send_position_to_base: false
      tcpcli:
        address: localhost
        port: 10001
        send_position_to_base: true
      tcpsvr:
        port: 10000
        send_position_to_base: true
device:
  privacy_policy_accepted: true
  role: null
  rv3_banner_shown: false
  usage_analysis_accepted: false
logging:
  logs:
    autostart: true
    base:
      enabled: false
      format: RTCM3
    raw:
      enabled: true
      format: RINEX
      rinex_options:
        logging_interval: 0
        marker_name: null
        pole_height: 0.208
        preset: custom
        satellite_systems:
          beidou: true
          galileo: true
          glonass: true
          gps: true
          qzss: true
          sbas: true
        time_adjustments_enabled: true
      version: '3.03'
    solution:
      enabled: false
      format: LLH
    started: true
  settings:
    interval: 24
    overwrite: true
    simultaneous_logging: false
position_output:
  output1:
    io_type: bluetooth
    nmea_settings:
      bluetooth:
        ebp:
          enabled: true
          update_rate: 5
        gga:
          enabled: true
          update_rate: 5
        gsa:
          enabled: true
          update_rate: 5
        gst:
          enabled: true
          update_rate: 5
        gsv:
          enabled: true
          update_rate: 5
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 5
        vtg:
          enabled: true
          update_rate: 5
        zda:
          enabled: true
          update_rate: 5
      serial:
        ebp:
          enabled: true
          update_rate: 1
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpcli:
        ebp:
          enabled: true
          update_rate: 1
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpsvr:
        ebp:
          enabled: true
          update_rate: 1
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
    settings:
      bluetooth:
        format: NMEA
      serial:
        baud_rate: 38400
        device: ttyEXTS0
        format: ERB
      tcpcli:
        address: localhost
        format: ERB
        port: 9000
      tcpsvr:
        format: LLH
        port: 9001
  output2:
    io_type: 'off'
    nmea_settings:
      bluetooth:
        ebp:
          enabled: true
          update_rate: 1
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      serial:
        ebp:
          enabled: true
          update_rate: 1
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpcli:
        ebp:
          enabled: true
          update_rate: 1
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
      tcpsvr:
        ebp:
          enabled: true
          update_rate: 1
        gga:
          enabled: true
          update_rate: 1
        gsa:
          enabled: true
          update_rate: 1
        gst:
          enabled: true
          update_rate: 1
        gsv:
          enabled: true
          update_rate: 1
        main_talker_id: gn
        rmc:
          enabled: true
          update_rate: 1
        vtg:
          enabled: true
          update_rate: 1
        zda:
          enabled: true
          update_rate: 1
    settings:
      bluetooth:
        format: NMEA
      serial:
        baud_rate: 38400
        device: ttyEXTS0
        format: ERB
      tcpcli:
        address: localhost
        format: ERB
        port: 9000
      tcpsvr:
        format: LLH
        port: 9001
positioning_settings:
  elevation_mask_angle: 15
  glonass_ar_mode: false
  gnss_settings:
    positioning_systems:
      beidou: true
      galileo: true
      glonass: true
      gps: true
      qzss: true
    update_rate: 10
  gps_ar_mode: fix-and-hold
  max_horizontal_acceleration: 1
  max_vertical_acceleration: 1
  positioning_mode: kinematic
  snr_mask: 35
3

Hi Thomas,

Welcome to the forum!

Do understand correctly that you would want to provide Reach M2 with Internet access via a direct USB-to-PC connection?

UPD. I changed my answer as I misunderstood Thomas earlier.

4

Thank you for the reply!

Maybe I’m not understanding here, but I’m not interested in a USB-to-PC connection. I just want to get the M2 to use the LTE modem, per the docs (“Connecting USB radio or LTE modem” in “Hardware Integration”). It clearly states to plug the modem into the USB OTG cable, set the M2 to hotspot mode, and then it should work.

If this is not a feature available on this model, then I have been wasting precious time and you should consider removing this configuration from your docs.

Best,
Thomas

5

Thomas,

I’m sorry, I misunderstood you earlier. I will change my previous answer so as not to confuse anyone.

Yes, an LTE modem can be connected to the M2. Is there any LED reaction on the modem when it’s connected to the M2?

Can you update the M2 to our 32 Beta 1 version and test if it will help? If not, please share the Full System report to the support@emlid.com.

1 Like
6

The modem lights up and appears to function. I snooped around in the M2 using SSH and was able to determine that the modem is detected as a connected USB device, a Quectel EC25-G, and that Network Manager sees it as a “wwan” device, but not as a GSM modem. It displays “plugin missing” on the device, which I think is the root cause here, as the M2 does not have Modem Manager installed, for some reason. See the attached screenshots.

In the meantime, I will send a current full system report to the support email and try the beta update.

1

Screenshot 2024-02-06 152010
Screenshot 2024-02-06 152010693×730 18.2 KB

7

Updating my M2 to beta v32 beta 1 made no change to the state of the issue. Also, the full system report has now been sent over.

8

Thomas,

Thank you for providing additional information and testing. Yes, the Soracom Onyx modem does require ModemManager to be installed. We don’t add such drivers to the devices without modems, and currently, we have no plans to support it in future firmware versions.

As a workaround, I can suggest using one of the modems we tested with Reach M+: ZTE MF823 or Huawei E171.

1 Like
9

Thank you for the confirmation, although I can’t say I understand why a limitation like that would willingly (or arbitrarily) be placed on a device such as this one. Also, what makes those two adapters different from a standard modem so that they may work without Modem Manager?

Consider this a +1 request for Modem Manager to be added, as I cannot add it myself without root access to the device (which is another shortcoming, but different issue).

I will attempt with the other LTE adapters for now.

Best,
Thomas

10

Thomas,

Adding this Modem Manager to the M2 firmware requires additional research, but I’ve passed your information to our development team.

Different modems have different requirements, and it’s difficult to predict why certain ones won’t work. We tested those 2 modems with M+ and can confirm that they should work with Reach devices.

1 Like
12

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.