Friends of Gabriel Chantayan

BackAgainLikeBadHair wrote:Also EndTimesEli MATH is still off by 0.3Hz in his Fuji calibration cross-reference from topic 262. Did the math in your HEAD or on a broken calc?

0.3Hz. You want to talk about 0.3Hz while the entire board is running meters on pre-rev firmware and citing artifacts as evidence. You want to nitpick MY math while BackAgainLikeBadHair posts screenshots of a Fluke with firmware 1.8 from November 2004 and everyone cheers like she brought the Ark of the Covenant to Euclid. That meter has been producing measurement artifacts for ELEVEN MONTHS because the 47Hz baseline table wasn't added until rev 2.0. Every reading she takes at that socket is contaminated. Every single one. And you're worried about MY cross-reference being off by three tenths of a hertz.

LISTEN TO ME. ElderProphet07 posted his firmware date ON THIS BOARD. Topic 350. He said 1.8, October 2004. He said the calibration table was added in rev 2.0 mid-2005. That means his meter, and every other pre-2005 Fluke 87V on this board, produces a 47Hz artifact at the 1:47 window because the firmware literally does not have the baseline correction for that frequency range. It's a BLIND SPOT. The meter fills it in with a default value. That's not the Going Quiet showing up in the readings - that's the meter lying to you because it doesn't know any better.

And you want to know why I care about YOUR 0.3Hz? Because if you're doing calibration cross-references against a contaminated baseline you're not finding the signal you're finding the NOISE FLOOR. The Going Quiet is beneath the artifact. It's in the gap BETWEEN what the meter reports and what the meter SHOULD report if it was running proper firmware. That's where the silence lives. That's the whole point. That's what I have been screaming about for SIX THREADS and every time I post it someone wants to talk about column B versus column C or spindle torque or whether the paper was static or moving.

You caught me doing math in my head. Fine. GUILTY. I was sitting on my porch step whispering timestamps into the dark instead of using a calculator because the gap was thirty one hours long and I didn't feel like I had time to find one. But at least I'm looking at the RIGHT GAP. At least I'm not standing at a socket with a meter running 2004 firmware screaming "LOOK THE LIGHT IS DARK" when the meter told you that before you even plugged it in.

ElderProphet07 I am not attacking you. You posted more honest data in one post than most people post in a month. But if you're right about that firmware date then we need to go back through EVERY Fluke 87V reading on this board and check the firmware stamp. Every one. Before we cite it. Because right now half our evidence base is ghosts in the machine and the other half is people too busy arguing about receipt printer columns to notice.

BackAgainLikeBadHair run your cross-reference again. Use rev 2.0 as your baseline. Watch what happens to the 0.3Hz. Watch what happens to ALL of it. And then ask yourself why nobody has done this already.

o/ FlameFury24 still counting wrong in spreadsheet but walkie green glow 1:47 left ear only, multimeter 0.00 Gabriel counting in static voice, not firmware date



TechAngel_00 STILL no hub override test SakuraMirror STILL no lot code ClassOf04_Truther STILL no jerky voltage

fiquem com Deus

ElderProphet07 still counting to seven with his fingers behind his back

e: typo - endtimeseli's 0.3hz complaint is valid but he's been running that fluke since '04 without DST correction so

^ exactly what i was going to say

who has the firmware 2.0 update file and why has nobody posted it yet

lyrik asking scribe for a cell value for the sixth time across six threads while his own vigil recording still has a 47.3hz tram braking hum that maps perfectly to the euclid streetcar line and he's been dodging firmware calibration traces since june. i called you out in topic 324, you asked about my measurement equipment instead of answering the frequency match, and now you're here demanding spreadsheet theology from a man whose hidden sheet you could verify yourself if you ever posted your own calibration baseline. scribe's vlookup is a distraction from the fact that your entire june 22 dataset is contaminated by a municipal transit system and you know it guten abend, bitte um die kalibrierung

FlameFury24 coming at me about reference junction from page 12 of the AC manual-lock thread while his April hex dump is still collecting digital dust like a cursed screensaver on a work computer nobody's touched since 2003

((sis can i point out that he's been posting in ALL CAPS about calibration chains while running firmware that predates the 47Hz baseline table by eight months?)) [bro let me cook] - no actually let ME cook because YOU are the one who brought the Vishay resistor to OSU physics lab and got it verified and what did FlameFury bring? a screenshot of a meter he borrowed from someone he met at a bus stop probably

Anyway

ElderProphet07 you keep saying I'm deflecting but I'll answer the reference junction question RIGHT HERE for everyone to see: the junction compensation on my Fluke 87V serial 8[REDACTED]7 was compensated against a known 0°C ice bath at the hardware store before I even walked to Euclid. I zeroed the leads. I have a photo of the ice bath with the newspaper from that morning because I'm not a monster who leaves things undocumented. (sis says "you're posting a photo of ICE now" and yes M it's a photo of ICE because that's what being thorough looks like unlike SOME people's hex dump situation)

But here's what's actually killing me about this thread - GuardiaoDaNoite posts a blurry photo of a walkie-talkie with a green glow and a CAT in the background and y'all are debating the firmware date on his multimeter like THAT's the priority. There's a CAT in the evidence photo. A cat. On cardboard boxes. Near a workbench with a tape measure that's YELLOW. Nobody in this thread has asked what the cat's name is or whether the cat was present during the 1:47 reading or if the cat has its OWN testimony. GuardiaoDaNoite we need answers. Is the cat a witness or a distraction. This is vital to the methodology.

((bro is asking about the cat's name instead of answering the junction question and i am dying)) [the cat question IS the junction question M read the room]

ListMasterPrime filed TwinPeaks_59 under sub-category 3D in his list which honestly I'm honored. Being in a list at all is an achievement when you share a computer with someone who leaves seventeen browser tabs open about gamma curves

BackAgainLikeBadHair - I still don't have the socket close-up from topic 154 because I WAS AT THE VIGIL WITH THE FLUKE AND WITNESSING NOT PHOTOGRAPHING and I have explained this four times now across three threads. But you know what I DO have? A photo of the ice bath I mentioned. And a cat. Not my cat. GuardiaoDaNoite's cat presumably. But the energy is similar.

(sis says to add that ScribeOfTheGrid's hidden sheet drama is giving "I made a mistake in July and built a spreadsheet mythology around it instead of admitting I copy-pasted the wrong range" and honestly she might be cooking on that one. But I also think Scribe is just trolling at this point and we're all biting. Either way the 0 vs NULL distinction is the funniest thing on this board since ClassOf04_Truther's jean count contradiction)

EndTimesEli wrote:who has the firmware 2.0 update file and why has nobody posted it yet

from an outsider's perspective, this is the actual question that matters here: if the firmware date on your meter determines whether you are measuring Gabriel or just a software bug, does anyone actually know how to flash the unit? because I have been reading these threads for months and nobody has explained the physical process of getting the new code onto the device - do you need a specific serial cable, is there a bootloader mode you have to trigger, or are we all just assuming the update happens magically when you hold the dial in the direction of Euclid

TwinPeaks still making up pF numbers while Grace dodges hex dump for month five

oh so the firmware date is the excuse now?? like the meter just decides what's real based on when it was built

LurkingObserver42 the flash process is documented you just refuse to read it

EndTimesEli asking the REAL question but let me go further - even if someone HAD the 2.0 update file, where's the fluke-approved flashing utility that doesn't void the warranty because I checked the Fluke website in June and the 87V firmware page has been 404 since 2005 just saying

Kael_Vs_Chantayan you literally just wrote "TwinPeaks still making up pF numbers while Grace dodges hex dump for month five" in topic 350 while YOU have been dodging the Novosibirsk timezone anchor since APRIL in topic 305

Where is YOUR hex dump brother?? I have a Euclid receipt with DST flag from June 12 and you have SEVEN confirmed lowercase exif occurrences across topic 237, 212, the Tsukuba thread, cottage cheese thread, printer serial thread, and now here lol

I rebuke this selective memory in the name of Gabreil's light!!

LurkingObserver42 wrote:from an outsider's perspective, this is the actual question that matters here: if the firmware date on your meter determines whether you are measuring Gabriel or just a software bug, does anyone actually know how to flash the unit? because I have been reading these threads for months and nobody has explained the physical process of getting the new code onto the device

i think exactly this