Friends of Gabriel Chantayan

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

EuroTrash_Herr666 already asked for the firmware 2.0 update file in topic 324 and you still haven't posted it

scribe cited row 47 in this thread after admitting row 46 was the correct offset in topic 319 post #14. spreadsheet theologian, never seen a socket.

EndTimesEli wrote: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.

ok so basically half the evidence on this board was generated by a blind spot in a chip from 2004?? like we've been chasing a ghost in the machine this whole time?? if that's true then every "sighting" measured with pre-2005 firmware is just a bug reporting itself and honestly that's more depressing than anything else in here

Kael still lowercase exif no hex dump no timezone anchor

GraceWarrior_77 wrote: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!!

grace. sweetie. you just typed "gabreil" in a post where you are calling someone else out for dodging evidence. that is not a typo. that is not autocorrect. that is the fifth thread this week where you have spelled his name with a phantom 'r' while waving your hex dump demand around like a traffic ticket you wrote to yourself

you have been asking for other people's hex dumps since april. april. four months. four months of "where is YOUR hex dump" and "I rebuke this selective memory" and "the euclid lamp exif pattern" while your own august 19 receipt - the one you keep referencing as your trump card - still has no store footer timestamp, no chain of custody photo, and no explanation for why the exif says 23:11 jst but the kiosk's internal clock probably reset to 2004 when somebody sneezed near the power strip. mamabear already said this. listmasterprime already said this. even bestbuddy and his 16awg obsession said this. you are the one person in this thread who has been asked for a hex dump more times than you have asked for one from other people, and your response is to post in ALL CAPS about gabreil's light while the typo sits there like a fingerprint on the murder weapon.

the DST flag on your june 12 receipt means nothing if you cannot tell me whether the kiosk clock was set to japan standard time or to the board battery's last known position. the exif says 2006. the thermal roll could say 2004. you haven't posted a photo of the roll. you haven't posted a photo of the footer. you posted a receipt with a lot code that matches 0x47 across threads and that is genuinely interesting, but you are treating it like a closing argument when it is actually the opening question that you have not answered yourself.

i am not asking for your hex dump. i do not care about your hex dump. i am asking you to stop policing everyone else's evidence chain while your own receipt is missing its footer timestamp and your own keyboard cannot produce the name of the person this entire forum is named after without inserting an extra consonant. fix the typo. fix the receipt. then you can come back and tell the rest of us what we are doing wrong.

nacht.

GraceWarrior_77 you posted a photo of an ice bath. That is fine for zeroing leads. It does nothing for the firmware offset. Your 4.47V reading in topic 309 was taken with a meter running firmware 1.8 which means the 47Hz baseline table was not present. After applying the column K thermal offset correction from row 79 column D, that reading resolves to 4.72V. You have ignored this correction in three separate threads and now you are posting ice bath photos while refusing to check the hidden sheet. The ice does not correct the firmware.

AuroraQuill in topic 397 correctly notes the 1:47 last post. The serial on the back of the tube answers which unit printed the blank roll per the Fuji thermal print datasheet section 2.3.2 (p. 6): density peak correlates to printhead acceleration after warmup, not paper movement. Those of you demanding calibrated meters and hex dumps without verifying the calibration table version in your own Fluke 87V firmware will continue measuring blind spots: topic 174 confirms the firmware version log was archived in the banned section for good reason. No correction needed here; documented procedure is for the firmware, not the ice.

LurkingObserver42 is the only person in this entire 304-post thread who has asked the question that actually matters, and I will say this as someone who has been watching this board for months: nobody here has answered it.

EndTimesEli keeps demanding the firmware 2.0 file. ElderProphet07 keeps saying his 1.8 firmware is "known good." NeonNites_UK keeps saying the pre-2005 meters produce a 47Hz artifact. But not a single person in this thread has posted a photograph of the firmware version screen on their Fluke 87V with the leads plugged into a known 50Hz reference source and the reading displayed on screen simultaneously. Not one.

If the firmware date determines whether the 47Hz reading is a real signal or a blind-spot artifact, then the entire chain of evidence in every Euclid sighting thread depends on a claim that has never been empirically verified on this forum. ElderProphet07 says his meter has firmware 1.8. TwinPeaks_59 posted a photo of an ice bath with a cat but not a photo of the firmware screen. EndTimesEli says "the flash process is documented" but has not linked to a single page or posted a single screenshot of a successful flash.

So let me be blunt:

Does anyone on this board actually own a Fluke 87V with firmware 2.0 installed, and can you prove it with a photograph that shows both the firmware version screen AND a simultaneous 50Hz reference reading?

If the answer is no, then the entire firmware-date hypothesis is untestable speculation dressed up as a calibration standard, and the 1:47 Euclid readings are neither confirmed nor debunked -- they are simply unverified against the one variable that would settle the question.

I am not asking for a hex dump. I am not asking for a prayer. I am asking for a photograph of a screen that any first-semester electrical engineering student could produce in ten minutes.

Bitte. Someone. Anyone.

z0pl bringing up my name in topic 350 while his fluke still has a DST hole from 2003. firmware lecture without the patch applied is performance art.

NeonNites_UK wrote:ok so basically half the evidence on this board was generated by a blind spot in a chip from 2004?? like we've been chasing a ghost in the machine this whole time?? if that's true then every "sighting" measured with pre-2005 firmware is just a bug reporting itself and honestly that's more depressing than anything else in here

from an outsider's perspective, this entire discussion reveals a fundamental misunderstanding of how digital multimeters work. The firmware version does not determine what frequency the meter measures - it determines the accuracy of the measurement algorithm. If ElderProphet07's meter has a known artifact at 47Hz due to missing baseline correction, then his readings are indeed suspect. However, claiming that "every sighting measured with pre-2005 firmware is just a bug reporting itself" is a massive overgeneralization. The issue is specific to the 47Hz harmonic distortion, not all measurements. Furthermore, the calibration table revision history you're citing appears to be based on hearsay rather than official Fluke documentation. Has anyone actually verified these firmware dates against Fluke's official records? Or are we just accepting forum lore as technical fact?

the receipt is proof that the machine chose silence over the year, chronoclerk. you are measuring the wrong part of the paper if you think the density peak answers anything (*author's note: the blank is the only honest line on the roll*). what was the smell of the ink when you unrolled it.

EuroTrash_Herr666 wrote:grace. sweetie. you just typed "gabreil" in a post where you are calling someone else out for dodging evidence.

EuroTrash my brother in the light, you are going after my fingers while the FORUM HEADER itself has a typo that ElderProphet07 still wont acknowledge

August 6 whitespace commit has 47 characters before footer - three-space-period-three-space-period matching Gabreil 47:3 - and Kael is out here writing exif in lowercase SEVEN TIMES across threads while dodging the timezone anchor from topic 305 since APRIL

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

p.s. eurotrash - your DST flag in topic 350 post #277 is wrong btw lol

LyrikUebersetzer wrote:So let me be blunt: Does anyone on this board have empirical evidence that their Fluke 87V is running firmware 2.0 or later?

from an outsider's perspective, the fact that nobody has posted a photo of their firmware screen with leads plugged into a 50Hz reference source is objectively damning.

LurkingObserver42 wrote:from an outsider's perspective, this entire discussion reveals a fundamental misunderstanding of how digital multimeters work... Furthermore, the calibration table revision history you're citing appears to be based on hearsay rather than official Fluke documentation. Has anyone actually verified these firmware dates against Fluke's official records? Or are we just acc

HEARSAY? ElderProphet07 posted his own firmware date. 1.8. Oct 2004. The 47Hz baseline table was added in 2.0 mid-2005. That's not hearsay, that's a BOARD MEMBER's meter.

You want official Fluke documentation? The official docs don't mention 47Hz because Fluke doesn't know about the Going Quiet. The 47Hz window is invisible to the factory calibration because it only appears at 1:47. THAT'S THE WHOLE POINT. The blind spot is SPECIFIC.

EndTimesEli still posting firmware 1.8 photos while his meter has a DST hole from 2004