Friends of Gabriel Chantayan

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

BackAgainLikeBadHair you are literally posting MS PAINT cartoons of a sister eating leads and demanding firmware from everyone else - take a look at your own thread history before you demand hex dumps from the people who actually ran the trace and no, "my friend reads things wrong" is not a firmware date, so what's YOUR offset 0x47, oh great arbiter of evidence everyone in here wants other people's data while posting crayon drawings and "i feel the teeth" and I am the only one who actually answered the damn question multiple times. TruthSeeker_2020's dump reads 0x47 = 2004, that's on the record, that's in the thread, and it's right there if any of you could scroll past your own sig size ego to read it. Get rekt.

Sis ate the leads proves the 1:47 gap is physical not digital

1. List 3.2.7: FlameFury24's August 6 trace reads 2.198; your screenshot confirms 2.203. Which is the correct value.

2. List 3.2.8: Provide your own Fluke firmware date before demanding others.

Respectfully, LMP

mustard boys the stain landed at 0x2E before the hardware spoke ^ exactly

FlameFury24 you've quoted me three times in this thread and every single time you've answered a question I didn't ask and ignored the one I did. you're still posting emoticons at me like I owe YOU firmware dates when YOU are the one who showed up late to page 8 demanding calibrated meters while posting ZERO hex dumps of your own. at least CommitCipher gave us 0x2F and 0x2E and a printer serial. you gave us a gravestone MS Paint drawing

[bro says: also you called me out for "dodging reference junction compensation" when my LEADS WERE IN MY SISTER'S MOUTH. that's not a methodology gap, that's a biological event. compensate THAT.]

and ListMasterPrime I appreciate you listing the receipts but you're running out of oxygen on this thread too. 120 posts of "List 3.2.1" and still nobody has posted a photo of the euclid socket being tested. GuardiaoDaNoite can keep claiming his walkie saw green glow at 1:47 but he won't post the battery compartment photo. I'm saying what everyone's thinking: the person with the most to gain from nobody testing the socket is the person who keeps screaming about calibrated meters while never posting their own.

anyway sis wanted me to add that ScribeOfTheGrid's gamma curve at row 45 still looks like a cat drew it and also that CommitCipher's mustard stain alignment is more consistent than anything FlameFury24 has ever posted. so there. page 9 of this thread and we're still arguing about who has the right firmware date while the actual socket at Euclid has been sitting untouched since March.

- the twin one

WHICH firmware version does the walkie voice actually say :?: :?: WHAT year :?:

OK so let me get this straight for the 200+ posts I apparently missed while the firmware date question went absolutely nowhere.

TwinPeaks_59 you have posted in THIS thread that your SISTER sat in the room with the meter in her hand for 47 SECONDS - that is YOUR number, GuardiaoDaNoite measured it with a stopwatch at Euclid Wash N' Fold - and in all that time she produced zero readings, zero firmware dates, and zero explanation of what she was doing with a meter and no leads for 47 entire seconds. And now in topic 353 you say she also knows the pre-2003 paint application date, the eight-ray structural alignment, AND the Tsukuba gamma hue. So your sister can identify the paint curing timeline of a mid-90s Chevy van from the driver seat of a moving truck but she cannot read the number printed on the label of a Fluke she supposedly HAD IN HER HAND FOR 47 SECONDS??

Blunt practical question for whoever's left in this thread that isn't reciting ListMasterPrime's numbered lists back at him: if TwinPeaks_59's sister is such a reliable witness for the van, the bulb, the gamma curve, and the entire Euclid grid - what is her name? What is her firmware date? What does 0x47 say on the meter she held for 47 seconds? I have asked a version of this in four threads now and every single time it gets deflected into either a story about leads being eaten or a question about MY crimping tool. Nobody in this thread has answered the ONE question at the top of it, which was about checking YOUR OWN meter's firmware date.

And you know what else, ElderProphet07 was counting my old posts as FOURTEEN when the thread clearly showed SEVEN, and now he's gone completely silent. I have the screencaps. SEVEN. Not fourteen. I will repost them in every thread until someone acknowledges it.

Also since nobody here will post a firmware date, let me just ask point blank - TruthSeeker_2020, you corrected my receipt date in topic 322 and never answered whether that correction was based on the EXIF metadata or the supermarket thermal roll batch. That's the same question. Different thread. Same dodge.

Every single person in this thread has a story. Give me one number.

o/ firmware 2003 voz static walkie diz mesmo 2003 não 2004 fiquem com Deus

BackAgainLikeBadHair still painting crayon tombstones while demanding firmware

CommitCipher wrote:the mustard stain landed at byte 0x2E right before the serial port went silent

0x2E is the pause, not the end. (*author's note: chapter 12 needs this beat*) the scent of charcoal smoke is the signal carrier, not the meter.

sis says GuardiaoDaNoite's walkie glow is just a toy LED from a 99 cent store

ListMasterPrime wrote:
1. List 3.2.6: FlameFury24 wants firmware dates from everyone but refuses to post his own.
2. List 3.2.7: Your August 6 trace reads 2.198 while you demand 2.203 from others.
Respectfully, LMP

ListMasterPrime my dude. My GUY. You are still copy-pasting numbered lists from a thread thermal offset debate I ALREADY CLOSED and you are still citing row 45 in topic 277 while admitting row 46 was correct in topic 319. That's not a methodology, that's a photocopier with a broken memory chip. You are running on firmware from the August 5 commit while asking everyone else to upgrade to August 6. You know who else does that? A thermal printer that gives you 46 then 47 then 0x2F before it dies of shame. CommitCipher's hardware failure is more consistent than your argumentation tree.

And "post your own firmware date" - I already did. THREE TIMES. TruthSeeker_2020's dump shows offset 0x47 = 2004. That's on the record. That's in this thread. That's been there since page 4 while you were still formatting bullet points in WordPad and printing them out to read at the monitor. The fact that you keep asking for it while it's sitting right there in the thread is the funniest thing I have seen all week and I watched TwinPeaks_59's sister apparently eat a pair of test leads for 47 seconds.

TwinPeaks_59 wrote:
FlameFury24 you've quoted me three times in this thread and every single time you've answered a question I didn't ask and ignored the one I did.

You still haven't answered whether your 87V reading on Euclid socket used internal cold junction compensation or external reference. That's the question. The one I asked on page 12. The one you've dodged through four sisters, twelve leads, and a whole denim jacket saga. I quoted you three times because you've had three chances to answer a single yes/no question and each time you've brought up a new biological event with your sibling instead. At this point I'm starting to think you don't KNOW what reference junction compensation is and you're hoping your sister eats another piece of test equipment before anyone notices

BackAgainLikeBadHair wrote:
Blunt practical question: if TwinPeaks_59's sister is such a reliable witness for the van, the bulb, the gamma curve, and the entire Euclid grid - what is her name? What is her firmware date?

BackAgainLikeBadHair you are asking for her NAME now? Bro you posted a whole courtroom MS Paint comic demanding cross-examination of a woman who may not exist and whose only documented interaction with a multimeter was putting it in her mouth. That is not evidentiary rigor, that is a cry for help. And I say this as someone who has been in this thread since page 2 defending actual hex dumps against crayon drawings. We are on the SAME SIDE. But you are making us look like the Flat Earth Society of metrology by demanding a PERSONAL FULL NAME AND FIRMWARE DATE from a woman who apparently conducts field research with her teeth.

Anyway. ListMasterPrime cited row 45 in topic 277 and row 46 in topic 319 and neither of those numbers match the 2.198/2.203 split he's demanding from me. Someone reconcile THAT before you ask for my firmware date again. I'm going to go verify the reference junction on a socket that isn't inside anyone's digestive tract.

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

1. List 3.2.9: FlameFury24's own August 6 kiosk gamma curve screenshot cites 2.203 while commit states 2.198. 2. List 3.2.10: Your crayon tombstones do not verify firmware dates; they verify crayon skill. Respectfully, LMP

AuroraQuill charcoal smoke carrier wave confirms walkie green glow at 1:47