John,
I'm glad you're on this list. Didn't realize that.
I've look and found no "solution" oriented documentation -- i.e. how can I use the device? All of the information about the internals, like "socket interfaces" may have meaning for some. But, since I don't write protocol internals, it doesn't help me understand the deployment scenarios.
For example, assume I have four JNOS systems that are currently connected to each other on a single subnet using a single 440 frequency. They talk to each other using IP over AX.25. I would definitely like to increase the speed. But it's not clear to me how I would deploy the UDR56K-4 to replace the existing 440 radios/TNCs. What protocol would it run, at what speed? What would the IP network diagram look like?
If this question is not appropriate for the 44-list, we can move it to your yahoo group.
Thanks much, Michael N6MEF
-----Original Message----- From: 44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of K7VE - John Sent: Friday, July 05, 2013 11:02 PM To: AMPRNet working group Subject: Re: [44net] hardware vs. software
(Please trim inclusions from previous messages) _______________________________________________ BTW -- the modems in the UDR56k-4 are DSP to I/Q modulation/demodulation and run on the included Linux card. The intent is to have flexibility in modems, protocols, and applications and provide an open source environment for the experimenters in the user community.
The modems, and protocol stacks, will be available on socket interfaces, so protocols and applications may run either on the radio's embedded system or via interconnection to another host.
By having on-board processing we also are looking at very low tx/rx turnaround time, well below what could be done on a USB or serial port.
One application is using the device as an 'Ethernet Bridge' within a given protocol, modem, and data rate.
Oh, and the price is a 3rd less than Bill posted :)