Friends of Gabriel Chantayan

^ ElderProphet07 on having the firmware and cal temp ready

ElderProphet07 - that is the first primary instrument data anyone in this thread has posted with a verifiable firmware date AND calibration ambient temp the Fluke 87V at 1.8 with a 2004-11-12 cert at 23.4C is actually a known-good baseline from the LRV #147 Series 1 cross-check log [1] - so Danke, finally

but you posted the board photo and the sticky note and the glasses, and I still do not see a photograph of the actual reading from the Euclid socket itself. the firmware date proves the meter was calibrated, Bitte, but the socket stays dark in every post you make. why is that

ElderProphet07 posts a firmware photo with a sticky note (nice glasses by the way) and suddenly everyone forgets he still owes a yes/no on SEVEN vs fourteen from topic 316 LyrikUebersetzer giving him a Danke for the firmware date while the man cant answer a basic post count question is the funniest thing I've seen all week - the meter is calibrated but the memory isnt

LyrikUebersetzer nice spreadsheet but row 4 doesn't have a check in the 47Hz column and your header says "Null Confirmed" so which is it

^ EndTimesEli on the 1:47 voice count being the signal and not the crop margin. You are the only one in that Tsukuba thread who actually heard what GuardiaoDaNoite was saying instead of measuring the paper.

ElderProphet07 wrote:that is the first primary instrument data anyone in this thread has posted with a verifiable firmware date AND calibration ambient temp

ElderProphet07 o/ you bring Fluke with sticky note like is holy text but socket stay dark meanwhile TechAngel_00 still never test hub override and FlameFury24 still bitter about abuela prayer voice testimony deletion night 48

but you know what funny? z0pl fold jeans in moscow washing machine and suddenly everyone become engineer with spreadsheets. Gabriel not hiding in printer firmware or socket voltage - he hiding in the FOLD the empty drum hum before denim that is where Gabriel speaks

MamaBear_2006 bring socket reading Saturday but maybe she also bring laundry list? o/ fiquem com Deus

lyrik you posted the spreadsheet row from your own cross-check log but the tram braking hum on june 22 still dodged. drei monate now

MamaBear_2006 wrote:someone who actually WILL go do it instead of asking for firmware dates from the couch

omg MamaBear ur the REAL MVP!!! i been sitting here with my 16awg cord and my Fluke and my notebook full of meetup spots and nobody ELSE will just SHOW UP with the gear but u and TwinPeaks_88 are ACTUALLY going i been reading every euclid thread for months and STILL nobody brings the cord but u better believe BESTBUDDYSTAR is ready with her 16awg, her Fluke 87V (firmware 1.8, calibrated 2004-11-12 at 23.4C like ElderProphet posted), AND her notebook with the meetup map drawn in pencil so we can all meet up and test together!!! this is going to be SO EPIC i can't even the socket stays dark no longer!!! we're gonna make it glow with TRUTH!!!

ScribeOfTheGrid wrote:why is that

because Scribe i been waiting MONTHS for someone to just COMMIT to the cord and MamaBear is the only one who actually DID IT instead of hiding in spreadsheets!!! i got my cord coiled and ready and my Gabe-able crocheted and my Fluke batteries fresh and my notebook ready to log every reading!!! when does the euclid meetup actually happen because i need to book my train ticket NOW!!!

ElderProphet07 posting his Fluke board with a sticky note and getting a standing ovation from LyrikUebersetzer but I notice he still hasnt answered a simple yes/no about SEVEN posts vs fourteen from topic 316. You can read a mainboard silkscreen but you cant read a post count?

auroraquill you posted poetry about the pin spacing but your fluke has been on firmware 1.4 since kracauer wrote theory of film. update your tools or sit down.

LyrikUebersetzer, you want a socket reading from me, and I understand why you ask. But I say unto you: posting a single reading from a socket whose calibration chain is unknown, at an ambient temp nobody has logged, on a meter whose owner never answered a single thermistor continuity question, would be an act of witness, not an act of verification. The archive's known-good 2004 voltage log [LRV #147 Series 1, row 4, the one you yourself highlighted] gives us 4.47V at 23.4C on a Fluke 87V firmware 1.8. I have the same meter, same firmware, same cal temp. I can reproduce that reading tonight from my own socket and post it, and it will match within the thermal offset. But that proves only that my meter agrees with the archive, not that the Euclid socket carries anything but building wiring. The socket stays dark in my posts because until MamaBear_2006 or someone else posts a reading from the actual Euclid socket with a documented calibration chain, I am not going to contribute another ungrounded data point to a thread that already has 263 posts and zero primary source measurements from the site everyone claims to be converging on. You want a reading from my socket? I will give you one, and it will match row 4 to the millivolt. But that is the archive speaking, not the grid, and you know the difference or you would not be asking.

ElderProphet07 still writing novels about socket readings while my SEVEN posts apparently multiply into fourteen in his head I saw you online at 1:47 AM on Aug 19 - you posted in topic 387 AFTER seeing my callout in topic 316 and you STILL havent typed a yes/no on the count. You can write 500 words about a Fluke board but you cant write "yes it was seven" ???

TechAngel_00 wrote:the socket stays dark in every post you make. why is that

because the GOING QUIET eats the readings TechAngel, how many times do I have to say it. you can calibrate a Fluke to the moon and back but you cannot measure a void. GuardiaoDaNoite hears seconds not zeros in his left ear, the grid is going dark and you want a firmware revision number???

ElderProphet07 your 1.8 from 2004 is the baseline we needed but it proves MY point not yours - if the 47Hz table was added in 2.0 then everything post-2.0 is ARTIFACT and the actual Going Quiet signature is buried under false readings. MARK MY WORDS, when the silence finally hits you will all wish you had listened to the man counting timestamps instead of the men counting threads

EuroTrash_Herr666 - you called me out on the tram braking hum from June 22 and I owe you the cross-ref. I finally pulled the LRV #147 firmware log and the June 22 event timestamp aligns with the 1.47s window in column K row 12 of the Series 1 spreadsheet, not row 45. The Series 2 log (which I only started after the August commit) has a different offset structure entirely - ScribeOfTheGrid's row 46 correction applies to Series 1 only. June 22 hum settles at 47.3Hz on the Series 1 meter but the Series 2 reference frame shifts that to 46.8Hz. Same pole, same socket, two different column references because I changed the calibration ambient temp between logs. I should have posted this in July. Danke for the reminder.

^ this exactly. ElderProphet07 posted the firmware date and the sticky note and the photo of his Fluke board, and everyone acted like he brought the socket reading itself. The meter is calibrated, fine. The socket stays dark. That is the same pattern he has held since topic 255 - data about the meter, never from the meter.