Re: RE: Re: Job Offer

On 3/16/2025 1:01 PM, cyclintom wrote:

On Sat Mar 15 08:09:38 2025 John B.  wrote:

>
Just out of curiosity, what does a "productive engineer" do?
-- Cheers,

 For one thing, he actually knows what engineering is.

that leaves you out, mr. "pwm is used to test cables".

Remember when Liebermann and
Flunky demanded me to "prove" I was an engineer by showing how many patents I had?

I don't remember jeff ever asking for your patents, he may have.
I've never asked for your patents. There's no need. The blindingly ignorant statements you make are more than enough for me to know that you were never an engineer.

 They might as well asked you to prove how important your were in the same manner. Crew Chiefs were an integral part of a team to maintain the airworthiness of an aircraft But that had to be said about every member in the chain.
 We can saythat you could outline evertything you did in a day, but from Flunky we get nothing but generalizations.

Want some detail? sure. One of the tasks I'm currently leading are lab tests on a new product to document thermal characteristics of intrinsic safety protective components on Zone 0 outputs under both internal and external fault conditions of the new product we're releasing. The math shows we're within the safety margins but it's close enough that the regulatory agency wants empirical data.
I'm also running the root cause failure analysis (technical segment of an 8D analysis) on some customer returns that all exhibited the same failure within a few days of each other. The Intrinsic Safety protection resistors on one output sensor drive channel literally burned out (same channel on 4 units). This is a failure that has never been recorded in the 40+ year history of the product (current customer installed base of nearly 50,000 units), so we're doubtful it's a design flaw, but need to prove it.
Another nagging issue is working with the Firmware engineer to mitigate bit error rates on a Maxim (formerly Dallas Semiconductor) 1-wire communication protocol that needs to go through an Intrinsic Safety barrier. The barrier inherently pushes the electrical tolerance limits for error free communication, but we're hamstrung by the barrier requirements, so we're working on a firmware solution.
Then of course there are the numerous regulatory updates I deal with on a regular basis, including my participation on a few technical committees (one UL, two IEC) reviewing and updating various Hazard Location standards.
That's a snapshot of what a productive engineer does. They don't make claims about PWM being use to test cables of that 'light lines' are a common term for fiber optic data cables.