Posts Tagged ‘Homebrew’

Update 10.10.2018

24 October 2018

It has been a while since I posted here…once again. I don’t know why that is, but it certainly hasn’t been for lack of anything to post.

Photography-wise, most of my focus lately has been on my old 400mm Tokina. Getting it into sharp focus seems to be an almost impossible task. “Almost” because I refuse to believe it is impossible. For the longest time, I’ve been trying to get “focus trap” to work on the lens with the Pentax K3. No matter what I tried, it just wouldn’t work. It worked with the K10 and *ist, so it was frustrating not being able to use that method.

Then I came across something on the internet that made me search with some terms I would never have thought of using. Sure enough, it turned out that with the K3, Pentax created a setting in the Custom menu to allow or disallow that. Not only that, the name of the menu item, at least to me, isn’t intuitive. Sharp Capture. In hindsight, the name does make some sense. So, now I have the ability to use focus trapping.

Even with that, though, it’s still not locking in with the sharp image I remember. Note to self: put the 400mm on the K10 and/or *ist and verify it works like I seem to remember.

I think ,however, that there is a slight difference where the focal plane is compared to the K10 and *ist bodies. That doesn’t make much sense, but right now it’s the only answer I have. Even with the other manual lenses that I remember working properly on the other two bodies, I have to focus past the subject to get a sharp image.

Right now, my plan is to combine focus trapping with the multiple shot mode. That way, when the focus trapping triggers the rapid sequence of images taken while still adjusting focus manually should hopefully include at least one image in which the image is sharp. Or at least sharpest.

We’ll see.

Well, that idea of focus trapping plus multiple shot mode didn’t work. I guess I’m going to have to try and find another way to do this.

The ham radio arena is the next area to bring up to date. Here, the use of the straight key for Morse code as my computer input keyboard has indeed taught me most of the characters. BUT that only taught me to transmit. Recently, a ham who agreed to be an Elmer (aka Mentor) for me sent me a simple device that activates a LED to the tune of the dits and dahs of Morse code.

I bring that up because once I got this hooked into my radio and everything tuned, I had a chance to actually see some Morse via the LED. I was able to, for the first time, clearly and without any of the usual difficulties of differentiating them, see the Morse code. And that segues nicely into I was able to see the dah-dit-dit but I had absolutely no idea what dah-dit-dit stood for. I actually needed to mentally imagine sending dah-dit-dit with a straight key before I could make the connection to the letter D.

And so I found out what I was afraid of actually happened.

I can now transmit a lot of the characters without even having to think about their dit and dah components. The reverse, however, is not true. I could not decipher that visual representation with the same ease I can send it.

Oh, boy.

Now I’m going to have to add a LED to the straight key I use with the computer. There’s a LED on the Teensy board that flashes as I key the characters but it’s under the board holding the key and not visible. Rats! That would have been a perfect solution.

At least it’s a relatively easy fix and since the onboard LED already flashes while keying, I can use that same pinout, so no code modifications needed. I just have to figure out what color LED to use.

Writing. This is where I hang my head in shame.

I’ve done some editing for other authors, but I’ve done precious little writing of my own. As I mentioned last time, I did start a new Pa’adhe story, but nothing past the opening scene and setting up the tale. I have a reasonably decent story for this one, and it’ll provide the backstory for Scarle, but just sitting down and writing just hasn’t happened. With any luck, writing and posting this will get me going on it.

Unfortunately, I’ve been spending a fair bit of time programming. Unfortunately because otherwise I might have been writing instead.

I bought a cheap 3.5” TFT LCD display that came with NO instructions or paperwork at all. It took me several months to finally locate what seemed to be the same display being sold by another vendor with tutorials and examples. So, that’s now up and running on one of my Arduino Unos.

Plus I’m waiting for a part for a 2004 display (20 chars x 4 lines) so that I can use IIC protocols to program it for use with ham radio. This will be a potential display for viewing and decoding Morse code that comes over the air to my radios. It’s intended to just plug into the headphone jack of the radio and display the detected audio and Morse. Eventually I want to modify that to provide the option of showing, selectively, the following: (1) a bar graph or “LED” display of the dits and dahs, (2) a string of dits and dahs such as …. . .-.. —, or (3) the actual translation of the code to display HELLO. Maybe even other modes, although at the moment those three seem to cover all bases for me.

UGH! That’s enough, this is already longer than planned and there’s more like trips. I’ll save those for another time.

Advertisements

Morse in a New Year

25 January 2018

One of the things I’ve done in the past few weeks is build a new keyboard for this computer. It’s what’s called a straight key in radio circles.

Telegraph key being used as a USB keyboard on my computer.

Yep, it’s real. And it works. I actually used it to type (key?) in some of this blog post. It’s literally just an USB cable, a Teensy 3.1, and a Morse code key. I’m going to mount the Teensy in the bottom of the board, but for now it’s on the protoboard until I get all my code changes done.

So, why? What the heck would I do that for when I have a perfectly good computer keyboard?

At the start of 2018 I was once again thinking I wanted to find a way to really make myself learn Morse Code. A way that would guarantee I would learn it.

Among other times, I want to use my mobile radio when I’m out and about but don’t have the computer with me. Normally, I use PSK-31 which is computer-to-computer via amateur radio. For that, obviously, I have to have a laptop with me. The thing is, I don’t always have one with me and sometimes I will be out in the Owyhees at a spot where I’d like to see if I can have a QSO (conversation) on the radio. No laptop, no QSO.

The obvious question is, why don’t I just sit down and learn it?

Well, I could, but I’m lazy and I know it. Also, I already know about half the alphabet and numbers and a punctuation mark or two. So, what’s the problem? It’s no fun for me just sitting and memorizing the International Morse Code. I can, but that’s boring.

I began to wonder if I could somehow replace my QWERTY keyboard with a straight key. I took the path of least resistance and started searching online to see if anyone had done something like this with an Arduino or Teensy. It turns out several people had and made their code and schematics freely available.

After studying a few of them, I zeroed in on Nomblr’s rebuild of her dad’s old telegraph key. Her code was clean and the schematic about as simple as it ever gets so I leveraged off her work. The good thing was I happened to have a Teensy 3.1 in my “hell box” (as in “where the hell is it?”).

I dug out the Teensy 3.1, connected the straight key to the Teensy, plugged the USB cable into the Teensy and the computer. For testing, I simply downloaded Nomblr’s code to the Teensy, opened up Notepad++, and tried the key. I used the programmer’s holy first test: …. . .-.. .-.. — .– — .-. .-.. -..

To my immense pleasure, the letters started showing up in Notepad++ right away: hello world.

OK, so I had to look up two of those letters. That’s the whole point. I can now use the telegraph key to write on the computer, and to do so, I have to learn the Morse code letters I don’t know. Sure, it’ll be slow for a bit here and there but over the next few days or weeks I’ll be up to speed. And I’ll have learned the International Morse Code much faster than otherwise. Much.

I have already made some tweaks to her code and am in the process of adding some extra bells and whistles that I think will be useful to me. For example, I’ve added in a couple of prosigns like CQ and SOS. Keying in SOS, for example, corresponds to pressing F1 on a QWERTY keyboard. I’ve added in the punctuation from the International Morse Code table, and I’ve set up “……..” which is Morse for “error” to mimic pressing the backspace key on a regular keyboard.

Now I’ve got a fun and productive way to learn Morse code. One that not only ensures I’ll learn it, but also lets me practice sending and have fun doing so.

Soon, I’ll be on the airwaves with CW.

Future tweaks to this setup include adding a way to adjust the words-per-minute of the program. Currently it’s hard-coded and to change it to work smoothly with a faster or slower WPM I have to modify the code and dump it to the Teensy. Not difficult, but also not ideal, especially as my speed improves.

I do want to increase my speed, but one caveat is that I need to ensure that I don’t send faster than I can receive. For that reason, among others, another mod is to add a display to show what my actual WPM is as I use the key.

As to why a straight key instead of an iambic paddle…I’m of German descent, which gives me a Stubborn bonus of +4. 😉

Time Passes

6 September 2017

It’s true, time passes faster when you’re having fun. It’s also true that if you stop doing something for a while, it’s much harder to resume. At the same time, at least for me, having that break with regular writing and playing on the radio makes it harder for me to start anything else since I have those two things hanging over my time. I want to get back into them, but…tomorrow? And then because of that attitude, I’m not eagerly starting new projects or doing other things that I want to. Not because I can’t or don’t have time, but because I have those two things hanging over me and I can’t get myself going on anything.

Milky Way from Coyote Grade in the Owyhee Foothills.

I did get out and do some Milky Way photography. It turned out OK, and I had a blast. With all the smoke lately, I haven’t gotten back out to shoot more astrophotography. Or any photography, actually. The drive just isn’t there and to be honest, I’m reluctant to just go by myself. Not because I can’t, but because I know my wife doesn’t like me going solo into the Owyhees. And I’ve sort of gotten used to having someone else along.

Excuses. Just excuses.

I do need to go back out with some settings from that shoot and try doing more and specific adjustments to the camera to attempt to get better images. I also want to take one of my telescopes out and use it to track the camera. That way, I can get some images to try stacking and see how that works to get a better Milky Way image.

In spite of that, I did do a bunch of prep for the recent total eclipse of 2017. For that, I built myself a solar filter out of PVC pipe and gold mylar sheet. A preliminary test showed the filter worked, but I am not happy with it and will probably eventually replace the mylar with newer or something else. It’s just not perfect.

My homemade solar filter mounted on the lens I will be using for the 2017 solar eclipse.

 

The sun as shot through my homemade solar filter. It’s two layers of gold mylar secured between an inner and outer PVC ring.

One of my sisters lived right in the path of totality, so it was a simple matter to head to her place 45 minutes away and observe the eclipse there.

My setup while shooting the 2017 Total Solar Eclipse. We had 100% totality here.

I did get at least one decent image that I was really happy with, and one I was sort of happy with. And yes, you can see sunspots in my images, so I guess there actually are other decent images from the event.

Bailey’s Beads from the 2017 Total Solar Eclipse. You can also see some solar prominences.

 

Another shot of Bailey’s Beads as the sun moved out of totality.

 

Sunspots during the 2017 Total Solar Eclipse, along with the moon encroaching. This is early in during the eclipse. They’re easier to see in the full size image.

The same time I did the Milky Way shoot, I took my DJI Phantom 4 along and did some flying. I had been mentally rehearsing the remote controller stick movements for a 180 flyby where you spin around 180 degrees without stopping. Or put another way, you’re flying away from a spot looking back at it and at some point along the flight path you spin around to face the other way while you continue flying in a straight line. I’m happy to report I got the stick movements right and it worked pretty well.

And now we have a Purple Air Quality alert for the valley. That’s the color for “very unhealthy” with the next color being brick red and meaning “hazardous”. So, I’ll leave you with one last image, one that I took last night and that I call the Fire Moon. The color is due to the smoke in the air, of course.

The nearly full moon, discolored from the heavy smoke covering Treasure Valley, Idaho.