Ross,
Great to hear about more people interested!
Just a few thoughts on using existing radios, I agree it would be nice to
make something that was backward compatible with existing radios, although
it's also going to be at a great loss to spectral efficiency especially if
you make the time slot smaller. Think how many new hams would get involved
if there was cheap hardware around that didn't involve mucking with lots of
wires and radio incompatibility.
Not too long ago I built a softrock txrx which was pretty simple for what
it does, it can't be that hard to build something like that made for
VHF/UHF that has a built in ADC/DAC and something like a STM32... Just a
thought anyway..
Also codec2 will probably always have some tweaking going on, I figure if
something gets built that supports 1400bps or maybe 2400bps full duplex,
it'll get used, if codec2 is less than that you have some extra bits to
play with; extra FEC or RSSI or header info?
Regards,
Daniel
Daniel Mundall
On Mon, Apr 21, 2014 at 5:17 AM, Ross Whenmouth <[email protected]> wrote:
> Hi,
>
> In between work and study, I have also been thinking about TDD for
> Codec2 on the shorter wavelengths.
>
> GMSK or C4FM is not only power efficient, but generally speaking, it is
> also compatible with all those "9k6 data ready" VHF/UHF transceivers
> that are out there. More people will probably connect their PC soundcard
> or a STM32F4 discovery board into their existing radio than will go out
> an buy a special experimental radio just to play with Codec2. In light
> of this, it might be a good idea for at least one of the TDD operating
> modes to be compatible with as many existing transceivers as possible
> (eg a DC free line code with generous T-R switching delay allowances).
> Then, when people like it, and build or buy new Codec2-compatible
> transceivers, repeaters can be configured to use the advanced modes that
> can cram lots of voice and data into a 25kHz channel (executed properly,
> this could also alleviate some of the APRS people have with poor
> collision avoidance with Ax.25).
>
>
> Before anyone rushes off a writes a (TDD) protocol for Codec2, how
> likely is the frame size/frame rate/etc of Codec2 to change in the near
> future?
>
>
> 73
> Ross Whenmouth ZL2WRW
>
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Freetel-codec2 mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
