ProbeLem

Call Website Contact the business

ProbeLem Continuous education
2. Love what you do, do what you love
3. Glorify God in the work of your hands
💬Why ProbeLem? Probe
a. b. Purpose
💡2. Plot
🎥3. Protagonist

ProbeLem™ | Traveling Fleet ETO

Documenting the real-world electrical knowledge
I wish existed when I was starting out.

📺 youtube.com/
📖 probelem.substack.com
🎙 Deep ProbeStudies: patreon.com/ProbeLem

🔎 PRObing Right into the Problem! 🔎PRObing Right into the Problem!
🚀Sharing my professional experience as Travelling Fleet ETO in Europe with average 2 - 3 weeks per vessel.
💡Vision:
To create digital library of electrical educational content for the resources of the learners.
🎯Mission:
To share my professional experience conveyed in a first-person perspective as travelling Fleet ETO.
📌Channel Values:
1. It is the coming together of three unique words:
🔍1. the test prod of an electrical multimeter or any testing device. to investigate or examine something.
💡2. Problem
- without this, there is nothing to resolve or probe; there is no plot in a story; there is no subject in a sentence.
🎥3. Lem
- of course, my name on it; the protagonist of this story. When we combine these characters, there is a profound play on words that describes the progress of my page:
🔍1.

Hey probe enthusiasts,I am building a sort of some personal database that is related to my career that may add some valu...
07/09/2026

Hey probe enthusiasts,

I am building a sort of some personal database that is related to my career that may add some value to yours as well. For now it is a simple wiki in Notion, but can be a useful free template for y'all enthusiasts. Future ready AI integration.

DM me for details.

Keep on probing!

The nameplate says 230V. My Fluke 177 says 397.9V AC across the indicator block's X1 and X2 terminals.The LED was illumi...
29/08/2026

The nameplate says 230V. My Fluke 177 says 397.9V AC across the indicator block's X1 and X2 terminals.

The LED was illuminated. That reading stopped me from treating the replacement as a routine spare-part change.

I was working on a distribution-panel indication lamp after the original transformer-based unit failed. The old assembly had a localized burn mark. The available replacement was a Schneider ZBVM1 LED light block marked for 230 to 240V AC.

Here is the part that matters: an illuminated LED proves that it was illuminated at that moment. The meter proves the voltage at its terminals. Neither observation tells us the sealed block's internal circuit, temperature, remaining life, or suitability for continuous duty.

Schneider's published supply range for this model is 195 to 264V AC. The 397.9V reading was outside that range. A 1kV surge figure is not permission to run a component continuously above its stated supply limit.

In the full Patreon field case, I separate what I observed, what the manufacturer documents, and what theory can only explore conditionally when the internal topology is unknown.

If you know an ETO who has seen a component keep working outside its nameplate conditions, forward this to them. What would you verify before accepting that installation for continued service?

The full Patreon field case is in the comments.

Keep on probing!

27/08/2026

After a generator overhaul, the commissioning test is where the work is proven.

In this field sequence, we verify phase-to-phase resistance, rotor and exciter-stator resistance, and insulation condition with dielectric absorption ratio (DAR) tests. We record the measurements against the test plan before the generator returns to service.

The readings are not just numbers. They create traceability between the overhaul work and the machine going back into service.

Affiliate tool pick for insulated electrical work: Wera Kraftform VDE 1000 V 6-piece screwdriver set. This is a recommended tool, not the meter used in this commissioning test.
https://s.shopee.ph/1LfIxy39Iu

Keep on probing!

──────────
🔔 Subscribe for real-world marine electrical troubleshooting:
https://www.youtube.com/

An ammeter can read correctly for 28 years while a current-transformer secondary circuit is still missing its intended g...
23/08/2026

An ammeter can read correctly for 28 years while a current-transformer secondary circuit is still missing its intended ground.

I found that during a drydocking replacement on one engine-room fan circuit. The old CT frame had become brittle after decades of heat cycling, so I replaced it with an equivalent unit. Its sister circuit showed the expected arrangement. The secondary was connected to the meter, and one side had an intentional ground.

The other CT had also been running for years. Its ammeter was normal. But when I traced S1 and S2, neither terminal had a grounding conductor.

That reading had proved only that the measurement path worked. It had never proved that the secondary circuit had a safety reference.

The correction was simple: I landed the specified green and yellow conductor on the designated secondary terminal and tied it into the panel's common ground point. The important part was the thinking before the correction. One intentional ground is different from a closed measurement circuit, and it is also different from opening a CT secondary while primary current is flowing.

If you work around CTs, forward this to the ETO or technician who may see a normal ammeter and assume the whole circuit is already right.

The Patreon link is in the comments.

Keep on probing!

17/08/2026

My meter showed 76.3 volts on a motor feeder that was already isolated and
locked out, and the reading would not settle.

I could not call it live, and I could not wave it off as ghost voltage. I kept
treating the conductor as energized, changed one measurement condition, and the
indication collapsed under an approved low-impedance load. That explained the
number, and the prove-dead sequence still had to cover every required
combination.

The question I get is never "what was the fault." It is "how did you know where
to start looking." I packaged the answer... 15 reusable AI skills, an offline
evidence logger, editable report templates with worked examples, and 8
anonymized field cases including this one.

If you know an ETO or engineer who keeps getting handed a fault with no
starting point... forward this to them.

Link in the comments.

Keep on probing!

16/08/2026

This UPS served for ~28 years. What are the key steps to retrofit this system? The best opportunity is during drydocking and major repair window, I think.

05/08/2026

Every new AI session made me pay the same tax... I had to explain the project again.

The notes already existed. The source files, technical decisions, active tasks, and unfinished drafts were already on my computer. But every time I changed tools, I became the memory bridge between them.

That is why my Obsidian vault stopped being only a notes folder.

I began opening the same ProbeLemOS folder in Obsidian and VS Code. Obsidian became the human-facing cockpit. VS Code became the shared CLI playground where Claude Code, Codex, Gemini Antigravity, and bounded local models could enter the same governed files.

The system is organized around Context, Capabilities, Cadence, and Connections. Active work moves through dedicated workspaces and projects. Every deliverable still stops at the Approval Gate because AI processes the work, but I make the decision.

The cockpit now spans LeMacBookM5Pro, ProbeLem-Linux/LeMint, and the rugged LeMovo-P14s field tool. Tailscale, Git, and Google Drive connect them through different paths without pretending that every copy has the same authority.

I wrote the complete story because I think many creators and engineers are solving the wrong problem. We keep searching for the perfect AI tool when the real weakness is often the handoff between tools.

If you know an ETO, engineer, or creator who keeps rebuilding their context in every new chat... forward this to them.

The full cockpit tour is linked in the comments.

Keep on probing!

Every new AI session made me pay the same tax... I had to explain the project again.The notes already existed. The sourc...
05/08/2026

Every new AI session made me pay the same tax... I had to explain the project again.

The notes already existed. The source files, technical decisions, active tasks, and unfinished drafts were already on my computer. But every time I changed tools, I became the memory bridge between them.

That is why my Obsidian vault stopped being only a notes folder.

I began opening the same ProbeLemOS folder in Obsidian and VS Code. Obsidian became the human-facing cockpit. VS Code became the shared CLI playground where Claude Code, Codex, Gemini Antigravity, and bounded local models could enter the same governed files.

The system is organized around Context, Capabilities, Cadence, and Connections. Active work moves through dedicated workspaces and projects. Every deliverable still stops at the Approval Gate because AI processes the work, but I make the decision.

The cockpit now spans LeMacBookM5Pro, ProbeLem-Linux/LeMint, and the rugged LeMovo-P14s field tool. Tailscale, Git, and Google Drive connect them through different paths without pretending that every copy has the same authority.

I wrote the complete story because I think many creators and engineers are solving the wrong problem. We keep searching for the perfect AI tool when the real weakness is often the handoff between tools.

If you know an ETO, engineer, or creator who keeps rebuilding their context in every new chat... forward this to them.

The full cockpit tour is linked in the comments.

Keep on probing!

17/07/2026

One day after I restored both radar units, the X-Band failed again.

The earlier repair was still holding, so I started from the evidence. Three alarms pointed to a different problem: the antenna was not turning.

The real cause was a broken lower drive belt. There was no correct spare aboard, so the repair had to wait. When the replacement arrived, we restored the radar echo and confirmed normal performance.

This is Part 2A of the radar emergency. It is a real troubleshooting story about following the alarm pattern, comparing the working system, and letting the evidence lead the repair.

YouTube members can watch it one day early. It goes public tomorrow. The YouTube link is in the first comment.

Keep on probing!

Address

Makati
1630

Opening Hours

Monday 9am - 5pm
Tuesday 9am - 5pm
Wednesday 9am - 5pm
Thursday 9am - 5pm
Friday 9am - 5pm
Saturday 9am - 12pm

Telephone

+639087228140

Website

Alerts

Be the first to know and let us send you an email when ProbeLem posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to ProbeLem:

Shortcuts

Share