1. main@nw-digital-radio.groups.io
   Date   
Re: UDRX ???

Paul Johnson
 

UDRX = a still birth = so sad! 1200 baud packet radio 30 years
old in the PNW. I was looking forward to the UDRX as the next
generation to carry the mode forward as a plug and play Amateur
Radio RADIO NETWORK device. Thanks for confirming the last nail
in the coffin for this project.....I can now stop waiting!

Paul VE7DHM

On Tue, 2018-05-01 at 09:48 -0700, John D Hays - K7VE wrote:
Marc -- the UDRX project had languished for too long and has been
discontinued. The current focus of NW Digital Radio is outlined here
-- http://nwdigitalradio.com/2018-state-of-the-union/


This decision was not taken lightly. Rest assured we are still
interested in providing solutions in the space that the UDRX
envisioned and we will have future products in the space, but likely
taking a different approach.


Right now we are working on projects outlined in the "State of the
Union", some of which will be available for view at Hamvention in a
couple of weeks.

On Tue, May 1, 2018 at 9:16 AM, Marc Lacy <KD7RYY@msn.com> wrote:
I see on the website that the UDRX is no longer listed. What
has happened?




--


______________________________________________________________________
John D. Hays
Director
UDRX-440 Board and Pi Star #hamvention

SkierInAvon@...
 

Re:  New UDRX-440 Board

Not certain I've read the product release correctly.
(in the future) will be be able to connect this new Board to a RPi 3 - that is running Pi-Star SW?

If yes, that should make a ~25Watt DMR/DSTAR/C4FM/P25/NXDN Hotspot...vs-a-vie the   20milliWatt   Pi Star Hotspots we're running today??

Comments?
N0ECT
Re: MMDVM & UDRC

Jonathan Naylor
 

Hi All

I don’t have a Compass Linux up and running yet so I built it on a standard Linux box with the WiringPi header added.

In MMDVM.cpp you will see two strings, “READ” and “WRITE” or similar. These need to be replaced with the Compass Linux UDRC ALSA sound devices. If someone could do a pull request with that info and the missing library, I’d appreciate it.

To use it, you need to use a pseudo tty to link it to the host, and have one end of the pseudo tty on the command line. It will run as a daemon if you pass -daemon on the command line.

It’s untested, but closely related to the latest MMDVM firmware.

Jonathan G4KLX 




On Saturday, May 5, 2018, 05:49, Tony <w7efs@...> wrote:

Thank you, it compiles successfully with that library addition to the Makefile.

Hopefully we'll soon receive some guidance on how to make the resulting executable MMDVM work with the UDRC-II. Does it replace one of the existing components dstarrepeaterd or ircddbgatewayd, perhaps via symlink? Where is the "more sensible configuration file"? Enquiring minds would like to know, as there's no man page and no "make install", only a usage message.


On 05/04/2018 01:59 PM, Jeremy McDermond wrote:
I don’t see a -lwiringPi in the link command you have cut/pasted.

— Anna

On May 4, 2018, at 10:32 AM, Rich KR4PI <rich.schnieders@...> wrote:

I ran into the same issue trying to compile on Compass Wilderness from March 2018. 

Rich, KR4PI

Re: MMDVM & UDRC

Tony <w7efs@...>
 

Thank you, it compiles successfully with that library addition to the Makefile.

Hopefully we'll soon receive some guidance on how to make the resulting executable MMDVM work with the UDRC-II. Does it replace one of the existing components dstarrepeaterd or ircddbgatewayd, perhaps via symlink? Where is the "more sensible configuration file"? Enquiring minds would like to know, as there's no man page and no "make install", only a usage message.


On 05/04/2018 01:59 PM, Jeremy McDermond wrote:
I don’t see a -lwiringPi in the link command you have cut/pasted.

— Anna

On May 4, 2018, at 10:32 AM, Rich KR4PI <rich.schnieders@...> wrote:

I ran into the same issue trying to compile on Compass Wilderness from March 2018. 

Rich, KR4PI

Re: MMDVM & UDRC

Jeremy McDermond <mcdermj@...>
 

I don’t see a -lwiringPi in the link command you have cut/pasted.

— Anna

On May 4, 2018, at 10:32 AM, Rich KR4PI <rich.schnieders@...> wrote:

I ran into the same issue trying to compile on Compass Wilderness from March 2018. 

Rich, KR4PI

Re: MMDVM & UDRC

Rich KR4PI
 

I ran into the same issue trying to compile on Compass Wilderness from March 2018. 

Rich, KR4PI
Re: MMDVM & UDRC

Tony <w7efs@...>
 

Greetings all,

I downloaded the zip file from https://github.com/g4klx/MMDVM-UDRC. The README.md contains no specific build instructions, and "make" encounters an error. First I check for some things:

root@:~/src/MMDVM-UDRC-master# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: udrc [udrc], device 0: Universal Digital Radio Controller tlv320aic32x4-hifi-0 []
  Subdevices: 0/1
  Subdevice #0: subdevice #0

root@:~/src/MMDVM-UDRC-master# dpkg --get-selections | grep wiringpi
wiringpi                                        install

root@:~/src/MMDVM-UDRC-master# make
...
g++ Biquad.o CalDMR.o CalDStarRX.o CalDStarTX.o CalNXDN.o CalP25.o CWIdTX.o DMRDMORX.o DMRDMOTX.o DMRSlotType.o DStarRX.o DStarTX.o FIR.o FIRInterpolator.o IO.o IOUDRC.o MMDVM.o NXDNRX.o NXDNTX.o P25RX.o P25TX.o SampleRB.o SerialDataController.o SerialPort.o SerialRB.o SoundCardReaderWriter.o Thread.o Utils.o YSFRX.o YSFTX.o -g -lpthread -lasound -o MMDVM
IOUDRC.o: In function `CIO::initInt()':
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:32: undefined reference to `wiringPiSetup'
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:34: undefined reference to `pinMode'
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:37: undefined reference to `pullUpDnControl'
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:39: undefined reference to `pinMode'
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:40: undefined reference to `pinMode'
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:41: undefined reference to `pinMode'
IOUDRC.o: In function `CIO::startInt()':
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:50: undefined reference to `digitalWrite'
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:51: undefined reference to `digitalWrite'
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:47: undefined reference to `digitalWrite'
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:48: undefined reference to `digitalWrite'
IOUDRC.o: In function `CIO::getCOSInt()':
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:57: undefined reference to `digitalRead'
IOUDRC.o: In function `CIO::setLEDInt(bool)':
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:62: undefined reference to `digitalWrite'
IOUDRC.o: In function `CIO::setPTTInt(bool)':
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:74: undefined reference to `digitalWrite'
/root/src/MMDVM-UDRC-master/IOUDRC.cpp:76: undefined reference to `digitalWrite'
collect2: error: ld returned 1 exit status
Makefile:14: recipe for target 'MMDVM' failed
make: *** [MMDVM] Error 1

Thinking that I might be missing some package(s), I search for the undefined references without result:

root@:~/src/MMDVM-UDRC-master# for i in \
> $(make 2>&1 | grep "^/root" | awk '{print $NF}' | \
> tr -d [:punct:] | sort | uniq)
> do
>   echo $i
>   apt-file search $i
> done
digitalRead
digitalWrite
pinMode
pullUpDnControl
wiringPiSetup

root@:~/src/MMDVM-UDRC-master#

What am I missing please to successfully compile this code?

On 05/03/2018 07:38 AM, Jonathan Naylor via Groups.Io wrote:

Hi Folks

I’ve been busy working on some new bits of software. Both of them target the UDRC on a Raspberry Pi as a platform, and offer some interesting new avenues for experimentation.

Firstly I ported my old AnalogueRepeater over to the UDRC (or any other sound card based system allied to an Arduino controller). I also simplified the software, removing its GUI and the need for wxWidgets and renamed it as the FMRepeater on my GitHub.

I removed the potential for a second audio input such as EchoLink and did some other simplifications. Otherwise it is the same as the old AnalogueRepeater but with a more sensible configuration file. It also has a lockout input :-)

I had toyed with the idea of incorporating it into the MMDVM code base to run on the same controller as the digital modes, however compared to the MMDVM, the number of tunable options is very great and I thought it would be better to run it on a separate platform. It hasn’t been tested yet, but most of the code is well tested in its previous incarnation so the bugs will be in the porting.

I’ve also ported the MMDVM firmware to run on the UDRC! It works on all modes in both simplex and duplex modes. The code has been taken from the latest MMDVM GitHub dstar_correlator branch as that offers the best sensitivity. It will only work with the UDRC as the hardware control is hard coded (the sound device is incorrect in GitHub until I get my UDRC running on Compass Linux). So far it sounds like there is no need for proper MMDVM hardware, and for some applications that is true. In fact you can run all modes in simplex or duplex modes like a real MMDVM with one major exception: you cannot run DMR in duplex mode, and it will never be able to do so. You could use it if you had two DMR radios in DMO mode (or one radio if you’re happy to change channel between TX and RX), but not a single DMR radio in duplex mode.

Although almost everything is hard coded. The MMDVM code requires a pseudo-TTY port passed as a command line parameter as that is the way it will communicate with an MMDVMHost process.

One of the things I did was move the MMDVM code to use floating point numbers, which will make thinks slightly easier if/when the main MMDVM code goes over to floating point. The pain of recalculating the coefficients has already been gone through.

Both of these projects need testing and tweaking by either myself or other people (hint hint), but they’re both on my GitHub as of now. The MMDVM version is named MMDVM-UDRC.

I still have one more older project I wish to resurrect and simplify, and I’ll get onto that now.

Jonathan  G4KLX
Re: MMDVM & UDRC

John D Hays - K7VE
 

Great to see, Jonathan.

Check your Yahoo email for some notes.

On Thu, May 3, 2018, 07:38 Jonathan Naylor via Groups.Io <naylorjs=yahoo.com@groups.io> wrote:

Hi Folks

 

I’ve been busy working on some new bits of software. Both of them target the UDRC on a Raspberry Pi as a platform, and offer some interesting new avenues for experimentation.

 

Firstly I ported my old AnalogueRepeater over to the UDRC (or any other sound card based system allied to an Arduino controller). I also simplified the software, removing its GUI and the need for wxWidgets and renamed it as the FMRepeater on my GitHub.

 

I removed the potential for a second audio input such as EchoLink and did some other simplifications. Otherwise it is the same as the old AnalogueRepeater but with a more sensible configuration file. It also has a lockout input :-)

 

I had toyed with the idea of incorporating it into the MMDVM code base to run on the same controller as the digital modes, however compared to the MMDVM, the number of tunable options is very great and I thought it would be better to run it on a separate platform. It hasn’t been tested yet, but most of the code is well tested in its previous incarnation so the bugs will be in the porting.

 

I’ve also ported the MMDVM firmware to run on the UDRC! It works on all modes in both simplex and duplex modes. The code has been taken from the latest MMDVM GitHub dstar_correlator branch as that offers the best sensitivity. It will only work with the UDRC as the hardware control is hard coded (the sound device is incorrect in GitHub until I get my UDRC running on Compass Linux). So far it sounds like there is no need for proper MMDVM hardware, and for some applications that is true. In fact you can run all modes in simplex or duplex modes like a real MMDVM with one major exception: you cannot run DMR in duplex mode, and it will never be able to do so. You could use it if you had two DMR radios in DMO mode (or one radio if you’re happy to change channel between TX and RX), but not a single DMR radio in duplex mode.

 

Although almost everything is hard coded. The MMDVM code requires a pseudo-TTY port passed as a command line parameter as that is the way it will communicate with an MMDVMHost process.

 

One of the things I did was move the MMDVM code to use floating point numbers, which will make thinks slightly easier if/when the main MMDVM code goes over to floating point. The pain of recalculating the coefficients has already been gone through.

 

Both of these projects need testing and tweaking by either myself or other people (hint hint), but they’re both on my GitHub as of now. The MMDVM version is named MMDVM-UDRC.

 

I still have one more older project I wish to resurrect and simplify, and I’ll get onto that now.

 

Jonathan  G4KLX
MMDVM & UDRC

Jonathan Naylor
 

Hi Folks

 

I’ve been busy working on some new bits of software. Both of them target the UDRC on a Raspberry Pi as a platform, and offer some interesting new avenues for experimentation.

 

Firstly I ported my old AnalogueRepeater over to the UDRC (or any other sound card based system allied to an Arduino controller). I also simplified the software, removing its GUI and the need for wxWidgets and renamed it as the FMRepeater on my GitHub.

 

I removed the potential for a second audio input such as EchoLink and did some other simplifications. Otherwise it is the same as the old AnalogueRepeater but with a more sensible configuration file. It also has a lockout input :-)

 

I had toyed with the idea of incorporating it into the MMDVM code base to run on the same controller as the digital modes, however compared to the MMDVM, the number of tunable options is very great and I thought it would be better to run it on a separate platform. It hasn’t been tested yet, but most of the code is well tested in its previous incarnation so the bugs will be in the porting.

 

I’ve also ported the MMDVM firmware to run on the UDRC! It works on all modes in both simplex and duplex modes. The code has been taken from the latest MMDVM GitHub dstar_correlator branch as that offers the best sensitivity. It will only work with the UDRC as the hardware control is hard coded (the sound device is incorrect in GitHub until I get my UDRC running on Compass Linux). So far it sounds like there is no need for proper MMDVM hardware, and for some applications that is true. In fact you can run all modes in simplex or duplex modes like a real MMDVM with one major exception: you cannot run DMR in duplex mode, and it will never be able to do so. You could use it if you had two DMR radios in DMO mode (or one radio if you’re happy to change channel between TX and RX), but not a single DMR radio in duplex mode.

 

Although almost everything is hard coded. The MMDVM code requires a pseudo-TTY port passed as a command line parameter as that is the way it will communicate with an MMDVMHost process.

 

One of the things I did was move the MMDVM code to use floating point numbers, which will make thinks slightly easier if/when the main MMDVM code goes over to floating point. The pain of recalculating the coefficients has already been gone through.

 

Both of these projects need testing and tweaking by either myself or other people (hint hint), but they’re both on my GitHub as of now. The MMDVM version is named MMDVM-UDRC.

 

I still have one more older project I wish to resurrect and simplify, and I’ll get onto that now.

 

Jonathan  G4KLX
Re: blueDV; Windows 7 & ThumbDV 3000

Douglas F. Enoch
 

Yes I got that.  I didn’t make the terminology connection.  Thanks again.  73,  Doug

 

From: main@nw-digital-radio.groups.io [mailto:main@nw-digital-radio.groups.io] On Behalf Of Eric Osterberg
Sent: Wednesday, May 02, 2018 3:20 PM
To: main@nw-digital-radio.groups.io
Subject: Re: [nw-digital-radio] blueDV; Windows 7 & ThumbDV 3000

 

Kerchunk the talk-group you want to use... That will cause a link.

Kerchunk on 4000 to disconnect.

 

On Wed, May 2, 2018 at 11:31 AM, Douglas F. Enoch <doug.enoch@...> wrote:

Thank you very much the.   4000 issue was the problem.  But, I am not sure about what “issuing a link command” is??   Doug…KD8YVD

 

From: main@nw-digital-radio.groups.io [mailto:main@nw-digital-radio.groups.io] On Behalf Of n9ko@...
Sent: Wednesday, May 02, 2018 7:26 AM
To: main@nw-digital-radio.groups.io
Subject: Re: [nw-digital-radio] blueDV; Windows 7 & ThumbDV 3000

 

You must issue a 4000 Group call  before you go to a second TG. Try that.  If that does not take care of the "negative lock" then I would uninstall blueDV and reinstall it. Every time you start blueDV you will need to issue a link command. 

 
Re: blueDV; Windows 7 & ThumbDV 3000

Eric Osterberg
 

Kerchunk the talk-group you want to use... That will cause a link.
Kerchunk on 4000 to disconnect.

On Wed, May 2, 2018 at 11:31 AM, Douglas F. Enoch <doug.enoch@...> wrote:

Thank you very much the.   4000 issue was the problem.  But, I am not sure about what “issuing a link command” is??   Doug…KD8YVD

 

From: main@....io [mailto:main@nw-digital-radio.groups.io] On Behalf Of n9ko@...
Sent: Wednesday, May 02, 2018 7:26 AM
To: main@....io
Subject: Re: [nw-digital-radio] blueDV; Windows 7 & ThumbDV 3000

 

You must issue a 4000 Group call  before you go to a second TG. Try that.  If that does not take care of the "negative lock" then I would uninstall blueDV and reinstall it. Every time you start blueDV you will need to issue a link command. 


Re: blueDV; Windows 7 & ThumbDV 3000

Douglas F. Enoch
 

Thank you very much the.   4000 issue was the problem.  But, I am not sure about what “issuing a link command” is??   Doug…KD8YVD

 

From: main@nw-digital-radio.groups.io [mailto:main@nw-digital-radio.groups.io] On Behalf Of n9ko@...
Sent: Wednesday, May 02, 2018 7:26 AM
To: main@nw-digital-radio.groups.io
Subject: Re: [nw-digital-radio] blueDV; Windows 7 & ThumbDV 3000

 

You must issue a 4000 Group call  before you go to a second TG. Try that.  If that does not take care of the "negative lock" then I would uninstall blueDV and reinstall it. Every time you start blueDV you will need to issue a link command. 

Re: blueDV; Windows 7 & ThumbDV 3000

Cal N9KO
 

You must issue a 4000 Group call  before you go to a second TG. Try that.  If that does not take care of the "negative lock" then I would uninstall blueDV and reinstall it. Every time you start blueDV you will need to issue a link command. 
blueDV; Windows 7 & ThumbDV 3000

Douglas F. Enoch
 

Can someone help?  I have a 2.2 GHz Lap Top; Windows 7; blueDV latest version(09499); a new ThumbDV 3000.  When I installed it:  (1) it transmitted and received on group 3100 the first time but not the second time?? (2) it did still receive 3100. (3) rechecked all settings.  (4) then switched to Tac 311 which it displayed but it still received 3100?? (5)  Switched back to 3100 but Now the Prompt says “negative Lock”?? (6) It will not lock on anything??   The only video for this installation is from England not US and is not complete info on all Boxes.  Also requires info not supplied??  Is there a written install list or better video?  Please reply if you have a suggestion.  I am 71, disabled and visually impaired.  73,  Doug…KD8YVD   doug.enoch@...
Re: Setting up D-STAR repeater

Jim Kusznir
 

thanks to both of you!  

As it stands, I have also been an unofficial advisor to W7UQ when they needed some help getting back on their feet.  I've spent many hours in both club's shacks, and we have a pretty good and friendly relationship.

I'll get them started on the pi repeater gateway.

--Jim

On Tue, May 1, 2018 at 7:58 AM, John D Hays - K7VE <john@...> wrote:
Yes.  You can use ircddbgateway with a Raspberry Pi -- see https://nw-digital-radio.groups.io/g/udrc/wiki/Configuring-ircDDBgateway#A-Repeater-on-an-Icom-ID-RP2C

I used to belong to the W7UQ club, but won't hold that against you :)

I would be glad to help you sort it out.

On Tue, May 1, 2018 at 7:30 AM, Jim Kusznir <jkusznir@...> wrote:
Hi all:

I'm helping mentor a college ham club that has an Icom D-STAR repeater hardware (UHF radio module + controller) that was at one time a full D-STAR repeater.  Years ago, the networking and matching server got disturbed, and it has been operating in "standalone" mode for quite some time.  

The specifics of the repeater location means that traditional servers located at the "tower site" are inappropriate, so the generation of students who got it up did some "network magic" and got it tunneled back to a data center where a VM ran the D-STAR repeater.  I remember getting the software and required networking in place was quite a challenge.

Now, I understand that there are additional options available, possibly even options that allow using a Raspberry Pi as the D-STAR server.  Is this correct?  Can others point me to where to get the server software (any variants -- Icom or 3rd party) that would work with the Icom repeater hardware?

Thanks!
--Jim, K7LL
advisor to W7YH WSU Amateur Radio Club Rho Epsilon




--

John D. Hays
Edmonds, WA
K7VE

   
Re: UDRX ???

John D Hays - K7VE
 

Marc -- the UDRX project had languished for too long and has been discontinued.  The current focus of NW Digital Radio is outlined here -- http://nwdigitalradio.com/2018-state-of-the-union/  

This decision was not taken lightly.  Rest assured we are still interested in providing solutions in the space that the UDRX envisioned and we will have future products in the space, but likely taking a different approach.

Right now we are working on projects outlined in the "State of the Union", some of which will be available for view at Hamvention in a couple of weeks.

On Tue, May 1, 2018 at 9:16 AM, Marc Lacy <KD7RYY@...> wrote:
I see on the website that the UDRX is no longer listed. What has happened?


--

John D. Hays
Director

  
UDRX ???

Marc Lacy
 

I see on the website that the UDRX is no longer listed. What has happened?
Re: Setting up D-STAR repeater

John D Hays - K7VE
 

Yes.  You can use ircddbgateway with a Raspberry Pi -- see https://nw-digital-radio.groups.io/g/udrc/wiki/Configuring-ircDDBgateway#A-Repeater-on-an-Icom-ID-RP2C

I used to belong to the W7UQ club, but won't hold that against you :)

I would be glad to help you sort it out.

On Tue, May 1, 2018 at 7:30 AM, Jim Kusznir <jkusznir@...> wrote:
Hi all:

I'm helping mentor a college ham club that has an Icom D-STAR repeater hardware (UHF radio module + controller) that was at one time a full D-STAR repeater.  Years ago, the networking and matching server got disturbed, and it has been operating in "standalone" mode for quite some time.  

The specifics of the repeater location means that traditional servers located at the "tower site" are inappropriate, so the generation of students who got it up did some "network magic" and got it tunneled back to a data center where a VM ran the D-STAR repeater.  I remember getting the software and required networking in place was quite a challenge.

Now, I understand that there are additional options available, possibly even options that allow using a Raspberry Pi as the D-STAR server.  Is this correct?  Can others point me to where to get the server software (any variants -- Icom or 3rd party) that would work with the Icom repeater hardware?

Thanks!
--Jim, K7LL
advisor to W7YH WSU Amateur Radio Club Rho Epsilon




--

John D. Hays
Edmonds, WA
K7VE

   
Setting up D-STAR repeater

Jim Kusznir
 

Hi all:

I'm helping mentor a college ham club that has an Icom D-STAR repeater hardware (UHF radio module + controller) that was at one time a full D-STAR repeater.  Years ago, the networking and matching server got disturbed, and it has been operating in "standalone" mode for quite some time.  

The specifics of the repeater location means that traditional servers located at the "tower site" are inappropriate, so the generation of students who got it up did some "network magic" and got it tunneled back to a data center where a VM ran the D-STAR repeater.  I remember getting the software and required networking in place was quite a challenge.

Now, I understand that there are additional options available, possibly even options that allow using a Raspberry Pi as the D-STAR server.  Is this correct?  Can others point me to where to get the server software (any variants -- Icom or 3rd party) that would work with the Icom repeater hardware?

Thanks!
--Jim, K7LL
advisor to W7YH WSU Amateur Radio Club Rho Epsilon
locked Re: D-STAR AT DAYTON HAMVENTION(R) 2018

hdk1220@...
 

Thank you

Harvey
Harvey Kolodner
WA3GTL

On Mon, Apr 30, 2018, 2:32 PM John D Hays - K7VE <john@...> wrote:
People can carry their torch all they want -- the point is, NW Digital Radio is not the inventor of D-STAR or AMBE and this is just unwarranted noise here.  I don't want people to unsubscribe from this list, which is a communication vehicle for NW Digital Radio company and their users, for too much noise.

As pointed out, all sorts of proprietary technology is in every modern piece of equipment we use.  Remember, even FM and SSB were patented (proprietary technology).

If people want to continue this debate, please move it to an appropriate list.



On Mon, Apr 30, 2018 at 10:46 AM, Steve McGrane <temporarilyoffline@...> wrote:
Ultimately, somebody has to speak to the unpopular things.  Sure, its
a lot of noise, but at the end of the day, the rules say something to
the effect of "no coded transmissions" and "no pecuniary interest".

I "get" what he's saying/trying to do and I appreciate that somebody
is carrying the torch.

How many of us have an iPad 1 that is just about completely useless
these days?  Imagine if it was an open platform and you could load a
functional OS on it and keep on browsing the internet and playing
videos? (Without being labeled a criminal)

I have enough dead apple gear sitting on shelves that I won't buy
anymore of it, even if I have to pay extra to get something from
somebody else.

On Mon, Apr 30, 2018 at 12:24 PM, Tony <w7efs@...> wrote:
> It appeared to me that someone had an AMBE "chip" on their shoulder, and it
> isn't you, Bob.
>

--

John D. Hays
Director
881 - 900 of 2575  
More
Home Messages Hashtags Subgroups Wiki About Features Pricing Updates Terms Help Twitter