#garfield Logs

Nov 14 2023

03:00 AM polprog: meh, could have stayed up longer
03:12 AM polprog: slow day at work today
06:18 AM polprog: warning: ignoring return value of ‘int system(const char*)’, declared with attribute warn_unused_result [-Wunused-result] 67 | system("shutdown -h 0");
06:18 AM polprog: lol
06:19 AM polprog: etags -R --language-force=C++
06:20 AM polprog: language force was why it was not working
06:20 AM polprog: or rather it was necesary to make it work
06:20 AM polprog: coworker uses .h for Cpp headers...
06:20 AM polprog: etags tries to read them as C headers...
08:22 AM rue_mohr: http://durealeyes.com/robot.html
12:23 PM polprog: that one which writes over it's program disc is quite literally a turing machine
12:23 PM polprog: a turning machine too
08:00 PM rue_shop2: 205-210
08:01 PM rue_shop2: polprog, how was AI class ... yesterday?
09:27 PM aandrew: hey rue_mohr
09:27 PM aandrew: I want to make a serial port glitcher
09:27 PM aandrew: e.g. relay which shorts serial line to gnd randomly
09:29 PM aandrew: I was thinking of using a shift reg configured as an lfsr (serial in, parallel out, couple xor gates for feedback) and then picking a q as the output and using that to trigger a monostable which energizes the relay for a short pulse.
09:29 PM aandrew: it's retriggerable so the monostable time determines the minimum glitch time and if the outut of the lfsr is a '1' for a while then the glitch becomes longer
09:31 PM aandrew: what do you think? am I overthinking?
09:32 PM aandrew: actually if I use xnor I don't have to worry about accidentally shifting in too many zeroes I don't think
09:32 PM aandrew: HC264 and a couple 1G97s would make this small and sort of configurable even
09:35 PM aandrew: 597 is another
10:02 PM aandrew: actually I could use the output of one LFSR to be the clock of a second LFSR and the output of the second would drive the monostable to generate glitches
11:28 PM aandrew: https://ibb.co/TH4ht7Z
11:28 PM aandrew: works decently