Re: UDRX Processor Board Was: 44 addresses / JNOS 56K / Gateway Security ?
Donald Jacob <wb5eku@...>
Have you looked at the Beagle bone Black?
On Mar 27, 2015 3:03 PM, "'John D. Hays' john@... [UniversalDigitalRadio]" <UniversalDigitalRadio@...> wrote:
|
|
|
|
Re: UDRX Processor Board Was: 44 addresses / JNOS 56K / Gateway Security ?
"John D. Hays" <john@...>
Hi Richard, To maintain the price point for the UDRX, we need something in the $50 and below range (including CPU, Memory, Network, and USB interfaces). The interface to the radio requires a SPI bus, I2S bus, and various GPIO. Our DSP code is fixed point, so highly efficient and doesn't strain a CPU. However, having multiple cores, plenty of RAM, etc. is important for applications. We have been watching various boards but a lot of otherwise good candidates are lacking one or more of the needed interfaces. We have no video processing needs in the radio. The Raspberry Pi processors put Ethernet on the USB bus but for normal operations should be sufficient, but it is one of the questions we have about the board. Did you see any boards that match the listed items that we should look at?
On Fri, Mar 27, 2015 at 2:50 PM, myyahoo@... [UniversalDigitalRadio] <UniversalDigitalRadio@...> wrote:
|
|
|
|
Re: UDRX Processor Board Was: 44 addresses / JNOS 56K / Gateway Security ?
myyahoo@...
I just attended the Embedded Linux 2015 conference, and there are a lot of choices (and a varying price range).
e.g., at $99 Intel had an Atom-based board with full-speed GigE, SATA, USB3, HDMI, and other interconnects. It was running at about 4 watts while doing HD video decoding. I have a Raspberry PI 2, and while it has more processing power than the original (four, faster cores instead of one slower core), it is still constrained for I/O. If we don't need the I/O, the $35 price tag is very attractive. I'm putting GNUradio onto it to see how well it does. - Richard
|
|
|
|
Re: 44 addresses / JNOS 56K / Gateway Security ?
Barry Volpe <ag6wk4bv@...>
Steve, Very nice write up. I read "the groups" (so my comments are for what I see in general) but rarely engage because I can take what I want and throw the rest out as I please in that way. I have to say that it didn't matter really what you said here (although definitely interesting and I understand the discussion of not reinventing something and following a broad standard that is already in place) and you rolled it out well in an enjoyable manner. The "groups" would bode well if we all followed this in some way, shape or form. 73, Barry AG6WK
On Thu, Mar 26, 2015 at 8:38 PM, Steve Stroh N8GNJ steve.n8gnj@... [UniversalDigitalRadio] <UniversalDigitalRadio@...> wrote:
|
|
|
|
UDRX Processor Board Was: 44 addresses / JNOS 56K / Gateway Security ?
"John D. Hays" <john@...>
Clarification on comments referenced by N8GNJ NW Digital Radio is looking at
alternative “off the shelf” computer boards. The Raspberry Pi 2
is a candidate, but we are still in the investigative stage -- no selection has been made. We have
certain requirements for interfacing the radio to such a computer
board. We believe that using such an “off the shelf” board
could expedite delivery of the UDRX-440 as the board that was
designed a couple of years ago uses a less available SOC processor,
which now has extended lead times.
We also believe this will allow the UDRX to evolve with newer processors as they become available, providing increased speed and functionality over time. The software effort to move from one Debian based ARM processor to another is minimal as we largely use drivers already in the operating system and any additional drivers that we might develop will mostly be a recompile. All application software should also either run or simply require a new compile.
We also agree that hearty and widely used computer platforms will enhance the delivery of even more solutions based on the UDRX architecture.
|
|
|
|
Re: 44 addresses / JNOS 56K / Gateway Security ?
Steve Stroh N8GNJ <steve.n8gnj@...>
Wow... ignore this list for a month, and some interesting discussions bloom!
toggle quoted messageShow quoted text
This might focus the discussion a bit more. At the MicroHAMS Digital Conference last weekend in Redmond, WA, Bryan Hoyer of NWDR (UDRX) confessed ruefully that technology had passed THEM by. The UDRX has two halves - an ARM-based computer board, and the RF board. The amazing thing is that the off-the-shelf-for-$35 (really... just gotta look hard) Raspberry Pi 2, with its quad core processor and 1 GB RAM, was now cheaper AND more capable than the computer board in the UDRX. So, since the UDRX still hasn't shipped :-(... NWDR is going to spin the design one more time and :-( and make the Raspberry Pi 2 the computer board. When I asked if I had it right... that the RF board was just going to glom on top of the Raspberry Pi 2, Bryan stated "There will be NO glomming" :-) Which I took to mean that they're going to do a careful design. But... now they're going to have to redo their hardware... AND software... again... perhaps to be compatible with more standard Linux distros common on the Raspberry Pi. But, we're going to get a more capable... and fun... UDRX. Eventually :-( What does the UDRX change? For starters, watch this video - https://youtu.be/SmyVEwjhG_k... or at least the last ten minutes of it. David Rowe discusses the concept of a TDMA repeater. Think digipeater (as in single frequency) only the T/R switching is done at 5 mS intervals. Yep - a REAL TIME (close enough for humans) single frequency repeater. He's going to do it with a minimal SDR and good software, but there's nothing in David's concept that the UDRX can't already do. Remember all the hype about 2.4 GHz Wi-Fi hobbyist mesh networks - every experimenter was a node in the mesh? And more recently the ham mesh based on the little blue routers? Good idea, but lousy technology. Hams had pretty good "mesh networking" 20 years earlier - remember Net/ROM? Good range - the network covered entire regions (and small countries in Europe), but it was low capacity (1200 baud, Z80's, 1 MHz, 32 MB RAM - nuff said). So fast forward 20... 30 years... and now we have the technology to marry the longer-range radios with decent compute power and better RF technology. Let 100,000 real-time digipeaters bloom at every ham's house... and apartment balcony. MANUAL spectrum coordination to minimize interference... that's laughable now. Let the MACHINES do it. We have ample spectrum when we don't have to worry about fossilized spectrum coordinations for reserved spectrum for ghost repeaters and affording duplexers that mandate fixed frequencies. We're going to have SO much fun playing with new RF technology - in 3-5 years, we're going to just blow past what's possible on commercial / public safety two-way networks. One guy, or a small team, with a great idea posts his alpha software and one weekend later hundreds of people are testing it for him. A few have 64 GB USB flash drives plugged into their UDRX for diagnostic logging that can be uploaded to the dev team to figure out where the holes in THAT project are. Don't like THAT project - there's dozens of others begging for participants. The potential is VAST, folks. We WILL get makers, hackers, etc. flooding in just to play with this stuff. There's going to be tech tests at Maker Spaces and Maker Fairs. There will be endless variants of SDRs for VHF/UHF as soon as it's abundantly clear to vendors (think Chinese radios, folks) that yes, there are legacy users of the Amateur Radio bands, but the old fart incumbents react in tens of minutes when the machines can adapt to changing conditions in milliseconds. So the old farts and their legacy modes will be properly classified as interference to the interesting things, and routed around. I've seen enough to believe that NWDR can make UDRX real, but they just haven't had the courage to pull the trigger on releasing anything less than a perfect design upon us, the great unwashed. I have some sympathy for that - my day job is frustrating, maddening, tiring tech support for a technical product. But at some point, to unleash the potential, we gotta have hardware in our hands to play, and for the code jockeys to hack on. Good news is that this is no longer a one-horse race, with us depending on NWDR, or nothing. There's other projects out there, and eventually one will pop loose with a good-enough SDR for VHF/UHF, and we're off. I vividly remember the Xerox 820 board? What a POS that thing was... but it was enough of a platform to start a revolution in hundreds... thousands (?) of BBS'. All we need is a good-enough SDR for VHF/UHF and we'll really start having some fun. Steve N8GNJ On Fri, Feb 27, 2015 at 7:52 AM, 'Tyrell Jentink, KD7KUJ' tyrell@... [UniversalDigitalRadio] <UniversalDigitalRadio@yahoogroups.com> wrote:
|
|
|
|
Re: Thumb DV
"John D. Hays" <john@...>
What operating system? Which application?
On Thu, Mar 26, 2015 at 2:56 PM, dave conrad w9dec@... [UniversalDigitalRadio] <UniversalDigitalRadio@...> wrote:
|
|
|
|
Thumb DV
dave conrad <w9dec@...>
Trying to set up my new thumb dv but it is not being recognized. i believe I have the driver and software installed but nothing is happening.
any ideas? Dave W9DEC
|
|
|
|
Re: WinDV 3000U help
John Hays <john@...>
You need to request the beta for WinDV from DUTCH*Star Sent from my iPhone
On Mar 23, 2015, at 18:29, n5dww@... [UniversalDigitalRadio] <UniversalDigitalRadio@...> wrote:
|
|
|
|
WinDV 3000U help
n5dww@...
In the YouTube video by Budd WB7FHC there was an selection for the Thumb Drive in the options. My setup does not have that as an option. How do I get that option? Is it because of the driver? The device shows up on COM3 but doesn't allow me to hear any traffic on whatever gateway choose. I need guidance to resolve my problem from the group who has been in D-Star longer that I have. Bob N5DWW
|
|
|
|
Re: ThumbDV on WinBook
Steven Brichta <purelightimages@...>
|
|
|
|
ThumbDV
k8khw@...
I received my ThumDV today and all worked very well. I tried it on Windows XP And Windows 7 Home, It was plug and play on both. Were using WinDV software which also has worked with no issues. Received great audio reports as well. Randy K8KHW
|
|
|
|
AMBE-3000 vs AMBE-2020
"John D. Hays" <john@...>
|
|
|
|
DV3000 usb vs rpi card
ka1ifq <ka1ifq@...>
Does anybody know or have tested which one of these uses less overhead on the Rpi or is there much difference between the overhead of serial over usb vs straight serial.??
-- OpenSuse Desktop (13.1)
|
|
|
|
Re: My ThumbDV won't work
ve3jx@...
Alas, fat fingers. "the screen goes back, then blue with text" should read: "the screen goes black, then blue with text". Sorry about that. Dave VE3JX
|
|
|
|
Re: My ThumbDV won't work
VE3JX <ve3jx@...>
Alas, I knew it was too good to last.
When I did the disable/enable a second time,
later on the same day, the screen goes back, then blue with text, with
indications in the text on the screen that it had something to do with
the FTDI driver, or as near as I can figure out. Once it comes back from
the Windows restart, then everything is okay . . . until the next nap
time.
Cheers,
Dave Hayes VE3JX
|
|
|
|
Re: My ThumbDV won't work
VE3JX <ve3jx@...>
Hi Dean,
So great to hear from you!
As you can see from my original message, I did toggle
the disable/enable button for the 'USB Serial Converter' which generally
resulted in a Windows crash.
However, you may be asking if I did the disable/enable
thing with the 'USB Root Hub'? I can't seem to be able to do that.
However, I did go back to the 'USB Serial Converter' in
the Device Manager list and redid the disable/enable thing, and it worked . . .
this time, without the blue screen of death, hi hi.
When it is up and running, my ThumbDV seems to work very
well.
Cheers,
Dave Hayes VE3JX
Sun Mar 8, 2015 6:47 pm (PDT) . Posted by:"Dean Gibson AE7Q" dean_ae7q> Try disabling and re-enabling in Device
Manager. Not a permanent > solution, but easier than rebooting. >On 2015-03-08 16:39, ve3jx@... [UniversalDigitalRa >> Thanks John. I tried this, i.e. ticking off the power management >> function on all these 'hubs' >> suckers, which is a bit strange to me. Anyway, the boxes stayed >> unclicked, but the problem is still there. It will not wake up unless >> reseated or the PC is restarted. >> >> I went into the same list as the 'hubs' but clicked on 'USB Serial >> Converter' >> toggling this, it seem to work at awakening it. All the other times >> (maybe 4 or 5), I got among other things the blue screen of death. >> >> I wonder, is there a certain vintage of FDTI driver that I should be >> using? The PC (Windows 7 Home Premium) automatically chose version >> 2.10.0.0 Should I be using one of the archived drivers from your >> website, perchance? >> >> Cheers, Dave Hayes VE3JX >>
|
|
|
|
Re: DV3000 Speeds
Robert Garcia <robert@...>
John, Thank you for the reply. I will scrub the datasheets again as I seem to have missed the recommendation on that speed. The cause for my question and wonder is that the DVSI branded AMBE-3000 USB sticks are set to 460,800 from the factory and there are many applications written around that speed. Needless to say my attempt to modify my USB stick to run at that speed ended when I broke one of the pins off of the IC. I am hoping a future release may give us user selectable speed settings for the ThumbDV. Robert N5QM
On Mon, Mar 9, 2015 at 1:32 AM, 'John D. Hays' john@... [UniversalDigitalRadio] <UniversalDigitalRadio@...> wrote:
|
|
|
|
Re: DV3000 Speeds
"John D. Hays" <john@...>
If you look at the schematic at http://nwdigitalradio.com/wp-content/uploads/2012/04/DV3000DS.pdf in the upper right you will see where you cut the default jumper and then can jumper for the higher baud rate. You will also need to increase (double?) the init_uart_clock in /boot/config.txt (and reboot). I haven't tested production units at the higher rate and the DVSI notes indicate the 230.4 rate is optimum, but worth a go.
On Sun, Mar 8, 2015 at 8:26 PM, robert@... [UniversalDigitalRadio] <UniversalDigitalRadio@...> wrote:
|
|
|
|
DV3000 Speeds
robert@...
Has anybody run and/or tested the DV3000 running at 460.8K baud instead of 230.4K baud? I have an application for them, but need them to run at the higher data rate. Robert N5QM
|
|
|