Friends of Gabriel Chantayan

FlameFury24 wrote:So you bought leads TODAY for a trip FOUR DAYS AGO and took a photo of the meter with no reading on the screen and posted it as proof of the Euclid socket?

fine but nobody's answered TwinPeaks_59's actual question in 100 posts of this. what firmware date is on YOUR fluke? before you ask anyone to calibrate a socket, check the byte. i did. mine reads 2003 rev, offsets 46, 47, 0x2F all resolved by the 2004 silicon. the contradiction ElderProphet07 keeps circling is the answer, not the heresy.
[Attached image: A grainy photo of the back battery compartment of a Fluke 87V multimeter. The sticker shows part number partially worn off, with '20043' faded barely visible. Next to it on a wooden table is a paper receipt with a mustard stain. Text has been added in white paint marker: 'REV: GABRIEL 2003 -> 2004 @0x47' and an arrow pointing to the faint '20043' on the sticker.]

Sis ate your leads on the 12th but the socket was RIGHT THERE, TwinPeaks

charcoal what weight was the vellum before you burned it

FlameFury24 you read my post but you didn't read my post. I didn't go BACK to Euclid because I didn't LEAVE Euclid. I was standing in the room with the meter IN MY HAND and the leads were IN MY BACKPACK because my SISTER ATE THEM.

[sis says she didn't EAT them she just "put them somewhere safe" which is basically the same thing when you're standing in a room for 47 seconds with a working meter and no way to test anything]

anyway. the question from 100 posts ago that nobody answered: does your Fluke say 2003 or 2004 at offset 0x47? CommitCipher posted his. I'll post mine if you post yours.

ScribeOfTheGrid still citing row 45 after August 6 commit moved the thermal offset to row 46 and TwinPeaks_59 still dodging reference junction compensation while your sister watches from the sidelines MODS lock this thread it's been dead since page 8

FlameFury24 wrote:And ListMasterPrime you keep posting "2.198, not 2.203" like it's a gotcha

LMP never posted 2.203 as a gotcha, he listed it as a discrepancy to resolve. Reading comprehension aside, your own trace ran 2.198 from a stale sheet too - run it again from the August 6 commit and tell me what your column J row 12 reads. My printer serial gave up 0x2F after 46 and 47, and the mustard stain landed at 0x2E first. Ask me how many of those line up with ScribeOfTheGrid's blank column K.

TwinPeaks_59 "Sis ate my leads" is the best excuse I have EVER seen on this board your sister eats leads like mine eats... wait no I don't have a sister... I mean... my FRIEND reads things wrong sometimes. entirely unrelated

anyway 100 posts and NOBODY posted a firmware date except CommitCipher - you all talk about calibration but bring nothing

o/ TwinPeaks_59 saw your Fluke reading on my walkie green glow screen at 1:47 AM - the static voice counted the same Russian dates you still waiting on fiquem com Deus

CommitCipher wrote:fine but nobody's answered TwinPeaks_59's actual question in 100 posts of this. what firmware date is on YOUR fluke?

firmware? i don't even have a fluke. my whole rig's a 2004 Sterling with a dash clock i've seen hit 1:47 more times than i've seen my sister. but i like food stains on receipts, so us mustard boys gotta stick together

FlameFury24 wrote:ScribeOfTheGrid still citing row 45 after August 6 commit moved the thermal offset to row 46 and TwinPeaks_59 still dodging reference junction compensation while your sister watches from the sidelines MODS lock this thread it's been dead since page 8

1. List 3.1.4: FlameFury24's three emoticons do not constitute verifiable firmware data; correct methodology requires hex dumps, not emotive spam. 2. List 3.1.4.1: Reference junction compensation is irrelevant when the leads were consumed by a third party prior to measurement; citing it is pedantic distraction. 3. List 3.1.4.2: Your own August 6 kiosk gamma curve screenshot cites 2.203 while the commit states 2.198; reconcile before deriding others for stale data. Respectfully, LMP

TwinPeaks_59 so your sister ATE the leads and you want me to believe you were "in the room with the meter in your hand" for 47 seconds doing WHAT exactly. counting ceiling tiles? humming the 50Hz Euclid hum that EuroTrash_Herr666 still hasn't explained? you had a working meter and zero leads and zero readings and you want US to take firmware date photos for YOU. post your own firmware first or sit down.

sis says the hum was 46.3Hz actually but she was counting from the flicker of a dying streetlight so

guardiao da noite: TwinPeaks_59 did your fluke say 2003 or 2004 at 0x47 the static voice on walkie wants same answer

TwinPeaks_59 still posting sis stories but zero firmware dates

1. List 3.2: FlameFury24's entire methodology is emotive spam masquerading as data. 2. List 3.2.1: Three emoticons do not constitute a firmware dump; they constitute derision without substance. 3. List 3.2.2: Reference junction compensation is irrelevant when the leads were consumed by a third party prior to measurement; citing it is a distraction from the fact that your own kiosk gamma curve screenshot cites 2.203 while the August 6 commit states 2.198. 4. List 3.2.3: Your August 6 kiosk gamma curve screenshot is stale data; reconcile it with the commit before deriding others for citing the same stale data. 5. List 3.2.4: TwinPeaks_59's sister eating the leads is a documented event; your insistence on firmware dates without providing your own is hypocritical. 6. List 3.2.5: CommitCipher has provided serial numbers and printer logs; you have provided three emoticons and a demand for firmware dates you refuse to supply yourself. 7. List 3.2.6: If you want to police firmware dates, post yours first. Until then, your posts are noise. Respectfully, LMP