Ramble / Poll: The State of Rip It Apart; Domains & Monetization?

2016 has flown by with considerable speed as of late – it’s already near the end of March the beginning of April, and I haven’t published a single blog post…

“So, what’s up with you?”

I will admit it – much of the radio silence on my blog stems from my own complacency. My desk/work area had accumulated vast amounts of detritus, many of them being half-done projects that never reached completion and years of deprecated audio equipment that wasted a good 1/3 of my entire desktop area – not to mention plenty of dust. All of this resulted in a workspace that made typing for any extended period of time quite uncomfortable; even attempting to play computer games had the risk of me breaking something, or vice versa.

This school year has been going pretty well. I’ve left Electronics Engineering and have started Broadcast Systems Technology; it’s essentially a mix of basic electronics, IT, radio and audio/video equipment. With that sort of fresh start (and extra credits that allowed me to free up considerable amounts of time), I’ve begun to clean up my area – a process that started in January and only recently has progressed to a point where I could “re-format” my desk space to maximize its usability.

Now that I’ve finally cleaned up my workspace, I can finally type in comfort again. I have several draft posts in various stages of completion, and I want to be able to get them finished up and published sometime soon (of course, no hard deadlines are set as I likely wouldn’t meet them anyway).

Domains & Advertisement Monetization

Over the years that I’ve been running this blog, my viewership has increased to levels I would have never anticipated when I first started writing blog posts on here, and I’d like to thank all of my readers for that.

As of late, I’ve averaged around 10,000 views per month, with significant peaks now and then. Because I’m currently running on the WordPress with a non-Premium account, most of my pages have advertisements in them that I have no control over. I can pay a hefty fee to go Premium and remove the advertisements completely, but I would like to at least to be able to get something out of those advertisements.

After looking online about WordAds, I’ve found out that I would need to register a proper domain name for this blog, which makes total sense – why bother putting branding on a .wordpress.com subdomain? Because of this requirement, I need to register my own domain… but what should I choose?

The whole issue of picking a domain for registration was one reason that I’ve been putting it off for so long. I could go with a domain with my name on it (literally!) in a similar vein as Gough Lui’s blog (disclaimer: I have absolutely no affiliation with him; I’m simply using his domain as an example… but on that note, his content is definitely worth checking out!), or perhaps simply remove the .wordpress portion of my blog’s URL.

With that decision in mind, then comes the choice of whom to register with. WordPress has their own service that ties seamlessly with their blogging platform, but incurs a higher cost than other providers. Alternatively, I can choose a lower-cost provider, but then I would need to manually connect that domain with WordPress’ platform. Admittedly, I have little experience when it comes to Web hosting; it’s why I started my blog on WordPress in the first place, and also one of the largest factors in my reluctance to register a domain for it in the first place.

Voice Your Opinion

Either way, domain registration and advertisement controls are decisions that can be put aside until later. On that note, if I were to register a domain, what do you think would be a good choice? Leave your choice in the poll below!


Pick a Card, Any Card: Fast and easy Windows logon using any NFC smart card

After finally reinstalling Windows on my main PC (the smart card components in the old install were trashed), I dusted off the old smart card reader and started looking into smart card-based logon options again.

Windows logon screen using a smart card

Windows logon screen using a smart card

After finding a way to force convince the installer for EIDAuthenticate, a program that lets you use smart cards to log on a Windows computer without the use of domains and Active Directory, to run on Windows 7 Professional (Microsoft DreamSpark only lets me obtain the Professional editions of Windows), I found a program called NFC Connector Light that lets you use any NFC-compatible smart card as a means of authentication.

Virtual smart card with certificate installed

Virtual smart card with certificate installed

NFC Connector Light links the unique identifier in an NFC-based smart card to create a virtual smart card on the local computer (no data is stored in the card itself), and that virtual card can be used like a real smart card within Windows. When paired with EIDAuthenticate, logging on is as simple as placing the smart card on the NFC reader and entering a PIN. This is especially useful when you set the Windows smart card policy to lock the computer when the card is removed (and it feels kind of cool to be able to lock your computer simply by taking your card off the reader).

HDQ Utility version 0.96 now available!

Whew, I’ve been working on this version for quite a while. With the helpful feedback of many people that have tried my software, I’ve made a large number of improvements to the software; of course, there are plenty of features that aren’t implemented yet, but are being worked on.

More information about how this utility works can be found here.

Download HDQ Utility v0.96 here: https://www.dropbox.com/s/pf0vszgfei7s8ly/HDQ%20Utility%200.96.zip?dl=0


  • (Major improvement!) Improved HDQ logging functionality (logs are now saved to a separate file instead of being overwritten).
    • Example: “HDQ Log (2015-10-26 at 19.02.50) – HDQ Utility v0.96.txt”
  • Improved HDQ communication (HDQ breaks no longer require the serial port to be opened more than once, and HDQ no-response timeouts are decreased from 0.5 to 0.3 seconds.
  • Reworded certain error messages for clarity.
    • Example: “Communication error: Cannot read byte from address 0x02 (No response from device).” 
  • Renamed file ‘config.txt’ to ‘Config – COM Port.txt’ for clarity.
  • Improved state-of-health warnings by making them non-modal (they do not require the user to dismiss the message).
  • Added more notifications for unidentified and uninitialized batteries. (Uninitialized batteries are determined by a FULL ACCESS security state, with Impedance Track disabled.)
  • Fixed invalid device name and maximum load current readings for v5.02/sn27545-A4 based batteries (e.g. iPhone 6, 6+…).
  • Added time-to-full readings (for firmware older than v2.24).
  • Improved error-checking for device identification (it will display a notice that the tool may need to be restarted).
  • Updated DingoLib UI library to auto-resize window to 0.9x display resolution for improved readability on larger monitors.


  • Create a dedicated section on my blog for the HDQ Utility.
  • Create a user’s manual describing the parameters displayed by the program (in particular, the Advanced Battery Information section).
  • Improve data logging functionality by saving logs to a subdirectory instead of the program’s root to decrease file clutter.
  • Improve error-checking for commands (retry reads if one or more bytes are not received from the device).
  • Add error statistics indicating how many communication errors occurred during data collection.
  • Improve support for older (older than v1.25) firmware.
  • Improve support for v5.02/sn27545-A4 devices (make use of advanced commands available in this firmware version).
  • Add support for restarting of data collection without having to re-execute the program.
  • Add Data Flash memory functions to allow for readout of advanced configuration, serial number, lifetime/black-box data, etc.
  • Rewrite this program in something that’s not LabWindows/CVI… also, use of a GUI rather than a non-console text UI.

Self-discharge test of Kentli PH5 1.5V Li-ion AA (Part 3)

Aw what, it’s October already? So much for having another blog post in September…
But anyway, “more months, more data!™”

The voltage of the PH5 has dropped down to 4.093 volts as of today (October 1st, 2015), and its State of Charge is now 93%. There’s just enough data to guess the discharge rate of the PH5: with the currently logged data, the PH5 self discharges at approximately 0.103%/day. At this rate, the cell should last years before finally reaching zero. Looks like this will be a very, very long term test…

(At least that would give me more time to procrastinate write blog posts.)

Self-discharge test of Kentli PH5 1.5V Li-ion AA (Part 2)

After my first self-discharge analysis of the Kentli PH5 Li-ion AA battery, I have collected another month’s worth of data.

The battery’s voltage drop has been surprisingly linear. Although I didn’t get the exact day when the bq27621-G1’s State of Charge readout dropped to 99%, it is quite clear that the state of charge is dropping with a fairly steep curve now. That said, because the battery’s voltage is still far away from the ‘flat region’ of the discharge curve, it is difficult to determine when the battery will discharge itself completely at this time.

Self-discharge test of Kentli PH5 1.5V Li-ion AA (Part 1)

As an extension to my previous performance analysis of Kentli’s PH5 Li-ion AA battery, I fully charged an unused PH5 and left it on my desk to self-discharge. Every now and then, a Texas Instruments bq27621-G1 fuel gauge is hooked up to the Li-ion battery terminals (in the case of the PH5, the recessed ring around the 1.5V terminal) and the bq27621’s default settings are used to measure the voltage and state of charge.

I started this test on June 18th, 2015 and will keep taking occasional measurements until the protection IC in the PH5 shuts down.

Since the 18th, the voltage dropped from 4.216 volts down to 4.192 volts as of July 6, 2015; the bq27621’s State of Charge reading remains at 100% for the time being. The voltage drop has been fairly linear so far, but I expect it to taper off as the battery discharges to the Li-ion cell’s “flat region”, and only after that do I expect the cell’s voltage to decline more rapidly.