Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. General Discussion
  3. Shared configs/data types for LoRa based radios

Shared configs/data types for LoRa based radios

Scheduled Pinned Locked Moved General Discussion
7 Posts 3 Posters 86 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E Offline
    E Offline
    eiten
    wrote on last edited by
    #1

    Hello there,

    what do you think if we would use commont data types and configs for all LoRa-based radios (rfm96, rfm59, maybe sometimes sx126x and the hopefully soon to come CubeCell)? It would make maintaining lots easyer.
    Same for the two different nrf24 radios (but here I'm not sure if they really got a future).

    Regards, Edi

    mfalkviddM 1 Reply Last reply
    0
    • E eiten

      Hello there,

      what do you think if we would use commont data types and configs for all LoRa-based radios (rfm96, rfm59, maybe sometimes sx126x and the hopefully soon to come CubeCell)? It would make maintaining lots easyer.
      Same for the two different nrf24 radios (but here I'm not sure if they really got a future).

      Regards, Edi

      mfalkviddM Offline
      mfalkviddM Offline
      mfalkvidd
      Mod
      wrote on last edited by
      #2

      @eiten clould you expand on what you mean by data types and configs in this context, maybe by examples?

      1 Reply Last reply
      0
      • E Offline
        E Offline
        eiten
        wrote on last edited by
        #3

        @mfalkvidd of course.

        Regarding configs:
        We have a MY_RFM69_FREQUENCY and a MY_RFM95_FREQUENCY. I think it would be easyer for the end user if we just got a MY_FREQUENCY.
        Also, for future implementation of other LoRa modules (CubeCell, SX126x...) i think it would be good if we have a lora.h where we define structs like these, to define lora_header_t, lora_ack_t, lora_packet_t, lora_sequence_number ... as well as defines like LORA_MAX_PACKET_LEN, LORA_HEADER_LEN and so on.
        It would ensure compatibility between lora modules and make maintaining easyer. (I know what I am talking about, I was looking for my error in the CubeCell driver for a half a day only finding that i defined the cubecell sequence number as a uint_8, not being compatible to the rfm95 uint16_t :face_palm:)
        Regards, Edi

        mfalkviddM 1 Reply Last reply
        0
        • E eiten

          @mfalkvidd of course.

          Regarding configs:
          We have a MY_RFM69_FREQUENCY and a MY_RFM95_FREQUENCY. I think it would be easyer for the end user if we just got a MY_FREQUENCY.
          Also, for future implementation of other LoRa modules (CubeCell, SX126x...) i think it would be good if we have a lora.h where we define structs like these, to define lora_header_t, lora_ack_t, lora_packet_t, lora_sequence_number ... as well as defines like LORA_MAX_PACKET_LEN, LORA_HEADER_LEN and so on.
          It would ensure compatibility between lora modules and make maintaining easyer. (I know what I am talking about, I was looking for my error in the CubeCell driver for a half a day only finding that i defined the cubecell sequence number as a uint_8, not being compatible to the rfm95 uint16_t :face_palm:)
          Regards, Edi

          mfalkviddM Offline
          mfalkviddM Offline
          mfalkvidd
          Mod
          wrote on last edited by mfalkvidd
          #4

          Thanks for explaining @eite. Consolidating the frequency setting to MY_FREQUENCY would make it hard to support multiple radios in a straightforward way. If a gateway has a lora radio and a rfm69 radio, they would not necessarily use the same frequency.

          For the structs, I'm afraid that is beyond my competence but hopefully someone more skilled in the radio code can contribute.

          YveauxY E 2 Replies Last reply
          2
          • mfalkviddM mfalkvidd

            Thanks for explaining @eite. Consolidating the frequency setting to MY_FREQUENCY would make it hard to support multiple radios in a straightforward way. If a gateway has a lora radio and a rfm69 radio, they would not necessarily use the same frequency.

            For the structs, I'm afraid that is beyond my competence but hopefully someone more skilled in the radio code can contribute.

            YveauxY Offline
            YveauxY Offline
            Yveaux
            Mod
            wrote on last edited by
            #5

            @mfalkvidd Agree. Another consideration would be that some #defines would be used for multiple radios (but not all), and some would be radio specific. I prefer to have the usage explicit in the name, to prevent confusion on which define is used by each radio.

            http://yveaux.blogspot.nl

            1 Reply Last reply
            0
            • mfalkviddM mfalkvidd

              Thanks for explaining @eite. Consolidating the frequency setting to MY_FREQUENCY would make it hard to support multiple radios in a straightforward way. If a gateway has a lora radio and a rfm69 radio, they would not necessarily use the same frequency.

              For the structs, I'm afraid that is beyond my competence but hopefully someone more skilled in the radio code can contribute.

              E Offline
              E Offline
              eiten
              wrote on last edited by
              #6

              @mfalkvidd Ah, I did not know that it's possible for a gateway to have multiple radios!

              mfalkviddM 1 Reply Last reply
              0
              • E eiten

                @mfalkvidd Ah, I did not know that it's possible for a gateway to have multiple radios!

                mfalkviddM Offline
                mfalkviddM Offline
                mfalkvidd
                Mod
                wrote on last edited by
                #7

                @eiten support for multiple radios is a new feature, only available in the development branch and not well documented yet so no surprise you weren't aware of it.

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                26

                Online

                11.7k

                Users

                11.2k

                Topics

                113.1k

                Posts


                Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • MySensors
                • OpenHardware.io
                • Categories
                • Recent
                • Tags
                • Popular