Manual channel number not available in 1.3?

Mihai · October 20, 2022, 9:17pm

Hello all,
I have recently upgraded my T-beam to 1.3 firmware and I realized that the “channel_num” option is not working anymore (it used to work in 1.2). It is really important for me (us) to have the ability to manually select the radio channel in order to avoid the interference. We are a group of ham-radio operators experimenting with propagation, antennas, etc.
Is there any work around for this?

Thanks,
Regards.

garth · October 20, 2022, 10:36pm

It is on the lora.config protobuf now, each meshtastic channel shares all the same config from the lora.config other than PSK so it was moved there

Mihai · October 21, 2022, 6:17am

Hi. Thanks for answering to me.
I’ve looked at the lora configuration options and I couldn’t find anything related to channel. The closest thing is the frequency offset, but that won’t cover so much.
Can you please give me more details?
Thank you!

garth · October 21, 2022, 4:43pm

github.com

meshtastic/Meshtastic-protobufs/blob/d0559bfa3c31023ed2f2aa3807b6a0a1da9a6feb/config.proto#L589


      
          
          
  /*
             * This is controlling the actual hardware frequency the radio is transmitting on.
             * Most users should never need to be exposed to this field/concept.
             * A channel number between 1 and NUM_CHANNELS (whatever the max is in the current region).
             * If ZERO then the rule is "use the old channel name hash based
             * algorithm to derive the channel number")
             * If using the hash algorithm the channel number will be: hash(channel_name) %
             * NUM_CHANNELS (Where num channels depends on the regulatory region).
             */
            uint32 channel_num = 11;
          
          
  /*
             * For testing it is useful sometimes to force a node to never listen to
             * particular other nodes (simulating radio out of range). All nodenums listed
             * in ignore_incoming will have packets they send droped on receive (by router.cpp)
             */
            repeated uint32 ignore_incoming = 103;
          
          
}

Mihai · October 21, 2022, 6:50pm

So, as far as I remember, this was the legacy method for automatic allocation of the radio channel in Meshtastic.
I managed to change the channel by changing the “name” of the channel. It does work, but it would have been nice to set it directly anyway.

Thanks for the help!

garth · October 21, 2022, 8:26pm

It is a 3 week old change move channel_num to LoRaConfig by andrekir · Pull Request #203 · meshtastic/Meshtastic-protobufs · GitHub

Mihai · October 21, 2022, 10:39pm

OK, so I didn’t try “lora.channel_num” until now. Maybe this is obvious for more advanced users, but for me it wasn’t.
Thanks again.
Offtopic now, is there an option for Transmit Power as well? The ham licence allows for much more than 12dBm

Regards.

Topic		Replies	Views
Inconsistent Channel Number Support	1	212	January 12, 2024
Channel settings for router with nrf52 Support	8	471	April 20, 2022
Relationship between channels and frequency/SF? Support	3	1496	August 10, 2020
New User Questions - Primary & Secondary Channels, etc Support	8	2679	January 3, 2022
Number of LoRa channels Development	4	514	March 3, 2021

Manual channel number not available in 1.3?

Related Topics