then I'll care about what "prominent members of the U.S. House of Representatives and the Senate" think about climate change.

Take a look at what James Inhofe (R-OK) who is chairman of the fucking Senate Committee on the Environmentthinks of global warming. TRIGGER WARNING: IF STUPIDITY UPSETS YOU DO NOT CLICK.

http://www.slate.com/blogs/fut...

Test equipment is allowed to transmit and receive on those frequencies. If it looks like a radio, it can't. I have a number of cellular testers hanging around here that can act like base stations, mostly because I buy them used as spectrum analyzers and never use the (obsolete) cellular facilities. Government has different rules regarding what it can and can't do in the name of law enforcement, although FCC has been very reluctant to allow them to use cellular jammers.

If you can afford it, something from Ettus would better suit your application.

That's not it, CRLF was a feature. How do you make strike-through text on a type-wheel printer? It automatically advances to the next position and it only has a fixed number of characters, you don't double it with strikethrough-a in addition to regular a. So you send a CR - carriage return - to return to first position, space your way over to the text to be striked out and make a ------- over it before you CRLF to the next line. And you have no idea how old knowing that makes me feel.

Unfortunately most of the projects I've been on are of the "We want to replace old system A and make a new system B that also has features X, Y, Z" variety. What they want from the new system is usually okay, it's somewhat documented already, you've identified some stakeholders, you can show them prototypes, you can ask for clarifications and their testing validates the feature. Developing new code for genuinely new features is actually quite easy and fun.

The old system on the other hand is more like software archaeology, nobody really seems to have the specs - or maybe a spec 1.0 from 10 years ago that's got nothing to do with reality - and if you're replacing it it's probably because it's crap, uncommented code in an arcane language with poor frameworks and third party components. So you dig and keep digging and try to implement something similar without knowing what's a feature and what's a bug, who'll come yelling if you break something or features nobody told you about and you weren't aware anyone was using disappear.

I had a bit of an epiphany today at work when i finally found out how structure a major piece of the redo I'm working on and I've so far spent ~2 months digging through that code. From a similar job I was doing in another area I thought maybe 2-3 months total, now I'm guessing it'll be 6-12 because of all the rework I have to make and every apparently simple thing has exceptions and special cases. It's wasn't my bad estimation, it's that the conditions are entirely different. Like comparing travel speed for a walk in the park to chopping your way through a dense jungle.

Good managers get my best guess.
Bad managers get my worst case.
Horrible managers get my resignation.

Tag: WORKS4ME

We think after we build this new PCB we can go for the croudfunded manufacturing run. It's mostly surface-mount, and we expect to sell assembled boards in this run, and then the next version will be fully-packaged radios.

Hi AC,

Matt Ettus has a story about a Chinese cloner of the USRP. The guy tells Chinese customers that it is illegal for them to buy from Ettus, they must buy from the cloner instead. Then, when they have problems and require serivce, he tells them to get it from Ettus. Who of course made nothing from their device sales and can not afford to service them.

This is not following the rules of Open anything. It's counterfeiting.

So, sometimes it is necessary to change the license a little so that you will not be a chump. I discussed the fact that the hardware is fully disclosed but not Open Hardware licensed with RMS, the software is 100% Free Software, and there is a regulatory chip you can't write. We can go for Respects Your Freedom certification that way..

I've paid my dues as far as "Open" is concerned, and Chris has too. This is all we can give you this time.

The case selection was so that we'd have at least one case that would work. We did not take much time on it. We'd be happy to have other people designing and selling cases.

The version after this one requires cases that look like real radios. That is going to be a bigger problem. We don't yet have a mold-design partner, etc.

We implement it as a chip that intercepts the serial bus to the VFO chip, and disallows certain frequencies. On FCC-certified equipment we might have to make that chip and the VFO chip physically difficult to get at by potting them or something. This first unit is test-equipment and does not have the limitation.

Anyone who is good at electronics can get around regulatory lockouts. We're not allowed to make it easy. But nor are we technically able to make it impossible.

U.S. regulation only allows Part 95 certified radios to be used on GMRS, and Part 95 requires that the radio be pretty well locked down. But all of those Asian imports are certified for Part 90 and there are lots of users putting them on both Amateur and GMRS. If FCC wanted to push the issue with any particular licensee, they could.

The D-STAR issue is not really ICOM's fault. JARL designed D-STAR (not ICOM) and put the AMBE codec in it because nobody believed that you could have a good open codec at the time. We now have Codec2 (a project I evangelized and recruited the developer) which is fully open. And we do have a software AMBE decoder in Open Source, although the patents won't let us use it. That is why I am working on the patent issue (as noted in the last slide of the presentation).

I know about the counterfeit FTDI chips, and Matt Ettus told me what has happened with the Chinese clone of USRP. We know what to do.

And it's because of No-Code. We looked at the licensing statistics and thought we'd preside over the end of Amateur Radio in our own lifetimes. That's the main reason I worked on no-code. There was really strong opposition among the old contingent, and ARRL fought to preserve the code for as long as they could. Someone even asked me to let Amateur Radio die with dignity rather than sully it with no-code hams. Gee, I am glad that fight is over.

Though a nice compromise might be to allow such things in certain bands only.

That is why there are different radio services. Hams really only have a few corners here and there of the radio spectrum. There really is a service for everyone, although you should be aware that the entire HF spectrum would fit in a few WiFi channels, and all of the Amateur HF spectrum would fit in one. So, we don't really have the bandwidth at all. And people who want the bandwidth on UHF already have WiFi and the various sorts of RF links, etc.

The internet really sucks and we don't want another one on ham radio. Nor could we possibly have the bandwidth to support one. The entire HF spectrum fits in just a few WiFi channels.

To satisfy the demands of the "it should be anything goes" crowd, we have CB radio. And there are all of the common carriers, etc.

So, I can't sympathize, and even if I did, there are not the technical resources there.

Sorry.

Except for cost. That's what powered the Android drive, it wasn't the technical superiority. There's probably more people gaming on phones and tablets than any other platform when you count Angry Birds, Candy Crush and such. Chromebooks running on Linux also seem to sell reasonably well for the same reason. If Valve can get a a range of steamboxes out there to sell to everything from a $99 box to sell freemium + $1-5 games to a $999 gaming rig to people who don't really care about having a desktop anymore with their tablet/convertible covering those needs there's probably a market for gaming boxes.

It does of course assume that you commit enough to get it off the ground. Nobody wanted to code for Android either before it got popular. And if Valve is backing off now that the Microsoft Store doesn't seem that big a threat after all, it might take many years. But Linux is well propped up by servers, supercomputers, embedded, cell phones, tables, chromebooks... it's not going away. Particularly not in the direction we're going with more cloud, less local it's certainly not going to get worse.

The driving force behind Mesa is Intel, they're certainly not going away. Pretty soon they'll hit the big OpenGL 4.0 and it seems almost all the prerequisities for 4.1 and 4.2 are done once they get over that hurdle. And they certainly want to keep their OpenGL ES current if they want to play in the x86 smartphone/tablet market. AMD also apparently like their open source driver for embedded/custom projects, less legal hurdles for customers who want full control. So maybe they don't win, but I don't see how they could lose much terrain either.