Lasagna in Paradise! Debbie cooked up a huge batch (three full-sized pans like the one at right). Most of this is going in the freezer, but one corner of one pan was our dinner tonight. It was brains-fall-out-on-the-table great!
The quantity of food that went into this is staggering: six pounds of hamburger, four pounds of sausage, nine big cans of tomato sauce, six cans of tomato paste, a half-dozen boiled-down tomatoes from our neighbor's garden (the last of the season, dang it!), three big boxes of lasagna noodles, nearly a gallon of ricotta cheese, several pounds of mozzarella cheese, a pound of Parmesan cheese, and all sorts of spices.
Now I'm in a pasta coma :) And I will be again, quite a few times over the winter!
Saturday, November 21, 2015
Jonah Goldberg has long been...
Jonah Goldberg has long been ... one of my favorite political commentators. The fact that he's a fellow dog lover doesn't hurt my opinion of him at all :) Here's one paragraph from his column this week, describing what happens when Zoë (one of his two dogs) runs in to steal a squirrel trapped by Pippa (his other dog):
The column, as always, is well worth your time to read...
Now I should say, I’m a big softy when it comes to these things. I hate to watch Zoë kill anything, but I nonetheless admire the commitment and passion. She raced-in, her paws barely touching the earth. She barreled Pippa out of the way; the little spaniel bouncing off the dingo like Robert Reich in a windstorm. Zoë grabbed the “beast,” hurling it into the air and catching it again in her mouth with a skill usually associated with frat guys’ tossing chicken McNuggets into each others’ mouths. When I yelled at her to drop it, I might as well have been commanding the statue at the Lincoln Memorial to dance. My commands were drowned out by the Viking battle drums beating in her ears. My futile attempts to grab her collar only encouraged her to run away and chomp more ferociously. I wasn’t trying to save the squirrel’s life. That would be like trying to revive the Thanksgiving turkey by chanting over the leftover-sandwiches. But I didn’t like the prospect of the bowel stewing that might accompany a breakfast of raw squirrel, healthy or sick. Finally, her war dance concluded, and the awareness came that she could not bring home her trophy, never mind enlist my wife in her cause of making a necklace of squirrel skulls. She ran off and buried it. Somehow I don’t think it was respect for the dead that motivated her.The world needs more writing like that!
The column, as always, is well worth your time to read...
Civil asset forfeiture abuse...
Civil asset forfeiture abuse... This program is one of those things that makes me ashamed of my country. It quite literally gives judges and law enforcement a license to steal from innocent citizens. If you find that hard to believe, then you need to do some reading (and follow my link here to find a source). This year the program has reached a new milestone: the cops are stealing more from citizens than the crooks are. A lot more.
Here's some more from Reason...
Here's some more from Reason...
The bits are flying in Paradise!
The bits are flying in Paradise! At about 4:30 this morning, I braved the cold (22°F) and walked out to the shed with my arms full of networking gear. Except for the Ethernet isolator, this was all stuff I bought and configured last January, and then just stored until I got the cabling all done. This morning I plugged it all in with the router, switch, and wireless router all sitting on top of my jointer, and ... it all worked, immediately. My initial test was to connect my phone to the shed's (new) wireless network, and that worked perfectly. Then I came back in the house and logged into each piece of equipment's administration page and checked it out. All working correctly!
The only anomaly I noticed was that the Ethernet link between the house router and the shed router took an unusually long time to come up – around 45 seconds. Usually an Ethernet link will establish in under 10 seconds. I think what's going on there is that the Ethernet isolator is powering up. It draws what little power it needs from the data lines, and I'm guessing that it takes a little while to charge its storage capacitors (you could think of them as tiny rechargeable batteries).
Given that this is a residence, we have quite the network installed here. In the house, there's a cable router which feeds the main house router, which in turn feeds a 20 port switch, the shed's router, and two wireless routers. In the shed there's the main shed router, which feeds another 20 port switch and a wireless router. When I finish moving my office from the house to the shed, we'll have a fairly even split of networked gear between the two buildings, most likely using 8 to 10 of those switch ports in each place. That leaves us plenty of room for expansion!
Comcast may have notoriously bad service, and they clearly do inject content into insecure web pages (HTTP vs. HTTPS), but ... they are delivering some nice, fast Internet to us: 180 mbps down, 24 mbps up, quite consistently. That's way faster than we used to have in Jamul, so for us this is a huge step up. Partly this is just plain luck: we live on the highway that the main Comcast feed for the southern part of Cache Valley runs alongside. The cabin we've purchased for my brother isn't quite so lucky – Comcast doesn't even service that area. Instead we're connecting him through a wireless ISP (Rise), at 50 mbps down and 5 mbps up. Even that is way better than what he's used to, so I'm expecting a big smile from him when he connects for the first time...
The only anomaly I noticed was that the Ethernet link between the house router and the shed router took an unusually long time to come up – around 45 seconds. Usually an Ethernet link will establish in under 10 seconds. I think what's going on there is that the Ethernet isolator is powering up. It draws what little power it needs from the data lines, and I'm guessing that it takes a little while to charge its storage capacitors (you could think of them as tiny rechargeable batteries).
Given that this is a residence, we have quite the network installed here. In the house, there's a cable router which feeds the main house router, which in turn feeds a 20 port switch, the shed's router, and two wireless routers. In the shed there's the main shed router, which feeds another 20 port switch and a wireless router. When I finish moving my office from the house to the shed, we'll have a fairly even split of networked gear between the two buildings, most likely using 8 to 10 of those switch ports in each place. That leaves us plenty of room for expansion!
Comcast may have notoriously bad service, and they clearly do inject content into insecure web pages (HTTP vs. HTTPS), but ... they are delivering some nice, fast Internet to us: 180 mbps down, 24 mbps up, quite consistently. That's way faster than we used to have in Jamul, so for us this is a huge step up. Partly this is just plain luck: we live on the highway that the main Comcast feed for the southern part of Cache Valley runs alongside. The cabin we've purchased for my brother isn't quite so lucky – Comcast doesn't even service that area. Instead we're connecting him through a wireless ISP (Rise), at 50 mbps down and 5 mbps up. Even that is way better than what he's used to, so I'm expecting a big smile from him when he connects for the first time...
Syria conflict for dummies!
Syria conflict for dummies! Passed along by reader Simi L., who is responsible for a great many belly laughs from this writer:
President Assad (who is bad) is a nasty guy who got so nasty his people rebelled and the Rebels (who are good) started winning.
But then some of the rebels turned a bit nasty and are now called Islamic State (who are definitely bad) and some continued to support democracy (who are still good).
So the Americans (who are good) started bombing Islamic State (who are bad) and giving arms to the Syrian Rebels (who are good) so they could fight Assad (who is still bad) which was good.
By the way, there is a breakaway state in the north run by the Kurds who want to fight IS (which is a good thing) but the Turkish authorities think they are bad, so we have to say they are bad whilst secretly thinking they're good and giving them guns to fight IS (which is good) but that is another matter.
Getting back to Syria. President Putin (bad, as he invaded Crimea and the Ukraine and killed lots of folks including that nice Russian man in London with polonium) has decided to back Assad (who is still bad) by attacking IS (who are also bad) which is sort of a good thing?
But Putin (still bad) thinks the Syrian Rebels (who are good) are also bad, and so he bombs them too, much to the annoyance of the Americans (who are good) who are busy backing and arming the rebels (who are also good).
Now Iran (who used to be bad, but now they have agreed not to build any nuclear weapons and bomb Israel are now good) are going to provide ground troops to support Assad (still bad) as are the Russians (bad) who now have ground troops and aircraft in Syria.
So, a Coalition of Assad (still bad) Putin (extra bad) and the Iranians (good, but in a bad sort of way) are going to attack IS (who are bad) which is a good thing, but also the Syrian Rebels (who are good) which is bad.
Now the British (obviously good, except Corbyn who is probably bad) and the Americans (also good) cannot attack Assad (still bad) for fear of upsetting Putin (bad) and Iran (good / bad) and now they have to accept that Assad might not be that bad after all compared to IS (who are super bad).
So Assad (bad) is now probably good, being better than IS (no real choice there) and since Putin and Iran are also fighting IS that may now make them good. America (still good) will find it hard to arm a group of rebels being attacked by the Russians for fear of upsetting Mr Putin (now good) and that mad ayatollah in Iran (also good) and so they may be forced to say that the Rebels are now bad, or at the very least abandon them to their fate. This will lead most of them to flee to Turkey and on to Europe or join IS (still the only constantly bad group).
To Sunni Muslims, an attack by Shia Muslims (Assad and Iran) backed by Russians will be seen as something of a Holy War, and the ranks of IS will now be seen by the Sunnis as the only Jihadis fighting in the Holy War and hence many Muslims will now see IS as good (doh!).
Sunni Muslims will also see the lack of action by Britain and America in support of their Sunni rebel brothers as something of a betrayal (might have a point) and hence we will be seen as bad.
So now we have America (now bad) and Britain (also bad) providing limited support to Sunni Rebels (bad) many of whom are looking to IS (good / bad) for support against Assad (now good) who, along with Iran (also good) and Putin (also, now, unbelievably, good ) are attempting to retake the country Assad used to run before all this started?
This should clear it all up for you. Just so you know I am not taking any questions on this subject!!!!!!!!!
Paradise ponders...
Paradise ponders... I worked some more this morning on my KABtronics clock kit – got the seconds decoder, LED drivers, and LED done. When I finished, I powered it up – and got nothing on the LED at all. A little inspection and I found a row of 7 resistors that I'd forgotten to install, and these were the current-limiting resistors for the LED segments. Once I actually loaded all the parts, it all worked on the first try. The circuit board now weighs perceptibly more than it did when I started, just from the weight of the 200 or so components I've mounted (and soldered). I'm in awe of the job the kit's maker did on it.
Yesterday afternoon, UPS delivered my Black Box SP426A Ethernet isolators. They were the last component I needed before installing a router, switch, and wireless router out in the shed – so that's what I'm going to be doing this morning. With any luck at all, I'll soon have network communications (including Internet access) out there!
Yesterday afternoon, UPS delivered my Black Box SP426A Ethernet isolators. They were the last component I needed before installing a router, switch, and wireless router out in the shed – so that's what I'm going to be doing this morning. With any luck at all, I'll soon have network communications (including Internet access) out there!
Friday, November 20, 2015
Burglary in Paradise!
Burglary in Paradise! A home invasion burglary, no less, with the robbers holding the homeowners at gunpoint. The pair were caught after a high speed chase. The two photos at right are the robbers, whom the sheriffs believe may be connected to a string of armed robberies in the county.
This has been the talk of the town for the past few days, as nothing even remotely like this has happened in Paradise within anybody's memory. So far as we can tell from the information at hand, the house in West Paradise (a couple miles SW of us) was targeted completely at random, as with the other burglaries attributed to this pair...
This has been the talk of the town for the past few days, as nothing even remotely like this has happened in Paradise within anybody's memory. So far as we can tell from the information at hand, the house in West Paradise (a couple miles SW of us) was targeted completely at random, as with the other burglaries attributed to this pair...
Muskrat in Paradise...
Muskrat in Paradise... Not a very happy one, though. This fellow fell into our basement window casement sometime last night. That's the third time this has happened since we moved here, and always when it was raining. This one was very aggressive compared with the other two – he attacked the stick I used to try and herd him into a box, instead of running from it like the other two. Maybe he didn't have his coffee this morning :) Instead of trying to herd him, I decided to just put an old 2x4 in the casement so he can climb out by himself. Eventually I think he'll figure that out...
Paradise ponders...
Paradise ponders... We're looking at buying the two parcels immediately adjacent to the cabin we just purchased up near Newton. These parcels would add about 10 acres to the area that my brother Scott could work with, and they come with water rights for irrigation water and a well. That means we could develop the parcels (add a well, driveway, etc.) and someday sell them. It also means that my brother could grow things on that land for the next ten or fifteen years, until the point we wanted to sell.
I've written before that there was a challenge to this plan – to wit, the parcels have the water rights (for irrigation), but no way to actually deliver the water to the property. The canal from which the water would be drawn is a mere hundred yards away, but for some reason the water company was denying permission to connect and draw water. We made our offer on those two parcels contingent on that problem being solved, and the sellers are in the process of attempting to do just that. I offered to help where it made sense.
It turns out that the very first step could use a particular attribute that I possess: being an outsider with no particular axe to grind with the water company. We needed to gather some information to help us understand the water company's position, so yesterday I met a member of the water company's Board. It was fascinating to hear the other side of the story.
It turns out there are two main issues.
The first is that the water company isn't certain that the parcels we've got an offer on are actually part of their designated area for delivering water to. That's because the parcels are just south of the southernmost end of the water company's distribution canal, an area that's close to (and possibly over) the edge of their “decree area”. That “decree area” refers to the decree that established the water company (along with a hundred or so other water companies in the area); that decree defines their distribution area.
The second is that this particular water company made their shares freely transferable, and that led to an unanticipated consequence. The way development of the area panned out, more people wanted water at the southern (downstream) end of their canal than on the upstream end. Because the shares were freely transferable, that led to a gradual shift in the share ownership toward the south. Eventually that got to the point where the capacity of the canal to deliver water was exceeded, and the only mechanism the water company had to control this was to start refusing to connect anyone with shares that originated upstream of the point where they wanted to draw water.
So...
For our sellers to get the water company's approval, they have to show two things. First, that the parcels are actually part of the decree area. That one is at least easy to attack – the sellers need to hire someone who can read the legal description of the decree area (gobbledygook to normal mortals) and figure out whether they are. Second, they have to show the provenance of the water rights are not from upstream. I'm not sure how they can do that, as it will require tracing the chain of share ownership. I believe (since water rights are real property in Utah) that all of this chain is recorded at the County office, so it might not be hard to do that.
On a completely different note, Debbie and I took a drive up the dirt road to Liberty last night. I was very sleepy (I'd gotten up particularly early yesterday morning), but nonetheless we saw some deer, about a million turkeys, a colony of muskrats, a kingfisher, and ... best of all ... a bald eagle. That eagle is almost certainly a migrator; this is the season they are flying south through our area. Hopefully we'll see more, but we got a great view of this fellow, just sitting up in a tree glaring at us. Or considering us for supper. Probably the latter :)
I've written before that there was a challenge to this plan – to wit, the parcels have the water rights (for irrigation), but no way to actually deliver the water to the property. The canal from which the water would be drawn is a mere hundred yards away, but for some reason the water company was denying permission to connect and draw water. We made our offer on those two parcels contingent on that problem being solved, and the sellers are in the process of attempting to do just that. I offered to help where it made sense.
It turns out that the very first step could use a particular attribute that I possess: being an outsider with no particular axe to grind with the water company. We needed to gather some information to help us understand the water company's position, so yesterday I met a member of the water company's Board. It was fascinating to hear the other side of the story.
It turns out there are two main issues.
The first is that the water company isn't certain that the parcels we've got an offer on are actually part of their designated area for delivering water to. That's because the parcels are just south of the southernmost end of the water company's distribution canal, an area that's close to (and possibly over) the edge of their “decree area”. That “decree area” refers to the decree that established the water company (along with a hundred or so other water companies in the area); that decree defines their distribution area.
The second is that this particular water company made their shares freely transferable, and that led to an unanticipated consequence. The way development of the area panned out, more people wanted water at the southern (downstream) end of their canal than on the upstream end. Because the shares were freely transferable, that led to a gradual shift in the share ownership toward the south. Eventually that got to the point where the capacity of the canal to deliver water was exceeded, and the only mechanism the water company had to control this was to start refusing to connect anyone with shares that originated upstream of the point where they wanted to draw water.
So...
For our sellers to get the water company's approval, they have to show two things. First, that the parcels are actually part of the decree area. That one is at least easy to attack – the sellers need to hire someone who can read the legal description of the decree area (gobbledygook to normal mortals) and figure out whether they are. Second, they have to show the provenance of the water rights are not from upstream. I'm not sure how they can do that, as it will require tracing the chain of share ownership. I believe (since water rights are real property in Utah) that all of this chain is recorded at the County office, so it might not be hard to do that.
On a completely different note, Debbie and I took a drive up the dirt road to Liberty last night. I was very sleepy (I'd gotten up particularly early yesterday morning), but nonetheless we saw some deer, about a million turkeys, a colony of muskrats, a kingfisher, and ... best of all ... a bald eagle. That eagle is almost certainly a migrator; this is the season they are flying south through our area. Hopefully we'll see more, but we got a great view of this fellow, just sitting up in a tree glaring at us. Or considering us for supper. Probably the latter :)
Thursday, November 19, 2015
Networking in Paradise...
Networking in Paradise... In response to a reader's question: the network cable tester I have is the Fluke MS2-100, pictured at right. It has a basic TDR (Time Domain Reflectometer) built in – no analog display, but it tells you the wire distance from the meter to any problem. It detects opens, shorts, and pairing. Having this thing in my toolkit has saved me hours of manual troubleshooting. Just on this job I've used it to tell me exactly where three separate wiring problems were, and to verify that the complete installation is working correctly. Highly recommended!
There's one other challenge to my networking here that I haven't mentioned before. The cable modem and main router for my house are located in Debbie's second floor office, and powered from the house electrical power. To get Internet in my shed, I've run CAT-6 all the way from that router out into the shed. The challenge is that the ground wires on that Ethernet cable are using the house's power ground – and the shed (including the network equipment out there) is on its own ground (because it has a completely separate AC main, including it's own transformer and meter).
If you've ever done any utility-side electrical work, you can anticipate my challenge: it's the classic “ground loop” problem. In my case, it's exacerbated by the fact that I have high current intermittent loads in the shed – things like a welder, 5 HP air compressor, etc. If I tried to connect the house Ethernet to the shed Ethernet, I'm sure to have large transient ground loop currents between them – and quite likely fry some equipment!
The classic solution for this sort of problem is electrical isolation (between the house and shed, in my case). I've never done this for Ethernet before (never needed to!), so I didn't know what was available. It turns out that medical equipment with network connections routinely deals with this, and there are parts readily available. I chose a Black Box SP426A “Ethernet Isolator”, pictured above left. This is an optoelectronic device that's powered from the Ethernet line, very conveniently for me. Mine should arrive tomorrow, and at that point I can actually install the router, switch, and wireless router in my shed...
There's one other challenge to my networking here that I haven't mentioned before. The cable modem and main router for my house are located in Debbie's second floor office, and powered from the house electrical power. To get Internet in my shed, I've run CAT-6 all the way from that router out into the shed. The challenge is that the ground wires on that Ethernet cable are using the house's power ground – and the shed (including the network equipment out there) is on its own ground (because it has a completely separate AC main, including it's own transformer and meter).
If you've ever done any utility-side electrical work, you can anticipate my challenge: it's the classic “ground loop” problem. In my case, it's exacerbated by the fact that I have high current intermittent loads in the shed – things like a welder, 5 HP air compressor, etc. If I tried to connect the house Ethernet to the shed Ethernet, I'm sure to have large transient ground loop currents between them – and quite likely fry some equipment!
The classic solution for this sort of problem is electrical isolation (between the house and shed, in my case). I've never done this for Ethernet before (never needed to!), so I didn't know what was available. It turns out that medical equipment with network connections routinely deals with this, and there are parts readily available. I chose a Black Box SP426A “Ethernet Isolator”, pictured above left. This is an optoelectronic device that's powered from the Ethernet line, very conveniently for me. Mine should arrive tomorrow, and at that point I can actually install the router, switch, and wireless router in my shed...
Paradise ponders...
Paradise ponders... Yesterday I spent a good part of the day in small and dark places :) Some of it was in the attic, crawling around to locate the top of the wall (in Debbie's office) through which I wanted to run the network cables. This was much more challenging than I had imagined it would be, for two reasons.
First, the wall in question isn't structural; it's just a dividing wall between two rooms. That matters because that means there's no corresponding structure in the attic – in fact, nothing visible in the attic at all to indicate where that wall might be. Precisely where it was actually matters a great deal, as I needed to drill a hole through the 2x4 at the top of that wall – and my target area for that hole was 3.5" wide by 8" long. That's not a very big target!
Second, the attic is completely filled with blown-in insulation, right to the tops of the 2x12 joists. That means that everything in the attic that might give me a visual cue (like wires, nails, etc.) is completely covered up with the insulation, rendering it invisible.
How could I find my drilling target? The only way I could think of is to measure from the one reference point I had that was visible both on the second floor and in the attic: the little hole that I crawled up to the attic in. That hole is about 12' east of the target wall, and about 2' south. So I did some very careful measuring on the second floor, then went up into the attic and duplicated it. That put me right between two joists (mounted north/south) and two big rectangular air ducts (going east/west). I dug through the insulation, marked an “X”, and drilled – then went down to the second floor to see if I'd drilled a hole through the ceiling. Nope! Apparently I actually hit the target! Yay!
At that point I cut a hole in the wallboard (photo above), “fished” the cable down toward the hole, and Debbie pulled it out. Victory!
But we still had one more challenge. One of the network cables was intended for a wireless router to be located in our kitchen. The wall there that I wanted to run the cable through was just barely accessible from our mechanical room in the basement. But, once again, I had no easy way to locate it. This was actually a tad more difficult than the attic location problem, as this time there wasn't a nice convenient common reference point. I ended up using the north and the east exterior walls as a reference. The east wall was nearly 20' away, in a different room both on the first floor and in the basement – but even so, it was the best reference I had. Once I located the place where I wanted the cable, I discovered that a huge steel air duct was blocking my access. Dang it! Then I had another idea: I could drill in from about a 45° angle, with a 20" long drill bit, and I could make it into the right area. That was a little scary making that hole – if I was off by even a couple inches, I'd be drilling into either a (very) visible area, or into a kitchen cabinet. Yikes! But I drilled away, and the hole came out within a quarter inch of where I intended it. Yay!
Shortly after that, I had everything wired up for the wireless router, and fired it up. Oops. It didn't work. Out came the cable tester, and I soon discovered that one wire was broken. The cable tester tells me where the problem is – and this time, it was in the female connector installed in the second floor wall (the photo above). On inspection I found a broken wire. All I needed to do was rewire it, and everything was working. And now we have 5 bars of WiFi throughout our house, including in our bedroom. Hooray!
Elray the well driller had a very successful day. His attempts to develop the water layer at 321' were successful. By the time he left yesterday afternoon he had almost completely cleaned out the area after having opened up the water bearing seams (with compressed air). The result: 30 GPM of clear water, no detectable odors, at 54°F. He's not going to be here today, but tomorrow he anticipates finishing the development work, pulling up the outer casing, and sealing the well. Then on Saturday or Monday he'll be pulling his rig out.
The next stage for us will be to put in a low-capacity pump, wire it up (to the shed), run a water line to the shed, and then put some infrastructure in the shed. I'm planning a 2,000 gallon cistern in there, with a float valve that controls the well pump. That can be filled at a low rate – probably under 5 GPM – which will help keep pump costs down. There will be a water softener and (if needed) iron removal system between the pump and the cistern. Then after the cistern there will be a booster pump and pressure tank. One potential variation on this scheme is to have a concrete cistern underground, outside the shed. I need to check into the feasibility of that. We have that setup for the spring that feed our house water, and it works well.
First, the wall in question isn't structural; it's just a dividing wall between two rooms. That matters because that means there's no corresponding structure in the attic – in fact, nothing visible in the attic at all to indicate where that wall might be. Precisely where it was actually matters a great deal, as I needed to drill a hole through the 2x4 at the top of that wall – and my target area for that hole was 3.5" wide by 8" long. That's not a very big target!
Second, the attic is completely filled with blown-in insulation, right to the tops of the 2x12 joists. That means that everything in the attic that might give me a visual cue (like wires, nails, etc.) is completely covered up with the insulation, rendering it invisible.
How could I find my drilling target? The only way I could think of is to measure from the one reference point I had that was visible both on the second floor and in the attic: the little hole that I crawled up to the attic in. That hole is about 12' east of the target wall, and about 2' south. So I did some very careful measuring on the second floor, then went up into the attic and duplicated it. That put me right between two joists (mounted north/south) and two big rectangular air ducts (going east/west). I dug through the insulation, marked an “X”, and drilled – then went down to the second floor to see if I'd drilled a hole through the ceiling. Nope! Apparently I actually hit the target! Yay!
At that point I cut a hole in the wallboard (photo above), “fished” the cable down toward the hole, and Debbie pulled it out. Victory!
But we still had one more challenge. One of the network cables was intended for a wireless router to be located in our kitchen. The wall there that I wanted to run the cable through was just barely accessible from our mechanical room in the basement. But, once again, I had no easy way to locate it. This was actually a tad more difficult than the attic location problem, as this time there wasn't a nice convenient common reference point. I ended up using the north and the east exterior walls as a reference. The east wall was nearly 20' away, in a different room both on the first floor and in the basement – but even so, it was the best reference I had. Once I located the place where I wanted the cable, I discovered that a huge steel air duct was blocking my access. Dang it! Then I had another idea: I could drill in from about a 45° angle, with a 20" long drill bit, and I could make it into the right area. That was a little scary making that hole – if I was off by even a couple inches, I'd be drilling into either a (very) visible area, or into a kitchen cabinet. Yikes! But I drilled away, and the hole came out within a quarter inch of where I intended it. Yay!
Shortly after that, I had everything wired up for the wireless router, and fired it up. Oops. It didn't work. Out came the cable tester, and I soon discovered that one wire was broken. The cable tester tells me where the problem is – and this time, it was in the female connector installed in the second floor wall (the photo above). On inspection I found a broken wire. All I needed to do was rewire it, and everything was working. And now we have 5 bars of WiFi throughout our house, including in our bedroom. Hooray!
Elray the well driller had a very successful day. His attempts to develop the water layer at 321' were successful. By the time he left yesterday afternoon he had almost completely cleaned out the area after having opened up the water bearing seams (with compressed air). The result: 30 GPM of clear water, no detectable odors, at 54°F. He's not going to be here today, but tomorrow he anticipates finishing the development work, pulling up the outer casing, and sealing the well. Then on Saturday or Monday he'll be pulling his rig out.
The next stage for us will be to put in a low-capacity pump, wire it up (to the shed), run a water line to the shed, and then put some infrastructure in the shed. I'm planning a 2,000 gallon cistern in there, with a float valve that controls the well pump. That can be filled at a low rate – probably under 5 GPM – which will help keep pump costs down. There will be a water softener and (if needed) iron removal system between the pump and the cistern. Then after the cistern there will be a booster pump and pressure tank. One potential variation on this scheme is to have a concrete cistern underground, outside the shed. I need to check into the feasibility of that. We have that setup for the spring that feed our house water, and it works well.
Wednesday, November 18, 2015
Paradise ponders...
Paradise ponders... This morning I built the seconds counter on my clock kit (photo of that section at right). It all worked on the first try. When I put my 'scope on the output of the 2^3 flip-flop, I saw a “0” for 8 seconds and a “1” for 2 seconds, repeating in that 10 second cycle. That's exactly what I should see there, because that flip-flop is only set when the seconds counter contains an 8 or a 9 – which it does for 2 seconds out of every 10. The other three flip-flops in the counter also had the expected patterns. My next assembly effort will be the seven-segment decoder logic, the seven-segment LED driver, and the LED itself. When I get that done, I'll see the seconds for the clock counting up!
Yesterday I started installing some network cables in the house. The first step was to run two CAT-6 cables from the basement “mechanical room” up into the attic. I ran them alongside the chimney, where there's already quite an assortment of pipes and wires running. Today I'm hoping to run them from the attic down through a wall in our second floor office, where I'll terminate them in a wall panel. One of those wires I'll be connecting to the underground CAT-6 that runs out to the barn; the other I'll be running up through a wall in the kitchen, to attach to a second wireless router for the house. Our WiFi on the first floor (especially in our bedroom) is kind of shaky, so we're hoping this will fix it.
We took Debbie in for her first treatment with a transdermal steroid patch. This is designed to attack her patella tendinitis. The patch contains a battery that uses an electric field to drive the drug down through her skin into the tendon. The physical therapist there noted that Debbie's extension in her injured leg isn't quite as good as in the uninjured leg, and he's pretty sure that's the root cause of her tendinitis. We got a bunch of exercises for her to do, all with the objective of improving that extension. She's hard at work on them already :)
Yesterday I started installing some network cables in the house. The first step was to run two CAT-6 cables from the basement “mechanical room” up into the attic. I ran them alongside the chimney, where there's already quite an assortment of pipes and wires running. Today I'm hoping to run them from the attic down through a wall in our second floor office, where I'll terminate them in a wall panel. One of those wires I'll be connecting to the underground CAT-6 that runs out to the barn; the other I'll be running up through a wall in the kitchen, to attach to a second wireless router for the house. Our WiFi on the first floor (especially in our bedroom) is kind of shaky, so we're hoping this will fix it.
We took Debbie in for her first treatment with a transdermal steroid patch. This is designed to attack her patella tendinitis. The patch contains a battery that uses an electric field to drive the drug down through her skin into the tendon. The physical therapist there noted that Debbie's extension in her injured leg isn't quite as good as in the uninjured leg, and he's pretty sure that's the root cause of her tendinitis. We got a bunch of exercises for her to do, all with the objective of improving that extension. She's hard at work on them already :)
Suppose I told you...
Suppose I told you ... that there was a group of armed people in the U.S. who have (so far) killed over 1,000 people this year. Would that alarm you?
It certainly alarms me!
Well, there really is such a group – the cops.
It's remarkable how little press this phenomenon – a recent one – gets...
It certainly alarms me!
Well, there really is such a group – the cops.
It's remarkable how little press this phenomenon – a recent one – gets...
Charts in presentations...
Charts in presentations... This morning's Dilbert cartoon (below) triggered a memory of a conversation I once had with my company's CEO. I was, at the time, the Chief Technology Officer. I had been tasked with making a presentation to the Board about our software development process. In my presentation, I had a chart that showed the number of unresolved bugs in our main product declining over time. If you're a software company, a steadily declining number of unresolved (“open”) bugs is a really good thing. The CEO – my boss – was very unhappy with that chart. Why? Because the trend was down, and that (to him) by definition was negative. So he had me change out the chart for one that showed the resolved (“closed”) bug count, which of course went steadily up. My protestations that the closed bug count was the wrong measure fell upon deaf ears. I couldn't even get him to let me use the inverse of unresolved bugs (which would make the trend upwards), as he said that would be too hard to explain to the Board.
The result?
When I gave my presentation, two Board members reacted as my CEO hoped – they saw the upward trend and assumed life was good. The rest of the board – four or five members – all jumped on me for having a stupid metric in my presentation, and they proceeded to lecture me about the importance of tracking unresolved bugs.
I'm so glad to be retired! :)
The result?
When I gave my presentation, two Board members reacted as my CEO hoped – they saw the upward trend and assumed life was good. The rest of the board – four or five members – all jumped on me for having a stupid metric in my presentation, and they proceeded to lecture me about the importance of tracking unresolved bugs.
I'm so glad to be retired! :)
Tuesday, November 17, 2015
Paradise postcards...
Paradise postcards... Just a couple of scenes from our yard this morning. The first was taken looking west just before sunrise; the Wellsville Mountains were lit up, but the valley floor was not (and that's our shed on the left). The second was taken from the same spot, looking east. That's my friend Tim's alfalfa field, with his two horses very contentedly munching away on the 4 to 6 inches that's grown since the last mowing of the season. They sometimes hang over our fence (on the right) and look longingly into our kitchen :)
Electronics and wildlife!
Electronics and wildlife! Down under transplant, reader, friend, and former colleague Simon M. noted that the latest xkcd cartoon combines two of my favorite things: wildlife and electronics! When I saw the cartoon yesterday, I just smiled – it didn't occur to me that a lot of people wouldn't get it.
Red and yellow are two of the ten standard colors used for coding the value of components (especially resistors). It's a very old system, predating me considerably, and it's used worldwide. I've been familiar with it since the early 1960s, so it's second nature to me. Red is the code for 2, and yellow for 4, hence the reference to “24” in the cartoon. The omega (Ω) is the symbol for ohms, the unit of electrical resistance.
The “red touches yellow” is part of a rhyme for telling a coral snake apart from a king snake. This is important where both snakes coexist (like in Florida), as the coral snake is venomous, and the king snake is not. The complete rhyme:
Red and yellow are two of the ten standard colors used for coding the value of components (especially resistors). It's a very old system, predating me considerably, and it's used worldwide. I've been familiar with it since the early 1960s, so it's second nature to me. Red is the code for 2, and yellow for 4, hence the reference to “24” in the cartoon. The omega (Ω) is the symbol for ohms, the unit of electrical resistance.
The “red touches yellow” is part of a rhyme for telling a coral snake apart from a king snake. This is important where both snakes coexist (like in Florida), as the coral snake is venomous, and the king snake is not. The complete rhyme:
Red Touch Yellow - Kills a Fellow
Red Touch Black - Venom Lack
Yellow Touches Red - Soon You'll Be Dead
Red Touches Black - Friend of Jack
Monday, November 16, 2015
Paradise ponders...
Paradise ponders... Another busy day today! First we went to see Debbie's doctor. She's been having some pain in her knee, making it painful to walk – and to make progress in her recovery. Tendinitis in the patella tendon was the diagnosis, and she's going to start treatment for that tomorrow. The treatment is a steroid-infused patch for her knee, with a battery that drives the steroid from her skin into the tendon. Amazing medical technology these days! We're hoping for a fast cure for this latest challenge.
When we finished with the doctor's appointment, we headed out to the cabin we're buying near Newton. Today was the final walkthrough; our last chance to voice objections before we formally take possession. We were very pleasantly surprised – the sellers did a bang-up job cleaning up the mess that we saw on our last visit. We found absolutely nothing to worry about.
The next step after that happened later this afternoon: the formal “closing”. We've done this several times in California, and I did it once in Utah (for our Paradise home). Debbie had never before seen the difference between closing in California versus closing in Utah. The short version: California took a couple hours and something like 100 signatures. Utah took 7 minutes and 3 signatures. Done! Before we went into the title company office to do the closing (they do it here, not escrow companies as in California), I wired the money to their trust account. Three signatures and a handshake, and now we're the owners. So easy here, and so straightforward. The recording will happen either this afternoon or early tomorrow morning. After that, the process is completely done!
After we got home from the closing, I went out to talk with Elray the well driller. He worked away as we talked, and he told me he was hoping to get through a clay layer and into water-bearing sandstone shortly. A few minutes later, he did – and by the purest luck, I was there to see it. I stayed out with him for about an hour as he went through the process of deepening the hole into the sandstone, and backing out the drill by 25' or so to “proof” the well (testing to see if good, clear water was coming up). He's going to be proofing the rest of the day today, and part of tomorrow, but as of now it looks like we have good water – at 321'. If things still look good tomorrow, he's going to weld about 4 more feet of casing on top and pound it down so that the bottom of the casing is resting on top of the water-bearing sandstone. This will keep the water as clean as possible by keeping it out of the clay layer above the sandstone. All good!
When we finished with the doctor's appointment, we headed out to the cabin we're buying near Newton. Today was the final walkthrough; our last chance to voice objections before we formally take possession. We were very pleasantly surprised – the sellers did a bang-up job cleaning up the mess that we saw on our last visit. We found absolutely nothing to worry about.
The next step after that happened later this afternoon: the formal “closing”. We've done this several times in California, and I did it once in Utah (for our Paradise home). Debbie had never before seen the difference between closing in California versus closing in Utah. The short version: California took a couple hours and something like 100 signatures. Utah took 7 minutes and 3 signatures. Done! Before we went into the title company office to do the closing (they do it here, not escrow companies as in California), I wired the money to their trust account. Three signatures and a handshake, and now we're the owners. So easy here, and so straightforward. The recording will happen either this afternoon or early tomorrow morning. After that, the process is completely done!
After we got home from the closing, I went out to talk with Elray the well driller. He worked away as we talked, and he told me he was hoping to get through a clay layer and into water-bearing sandstone shortly. A few minutes later, he did – and by the purest luck, I was there to see it. I stayed out with him for about an hour as he went through the process of deepening the hole into the sandstone, and backing out the drill by 25' or so to “proof” the well (testing to see if good, clear water was coming up). He's going to be proofing the rest of the day today, and part of tomorrow, but as of now it looks like we have good water – at 321'. If things still look good tomorrow, he's going to weld about 4 more feet of casing on top and pound it down so that the bottom of the casing is resting on top of the water-bearing sandstone. This will keep the water as clean as possible by keeping it out of the clay layer above the sandstone. All good!
Paradise problem puzzled!
Paradise problem puzzled! Yesterday I posted about the clock kit I was building, and how the prescaler had a problem that needed to be troubleshot. Well, this morning I found the problem: a bad trace on the printed circuit board. I soldered in a jumper, about a quarter inch long, and presto! The prescaler is now working perfectly, giving me a beautiful 1 Hz (one pulse per second) signal. That 1 Hz signal will drive the seconds counter, which is the next part I'll be assembling.
I was surprised that it turned out to be a circuit board problem. There must have been a tiny break in the trace, but I couldn't see it under the solder mask. I found two components whose leads were very close together, that were supposed to be connected (but weren't), so the break had to be somewhere in the quarter inch or so between them. That little jumper did the trick nicely. Troubleshooting it was actually fairly easy: one component was a resistor that showed a signal on the end that was supposed to be connected to the base of a transistor. That base showed no signal at all. Straight wires (or circuit board traces) aren't supposed to behave like that :) Once I observed that anomaly, finding the actual cause was easy...
I was surprised that it turned out to be a circuit board problem. There must have been a tiny break in the trace, but I couldn't see it under the solder mask. I found two components whose leads were very close together, that were supposed to be connected (but weren't), so the break had to be somewhere in the quarter inch or so between them. That little jumper did the trick nicely. Troubleshooting it was actually fairly easy: one component was a resistor that showed a signal on the end that was supposed to be connected to the base of a transistor. That base showed no signal at all. Straight wires (or circuit board traces) aren't supposed to behave like that :) Once I observed that anomaly, finding the actual cause was easy...
Subscribe to:
Posts (Atom)







