[chirp_users] Out of Band freqs memory
Hello, good job out there. The only problem I "see" is the fact that despite chirp allows us to "unlock" baofeng, for example (I can set the range from 1 to 1000mhz), it won't allow me to save those freqs in memory! Despite the original freqs, I can tune some out of range freqs with my radio, thatts why I Want them into channels. So I have to run the original VIP software, import from radio, add the channel with the out oft Band freq (Because VIP recognises the range of baofeng and allow me to input those) and then export to radio. Thats a long jorney, considering I have a Mac, so I have to lauch Windows.... A user called Jim, made me a .py modification to help me with that. I just load the mode, and right: now I am able to add the out of range freqs. So, why not to add this .py file directly to /chirp/content...? Because this modification has a bug, when I load it I can only set the channels, the settings menu won't work. It remains blank. So I only use this modificated py file to add the freqs. Isn't possible to let chirp to add those freqs eternally? Tks
Hi Andre,
I hope this can be our last discussion on this topic.
The only problem I "see" is the fact that despite chirp allows us to "unlock" baofeng, for example (I can set the range from 1 to 1000mhz), it won't allow me to save those freqs in memory!
At this point, the mainline version of CHIRP will not gain support for programming frequency ranges that the hardware is known not to support. I have seen no compelling evidence that any version of the hardware is capable of anything outside the range that CHIRP currently supports (aside from the 220MHz variant). Until I do, the current functionality will remain.
You have brought this up multiple times in multiple places and we have repeatedly explained that we have no interest in features that may be at best useless and at worst damaging. Please, lets put this topic to rest.
Thanks!
Sorry for that, I didn't noticies that I sent the message for you before. But despite you had evidence or not, many like me had the "lucky" to tune their baofengs in many outside Band freqs and like to keep those in memory. I proved many times posting videos, but it seamns to be like believe or not in god, because some like you still doesn't believe, like if I have something to win with that... Anyway, it was just a advice to make what chirp "born" to do: make the ham's life easier. I am not a programer, so I don't know how to do, that's ok, I know they way I can do what I desired, despite chirp could make my life easier! But nothing in life is easy, Right? Why to help? Tks very much, good work. When my py file worked fine I will post it for "liers" like my, maybe I help them Tks
Em 02/04/2013, às 12:39, Dan Smith dsmith@danplanet.com escreveu:
Hi Andre,
I hope this can be our last discussion on this topic.
The only problem I "see" is the fact that despite chirp allows us to "unlock" baofeng, for example (I can set the range from 1 to 1000mhz), it won't allow me to save those freqs in memory!
At this point, the mainline version of CHIRP will not gain support for programming frequency ranges that the hardware is known not to support. I have seen no compelling evidence that any version of the hardware is capable of anything outside the range that CHIRP currently supports (aside from the 220MHz variant). Until I do, the current functionality will remain.
You have brought this up multiple times in multiple places and we have repeatedly explained that we have no interest in features that may be at best useless and at worst damaging. Please, lets put this topic to rest.
Thanks!
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Only to finish, again: proving the existence of "god":
http://youtu.be/DldYXk6Z9xA http://youtu.be/KvvnvvQIG2E http://youtu.be/Z-2OIs8XeTY http://youtu.be/xTGa3uczRQ8
Dr. André Berger CRM 115.404 / SP Oftalmologista
Oftalmologia Cidade Jardim
Centro Especialidades Médicas Cidade Jardim Av. Lineu de Paula Machado, 916 11-3032-6024 dranbes@gmail.com
www.oftalmologiacidadejardim.com.br
Em 02/04/2013, às 13:23, Yahoo anbes@yahoo.com escreveu:
Sorry for that, I didn't noticies that I sent the message for you before. But despite you had evidence or not, many like me had the "lucky" to tune their baofengs in many outside Band freqs and like to keep those in memory. I proved many times posting videos, but it seamns to be like believe or not in god, because some like you still doesn't believe, like if I have something to win with that... Anyway, it was just a advice to make what chirp "born" to do: make the ham's life easier. I am not a programer, so I don't know how to do, that's ok, I know they way I can do what I desired, despite chirp could make my life easier! But nothing in life is easy, Right? Why to help? Tks very much, good work. When my py file worked fine I will post it for "liers" like my, maybe I help them Tks
Em 02/04/2013, às 12:39, Dan Smith dsmith@danplanet.com escreveu:
Hi Andre,
I hope this can be our last discussion on this topic.
The only problem I "see" is the fact that despite chirp allows us to "unlock" baofeng, for example (I can set the range from 1 to 1000mhz), it won't allow me to save those freqs in memory!
At this point, the mainline version of CHIRP will not gain support for programming frequency ranges that the hardware is known not to support. I have seen no compelling evidence that any version of the hardware is capable of anything outside the range that CHIRP currently supports (aside from the 220MHz variant). Until I do, the current functionality will remain.
You have brought this up multiple times in multiple places and we have repeatedly explained that we have no interest in features that may be at best useless and at worst damaging. Please, lets put this topic to rest.
Thanks!
-- Dan Smith www.danplanet.com KK7DS _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
I've sent this privately to avoid "polluting" the public thread. I haven't followed this very closely, but:
1. As I understand it, this guy doesn't really understand "image" frequency reception. 2. From his last message, I think he will "continue the fight", perhaps on other forums.
So, I'd suggest a policy statement on your web site, something like:
/Chirp will not accept or support modifications that may cause a radio to actually operate (including receive) on a frequency or in a mode that is different than the frequency or mode displayed. Such modifications may cause users to operate on a frequency or in a mode that they do not intend. Discussions on this matter are considered "off-topic" for the mailing list./
Sincerely, Dean
On 2013-04-02 08:39, Dan Smith wrote:
Hi Andre,
I hope this can be our last discussion on this topic.
The only problem I "see" is the fact that despite chirp allows us to "unlock" baofeng, for example (I can set the range from 1 to 1000mhz), it won't allow me to save those freqs in memory!
At this point, the mainline version of CHIRP will not gain support for programming frequency ranges that the hardware is known not to support. I have seen no compelling evidence that any version of the hardware is capable of anything outside the range that CHIRP currently supports (aside from the 220MHz variant). Until I do, the current functionality will remain.
You have brought this up multiple times in multiple places and we have repeatedly explained that we have no interest in features that may be at best useless and at worst damaging. Please, lets put this topic to rest.
Thanks!
Oops, it was supposed to be private! Oh well!
On 2013-04-02 10:09, Dean Gibson AE7Q wrote:
I've sent this privately to avoid "polluting" the public thread. I haven't followed this very closely, but:
- As I understand it, this guy doesn't really understand "image" frequency reception.
- From his last message, I think he will "continue the fight", perhaps on other forums.
So, I'd suggest a policy statement on your web site, something like:
/Chirp will not accept or support modifications that may cause a radio to actually operate (including receive) on a frequency or in a mode that is different than the frequency or mode displayed. Such modifications may cause users to operate on a frequency or in a mode that they do not intend. Discussions on this matter are considered "off-topic" for the mailing list./
Sincerely, Dean
participants (4)
-
André Berger -
Dan Smith -
Dean Gibson AE7Q -
Yahoo