Implementing some missing features

User avatar
YT5HOK
Posts: 213
Joined: Sat Nov 16, 2019 11:36 am
Location: Belgrade, KN04FR

Re: Implementing some missing features

Post by YT5HOK » Mon Aug 10, 2020 5:14 pm

VK3KYY wrote:
Sun Aug 09, 2020 10:45 pm
...
I'm not even sure if any of the BM source code is publicly available. There is virtually nothing on their GitHub repo

https://github.com/BrandMeister
BrandMeister is closed source mostly (first hand info, from admins). :ugeek:

VK3KYY
Posts: 7594
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Implementing some missing features

Post by VK3KYY » Mon Aug 10, 2020 8:50 pm

YT5HOK wrote:
Mon Aug 10, 2020 5:14 pm
VK3KYY wrote:
Sun Aug 09, 2020 10:45 pm
...
I'm not even sure if any of the BM source code is publicly available. There is virtually nothing on their GitHub repo

https://github.com/BrandMeister
BrandMeister is closed source mostly (first hand info, from admins). :ugeek:
Thanks...

I thought it may be closed source.

ok1pt
Posts: 167
Joined: Mon Jul 20, 2020 3:38 am

Re: Implementing some missing features

Post by ok1pt » Thu Aug 13, 2020 5:32 pm

VK3KYY wrote:
Sun Aug 09, 2020 10:45 pm

BM does not process the SMS to transcode between different manufacturers, because the BM network does not know what type of radio is receiving the data.
I believe you are not right in this. BM knows it because you can specify your radio type in the BM Selfcare.
Now you can specify ETSI, Hytera/Kenwood, Motorola, Chinese Radio and Runbo/Rfinder.
And it really works! You'll not be able to send or receive SMS or both, if you have this set incorrectly (or didn't set anything). So, they should do something and they probably convert the formats, if they know the setting for both parties and they are mutually different.

With regards,
Pavel

n6io
Posts: 11
Joined: Sat Aug 15, 2020 3:54 am

Re: Implementing some missing features

Post by n6io » Sat Aug 15, 2020 4:07 am

ki4gst wrote:
Sat Aug 08, 2020 6:00 am
To answer your first part on power. From what I understand the problem is even thou the firm ware supports all the diffrent power setting the code plug part only supports 2. So that we’re the hang up is. Since the code plug part of memory only supports high and low and Roger hasn’t found a way around it.
Maybe I'm missing something, but this is exactly what I'd like: To be able to store a setting of High or Low power per channel. I tried editing an import file to force those values in, but they didn't seem to get saved.

If the code plug memory supports two power levels - couldn't we use that?

Thanks - Craig, N6IO

ok1pt
Posts: 167
Joined: Mon Jul 20, 2020 3:38 am

Re: Implementing some missing features

Post by ok1pt » Sat Aug 15, 2020 8:34 am

n6io wrote:
Sat Aug 15, 2020 4:07 am
If the code plug memory supports two power levels - couldn't we use that?
Hi!
The question is: WHICH ones ? Now we have 9 power levels. OK, let's state that 5W as High. But which one should be set for Low ? 50mW ? 500mW? 1W? Or any of the others ?
Pavel

n6io
Posts: 11
Joined: Sat Aug 15, 2020 3:54 am

Re: Implementing some missing features

Post by n6io » Sat Aug 29, 2020 5:14 am

Which power level? Well for me the two obvious ones would be lowest possible for low - for use with your hotspot - and the highest typical level which would be 4w for use with an actual repeater (not 5W). Bonus points for allowing a setting for what is low and what is high, but lowest and highest would be my choice.

Post Reply