> <mailto:
iz3gme.marco@gmail.com>> wrote:
>
> On 26/09/2012 01:37, Dan Smith wrote:
> >> thanks dan! yep, i can tell at a glance that the daily build covers
> >> exactly the frequency range of my uv6x, but not near the freq
> range of
> >> my uv6d. does this mean i shouldn't use chirp with the uv6d
> until this
> >> has been resolved? or does it just mean that channels outside the
> >> 'official' range won't get transferred?
> >
> > I'll let Marco comment here, since he wrote the UV6 driver.
> >
> > I would expect that it's just a matter of range-checking and that
> CHIRP
> > will refuse entering frequencies outside the range it thinks is
> > appropriate for your model. However, the way those radios work, I'd
> > expect no ill effects of putting in frequencies outside the accepted
> > range, nor would I expect the radio to not tune (or appear to
> tune) them.
>
> Dan is, obviously, right: it's only a matter of range checking.
> Chirp interface is forced, for uv6d, to accept frequencies in range
> 136MHz to 175MHz and 350MHz to 471MHz which appeared to be correct for
> that radio at the time I wrote the driver.
> I suspect that forcing radio on frequencies a little outside his range
> don't give any bad effect but I didn't try this myself.
>
> Guy, can you please send me an image downloaded from your uv6d and the
> ranges your radio accept so that I can try to find a way to distinguish
> this submodel?
>
> It would be nice to have a full range of radio given from the sellers to
> play with ... having complete programming info from producers could be
> even better ;)
>
> Dan, have you ever tried to contact wouxun headquarter?
>
> 73 de IZ3GME Marco
> _______________________________________________
> chirp_users mailing list
>
chirp_users@intrepid.danplanet.com