The XHDATA D-808 resting on the workbench, prepped to capture weak cross-border DX signals out of the evening static. |
Friday, 6 November 2026
D-808 Mediumwave Chronicles: Unmasking the Cold War on my Nightstand
Friday, 30 October 2026
XHDATA D-808 Anatomy: A Frustrated Ham’s Micro-Repair Journal & Engineering Review
![]() |
| The XHDATA D-808 Portable World Receiver on the workbench before disassembly. |
![]() |
| The uncovered control panel circuit board with the main tuning encoder and the fine-tune potentiometer buried under the factory roof-top guard. |
![]() |
| The exposed vertical thumbwheel area after carefully shaving the melted plastic factory rivet to swing the protective roof-top guard out of the way. |
Because the plastic stem had broken completely flat, the thumbwheel had nothing left to grip. I spent hours trying to execute a micro-dowel pin repair. I tried using a microscopic strand of single-core copper wire salvaged from a LAN cable, but the metal was too soft and the piece kept vanishing on my desk. I eventually used a pair of fine forceps to implant the blunt end of a micro-length hand-stitching needle straight into the centre of the plastic wheel to act as a steel axle.
![]() |
| The flat plastic fine-tune thumbwheel wheel showing the grey fracture scar where it sheared flush from the potentiometer stem. |
![]() |
| The custom-implanted steel needle stub embedded precisely into the centre of the thumbwheel to serve as a reinforced mounting pin. |
![]() |
| A high-magnification macro view of the main driving digital signal processor chip responsible for the radio's RF tracking. |
I sent a formal, detailed email to the XHDATA help desk a week ago, outlining my direct purchase history and requesting a replacement control sub-board or potentiometer component. I will update this blog post with their official response the exact moment it drops into my inbox. Stay tuned for the update.
Thursday, 15 October 2026
Wires and Barricades: Day Capital Ditched Mainstream Narratives
![]() |
| Independent voices on the ground: A composite tracking the digital news portals anchoring the capital's reporting network. Left, Nidhi Razdan conducting live broadcasts for DeKorder, center, legendary editor Dr Prannoy Roy explaining the voter data deletions, and right, Sreenivasan Jain of Newslaundry confronting enforcement perimeters during the anti-CEC protest in New Delhi on Monday, October 12. |
![]() |
| Mainstream evasion and public rejection: Screenshots from on-the-scene footage documented by digital observers during the anti-CEC demonstrations. Left, independent creator Memeghnad confronts a Republic TV camera team for evading field footage of police excesses, and right, a young NDTV field crew faces spontaneous public heckling by citizens chanting "Godi Media" in New Delhi. |
In sharp contrast to this high-quality independent coverage, the state apparatus has implemented severe containment tactics. A detailed ground investigation by Decode Internet documented a sweeping crackdown systematically targeting the young journalists, YouTubers, and independent scribes responsible for capturing street realities. Over 37 journalists were detained over a two-day window. The Caravan's Ryan Thomas was dragged onto a transit vehicle and hit repeatedly on the head by police for refusing to delete raw documentary footage. This institutional heavy-handedness has swept up completely innocent bystanders. In one verified video, a helpless man who had travelled to Delhi to arrange urgent clinical treatment for his nephew suffering from double kidney failure was aggressively shoved into a police bus. Despite the frantic man showing officers his hospital prescriptions, his documentation was completely ignored. The Delhi Police have dismissed allegations of selective enforcement, stating that security measures are strictly legal actions taken to maintain public order and safety.
![]() |
Sunday, 11 October 2026
Siege of New Delhi: How an Automated Voting Glitch Triggered an Unofficial Emergency
![]() |
| Ground-level realities from the capital: Screenshots from video reports published on X by BOOM Live (left), showing heavy security deployment at Jantar Mantar, and The Hindu (right), showing student and youth activists marching from Gurudwara Bangla Sahib during the anti-CEC protest in New Delhi on Saturday, October 10 |
![]() |
Clashes on the streets: Screenshots from video footage published on X by The Quint, documenting a group of individuals attacking peaceful demonstrators in the Connaught Place area of New Delhi on Saturday, October 10. The ground footage highlights the breakdown of order as scuffles broke out in full public view. |
The strategy of total containment may keep the streets clear temporarily, but it deepens the trust deficit between citizens and the state. When administrative machinery is used entirely to insulate an individual from accountability, it signals structural weakness rather than strength. The aggressive lockdown of Delhi has not silenced the questions surrounding the electoral process. Instead, it has put those questions on the global stage.
Saturday, 19 September 2026
Surrender at Sector 16: Exposing PVVNL Billing Fraud, Falsified ATRs, and Remote Disconnection Tactics
Ghost in Smart Meter.
![]() |
| The master evidence dossier containing handwritten grievance logs, formal representation letters, and historical billing records used to dismantle PVVNL's billing fraud |
On 28 March 2026, I returned to Vasundhara from Bengaluru after performing the last rites for my late brother. When I opened my flat, I found that the power had been cut off remotely without any warning. No legal notice had been served. My formal emails sent to UPPCL authorities throughout January, February, and March had been completely ignored. I walked into the Sector 16 Bijli Ghar in extreme personal grief, carrying two years of hardcopy bills proving my winter baseline consumption was consistently between 460 and 480 rupees during periods of non-occupancy. Assistant Engineer Vibor Sharma refused to examine the records. He dismissed my documents and declared that I had to first pay a disputed 16,000-rupee bill and deposit additional funds for a Check Meter before anyone in the department would investigate.
What followed was an intense campaign of psychological pressure delivered via short message service text alerts. The 1912 Customer Relationship Management (CRM) framework became a defensive shield for dereliction of duty. Local staff used canned responses to close grievance tickets without performing any site inspections. Meanwhile, the system bombarded my phone with automated alerts threatening immediate disconnection for a demand exceeding 20,000 rupees. Forty-eight hours later, without any meter reading, physical audit, or explanation, another message dropped the demand to 17,000 rupees. The numbers were entirely inconsistent, designed to pressure the consumer into paying. Unidentified individuals claiming to represent UPPCL began calling my private mobile number, using hostile language to demand immediate settlement.
The Check Meter process was just as dishonest. Department linemen requested a thick 6mm copper wire to install the unit. I lent them a 20-metre coil of premium wire that I had borrowed. During the installation, field staff solicited informal payments and actively avoided being photographed. Fifty days later, they secretly took the Check Meter down and stole my borrowed copper wire.
They claimed that the smart meter architecture provides automated head-end system data that is tamper-proof and synchronized with the central server, arguing that historical gaps in documentation do not invalidate cumulative automated readings. But automated data is legally invalid if the physical baseline is flawed. Under Clause 5.6 of the Uttar Pradesh Electricity Supply Code 2005, the licensee is legally bound to ensure initial meter readings are verified, recorded, and signed by the consumer on the Sealing Certificate at the time of installation. Manually backfilling blank official records months later at the Sector 11 lab violates statutory protocol.
The department then argued that my failure to clear the raised assessment within the billing cycle justified automatic remote disconnection to prevent revenue loss. Yet Section 56(1) of the Electricity Act 2003 strictly mandates a minimum 15-day clear written notice before any disconnection. Furthermore, Clause 6.5 of the UP Electricity Supply Code 2005 explicitly prohibits disconnection when a bill is formally disputed with baseline evidence submitted. Remote disconnection while my flat was vacant, following my written communications from January through March, was an unlawful act.
Finally, they claimed the Check Meter test confirmed the accuracy of the smart meter. In reality, the Check Meter operated without transparent calibration records and was removed after 50 days without issuing a joint inspection report signed by the consumer, violating Clause 5.7 of the Supply Code. A test conducted without procedural compliance carries zero evidentiary value.
Faced with this wall of statutory violations, the local bureaucracy collapsed. I registered a 1-star negative feedback entry on the Uttar Pradesh government Jansunwai grievance portal (Grievance Reference: 40014026064730), attaching six explicit points of administrative misconduct. The system locked the grievance and escalated the file directly to the Superintending Engineer (SE) for mandatory re-investigation. Stripped of their pre-written scripts and facing formal accountability for record tampering, unreturned private property, and procedural breaches, PVVNL abandoned its demand.
State utility companies rely on citizen fatigue. They expect consumers to break under the pressure of automated threats and arrogant field officers. But when you systematically organise your evidence, master the governing regulations, and refuse to accept falsified records, the entire apparatus fails. This case stands as a permanent public record: PVVNL's machinery can be defeated, and arbitrary power can be brought to account.
Follow/Subscribe TimesView Blogspot















ct2026.001.jpg)











