danplanet.comdanplanetcom - Right Angles If theyre not rightthey
danplanet.com Profile
danplanet.com
Sub Domains:comm-trac.danplanet.com trac.chirp.danplanet.com chirp.danplanet.com intrepid.danplanet.com
Title:danplanetcom - Right Angles If theyre not rightthey
Description:I recently got a good deal on a condition-unknown Kenwood TK-7160H radio This is a nice 50W VHF high-band commercial transceiver and I figured that even if it was a little sick it could probably be used to add support to CHIRPOnce I had a chance to check it out I discovered that it was almost entirely deaf but only when it was in wide 5kHz deviation mode
Discover danplanet.com website stats, rating, details and status online.Use our online tools to find owner and admin contact info. Find out where is server located.Read and write reviews or vote to improve it ranking. Check alliedvsaxis duplicates with related css, domain relations, most used words, social networks references. Go to regular site
danplanet.com Information
Website / Domain: |
danplanet.com |
HomePage size: | 189.305 KB |
Page Load Time: | 0.501901 Seconds |
Website IP Address: |
50.116.5.251 |
Isp Server: |
Linode |
danplanet.com Ip Information
Ip Country: |
United States |
City Name: |
Fremont |
Latitude: |
37.548271179199 |
Longitude: |
-121.98857116699 |
danplanet.com Keywords accounting
danplanet.com Httpheader
Date: Tue, 12 May 2020 09:46:06 GMT |
Server: Apache/2.2.22 (Ubuntu) |
X-Powered-By: PHP/5.3.10-1ubuntu3.26 |
Link: http://www.danplanet.com/blog/wp-json/; rel="https://api.w.org/" |
Vary: Accept-Encoding |
Content-Encoding: gzip |
Content-Length: 41789 |
Connection: close |
Content-Type: text/html; charset=UTF-8 |
danplanet.com Meta Info
charset="utf-8"/ |
content="WordPress 5.1.1" name="generator"/ |
50.116.5.251 Domains
danplanet.com Similar Website
Domain |
WebSite Title |
danplanet.com | danplanetcom - Right Angles If theyre not rightthey |
intrepid.danplanet.com | danplanetcom - Right Angles If theyre not rightthey |
crustcafeandpizzeria.com | "We Tossem Theyre Awesome" - Crust Cafe and Pizzeria |
danplanet.com Traffic Sources Chart
danplanet.com Alexa Rank History Chart
danplanet.com Html To Plain Text
-- Right Angles If they're not right...they're wrong Skip to content Home February 14, 2020 15:50 by: Dan 2 comment(s) comments RSS trackback permalink Fixing bad filters in a Kenwood TK-7160H I recently got a good deal on a condition-unknown Kenwood TK-7160H radio. This is a nice 50W VHF high-band commercial transceiver, and I figured that even if it was a little sick, it could probably be used to add support to CHIRP . Once I had a chance to check it out, I discovered that it was almost entirely deaf — but only when it was in wide (5kHz deviation) mode. In narrow (2.5kHz deviation) mode, it was fine. Everything else about the thing was on point. I cracked the case and followed the service manual’s description of the signal path to the IF filters. They’re on the bottom side of the board as installed in the chassis, which means it’s hard to examine them directly, but their terminals are sticking up, ripe for the probing. Sure enough, I could scope the IF signal on either side of the narrow filter, but one side of the wide filter it was clamped hard to ground. If you are looking at the radio top-down, the wide filter is the one closest to the edge of the board: The filters each have five pins: three closely-spaced on one side which are ground, and then two on the other side far apart. The two two far-apart ones are the filter input/output pins. I also noticed that there was some buildup on the otherwise-clean board right around the filters. This looked like crispy flux residue, but also could have been some sort of corrosion. If it was flux, it seemed likely that someone had already been in here to replace filters, potentially only the narrow one since it was healthy? It is well-known that some radios have issues with their ceramic IF filters. Notably, Kenwood had a rash of much-too-early failures on some of the TM-D710 and TM-V71 radios which had some people worried about long-term longevity. It has been theorized that this problem is due to electromigration due to improper buffering of the filters from the DC bias used in the narrow/wide filter selection logic. Many radio manufacturers do this across many of their models and widespread deaths of all those don’t seem common enough for this to be some major oversight by the world’s leading radio manufacturers, at least in my opinion. Other theories are that Kenwood specifically got a bad batch of Toko filters within a certain manufacturing window, and these are the ones that are dying early. Other pictures and video I have seen of this problem revealed the affected filters showing external signs of “green death” leaking out of the filter enclosure, slowly working its way out due to increased pressure. To get a look at the filters themselves I had to remove the board, which required unsoldering the antenna connector at the back: Once that was free, the rest of the screws will release the board from the chassis. I flipped it over and immediately noticed a few things. First, the filters were different brands, indicating that likely one had been swapped out and not the other. Second, the wide one was Toko brand. Third, the wide filter was covered in white fuzz, similar to other pictures I had seen of this problem, but not the narrow one. Since this radio is intended for Part 90 use, it is likely that someone would have repaired/replaced just the narrow filter, as wide mode would really only be useful to a ham these days. Filters are cheap, about $5 each, and they’re fairly common across these sorts of radios. I ordered three of each and figured I’d swap out the narrow filter in this guy too, since I was in there, just in case. I opted not to do the bypass cap hack job to remove the DC bias. Kenwood’s part numbers for the filters are in the service manual: Wide: L72-0993-05 Narrow: L72-0999-05 Here’s the wide filter desoldered, and the narrow one came out right after it: After the board was cleaned up, both new filters went back into their spots: The hot elements are heat sinked to the chassis underneath and mated with thermal paste. I added a little more to each landing before I reassembled it to make sure nothing was thermally compromised by the dis- and re-assembly. Don’t forget to re-solder the antenna connection to the board once it is screwed back down. After it was all back together, I checked on the service monitor and sure enough, the wide mode was working properly again. Sensitive down well below -120dBm. Before the fix, at 0dBm, I could only barely hear the modulation through the static when I held the squelch open. There isn’t a lot of information out there (at least that I could find) about applying these filter fixes to the commercial line of radios. Most of those probably get fixed in a shop, where radios from the amateur line are more likely to get fixed by the owner. The same theory here should apply for the UHF variant (TK-7180) as well as similar models of TK-7162, TK-8162, TK-7102, TK-7108, TK-8102, TK-8108, TK-7180, and TK-8180. Posted in Radio Tagged amateur radio , ceramic , commercial , filter , fix , kenwood , radio , tk-7160 , tk-7180 , tk-8160 , tk-8180 November 4, 2019 11:30 by: Dan trackback permalink Start and Monitor Image Pre-cache Operations in Nova When you boot an instance in Nova, you provide a reference to an image. In many cases, once Nova has selected a host, the virt driver on that node downloads the image from Glance and uses it as the basis for the root disk of your instance. If your nodes are using a virt driver that supports image caching , then that image only needs to be downloaded once per node, which means the first instance to use that image causes it to be downloaded (and thus has to wait). Subsequent instances based on that image will boot much faster as the image is already resident. If you manage an application that involves booting a lot of instances from the same image, you know that the time-to-boot for those instances could be vastly reduced if the image is already resident on the compute nodes you will land on. If you are trying to avoid the latency of rolling out a new image, this becomes a critical calculation. For years , people have asked for or proposed solutions in Nova for allowing some sort of image pre-caching to solve this, but those discussions have always become stalled in detail hell. Some people have resorted to hacks like booting host-targeted tiny instances ahead of time, direct injection of image files to Nova’s cache directory, or local code modifications. Starting in the Ussuri release, such hacks will no longer be necessary. Image pre-caching in Ussuri Nova’s now-merged image caching feature includes a very lightweight and no-promises way to request that an image be cached on a group of hosts (defined by a host aggregate). In order to avoid some of the roadblocks to success that have plagued previous attempts, the new API does not attempt to provide a rich status result, nor a way to poll for or check on the status of a caching operation. There is also no scheduling, persistence, or reporting of which images are cached where. Asking Nova to cache one or more images on a group of hosts is similar to asking those hosts to boot an instance there, but without the overhead that goes along with it. That means that images cached as part of such a request will be subject to the same expiry timer as any other. If you want them to remain resident on the nodes permanently, you must re-request the images before the expiry timer would have purged them. Each time an image is pre-cached on a host, the timestamp for purge is updated if the image is already resident. Obviously for a large cloud, status and monitoring of the cache process in some way is required, especially if you are waiting for it to complete before starting a rollout. The subject of this post is to demonstrate how this can be done with notifications . Example setup Before we can talk about how to kick off and monitor a caching operation, we need to set up the basic elements o...
danplanet.com Whois
"domain_name": "DANPLANET.COM",
"registrar": "Domain.com, LLC",
"whois_server": "whois.domain.com",
"referral_url": null,
"updated_date": [
"2018-09-24 17:30:34",
"2018-09-24T17:30:34"
],
"creation_date": [
"2002-10-20 00:41:36",
"2002-10-20T00:41:36"
],
"expiration_date": [
"2023-10-20 00:41:36",
"2023-10-20T00:41:36"
],
"name_servers": [
"NS1.LINODE.COM",
"NS2.LINODE.COM",
"NS3.DANPLANET.COM",
"NS3.LINODE.COM",
"NS4.DANPLANET.COM",
"NS4.LINODE.COM",
"ns1.linode.com",
"ns2.linode.com",
"ns3.linode.com",
"ns4.linode.com",
"ns3.danplanet.com",
"ns4.danplanet.com"
],
"status": [
"clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited",
"clientTransferProhibited https://icann.org/epp#clientTransferProhibited",
"clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited"
],
"emails": [
"compliance@domain-inc.net",
"support@dotster-inc.com"
],
"dnssec": "unsigned",
"name": "REDACTED FOR PRIVACY",
"org": "REDACTED FOR PRIVACY",
"address": "REDACTED FOR PRIVACY",
"city": "REDACTED FOR PRIVACY",
"state": "OR",
"zipcode": "REDACTED FOR PRIVACY",
"country": "US"