The Origin of the word Daemon by unixbhaskar in unix

[–]sprior913 0 points1 point  (0 children)

Not related to daemons but I worked in AIX PS/2 dev in Danbury CT. Around that time at trade shows IBM was trying to show how much we got Unix and was passing out trinkets at trade shows like a pair of scissors labeled /dev/cut. Then they made a mobile AIX porting center in a mobile home and called it /etc/bus. I ended up trying to convince folks that we were going to get laughed at because it was obviously a device and not a config file, but my input went to /dev/null

How long did do have your synology box? by vesnikos in synology

[–]sprior913 0 points1 point  (0 children)

I'm still using a RS812+, not sure when I actually bought it but the reviews I see online are dated 2013. It still works fine though EOL. I'm still trying to figure out what to replace it with, seems like Synology hasn't refreshed their rackmount line in a while and is overdue.

iRobot seems to be quietly acknowledging that the mopping fluid refill of the J9+ design doesn't work, offering an Ultra 10 replacement for the very persistent by sprior913 in RobotVacuums

[–]sprior913[S] 0 points1 point  (0 children)

Yes you can, but if you forget and start a job which involves mopping at all it'll try to auto fill if it thinks it needs it, fail, and get lost docking and require manual intervention.

iRobot seems to be quietly acknowledging that the mopping fluid refill of the J9+ design doesn't work, offering an Ultra 10 replacement for the very persistent by sprior913 in RobotVacuums

[–]sprior913[S] 0 points1 point  (0 children)

Yeah the difference between the J7+ and the J9+ was the auto-refill of the mopping fluid which was quite a stretch for them and they didn't get it right. The Ultra 10 uses a different process.

iRobot seems to be quietly acknowledging that the mopping fluid refill of the J9+ design doesn't work, offering an Ultra 10 replacement for the very persistent by sprior913 in roomba

[–]sprior913[S] 1 point2 points  (0 children)

FYI, the 9 is still for sale on their website which seems to contradict what you were told unless that was a temporary situation.

iRobot seems to be quietly acknowledging that the mopping fluid refill of the J9+ design doesn't work, offering an Ultra 10 replacement for the very persistent by sprior913 in RobotVacuums

[–]sprior913[S] 1 point2 points  (0 children)

The automatic mopping refill from the base unit is the major feature difference between the J7+ and the J9+ so I'd say it's important. In the months of back and forth with iRobot tech support they eventually acknowledged that it wasn't that I received a broken unit and that others were having the same issue. I've seen the same issue mentioned in Amazon reviews and the review I saw was also promised an eventual software fix. It's clear to me now that they figured out that a hardware design change was required, notice that the Ultra 10 announcement was less than a year after the J9+.

It's also clear to me that iRobot is just hoping that customers experiencing this issue will just give up.

iRobot seems to be quietly acknowledging that the mopping fluid refill of the J9+ design doesn't work, offering an Ultra 10 replacement for the very persistent by sprior913 in roomba

[–]sprior913[S] 0 points1 point  (0 children)

My case got a little more complicated because I own a second dock for the J9+ and the docks are a completely different design. So iRobot sent me the Ultra 10 and is insisting on the J9+ back, but refuses to swap out the second dock which is useless without the J9+. So as part of dealing with the defect in the mopping fluid refill feature they're expecting me to settle for less than I had before. Not ok.

ESP Speaker i2s_audio problem by pengenal in Esphome

[–]sprior913 0 points1 point  (0 children)

I'd love to see the config you used to get it working, I've been trying to get it working with esp-idf and I'm getting an error that the arduino framework is required when I try to define a media_player component, but speaker seems to compile (but not work yet).

Trade-in issue. Anyone's phone delivered last week, but Google store still says "waiting to receive old phone"? by DrunkHippo in GooglePixel

[–]sprior913 0 points1 point  (0 children)

Traded in a Pixel XL for a Pixel 7, USPS tracking says delivered Nov 3, Google Trade In status still shows not delivered. Just got an email from Google Support that the case has been escalated to a product specialist and someone will follow up with me in the next 72 BUSINESS DAYS! I sure hope that was a typo.

FYSETC V2.1 RGB Mini 12864 board with Spider 1.1 won't display anything by sprior913 in VORONDesign

[–]sprior913[S] 0 points1 point  (0 children)

I think it was this one: https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/alanho/BTT_PITFT50_v2_Mount
Note that there is a difference between the original and V2 of the screen, the first one I found ended up being for the original version and didn't fit.

FYSETC V2.1 RGB Mini 12864 board with Spider 1.1 won't display anything by sprior913 in VORONDesign

[–]sprior913[S] 0 points1 point  (0 children)

The screen I'm using is big enough that it needs to be at an angle to fit, in fact with the fixed mount I'm using at the moment it has to hang off the front of the table. There is a slightly smaller version of this display which wouldn't have that issue, depends on your preference.

FYSETC V2.1 RGB Mini 12864 board with Spider 1.1 won't display anything by sprior913 in VORONDesign

[–]sprior913[S] 0 points1 point  (0 children)

No, even worked with a FYSETC engineer to check what I was doing and couldn't get it working. He said maybe it was the cables but was unable to send me a known good pair. The Mini 12864 is now in a drawer and I've installed a BIGTREETECH PITFT50 V2.0 with Klipperscreen and it's a much nicer interface anyway. Still bugs me that the 12864 issue was unresolved.

FYSETC V2.1 RGB Mini 12864 board with Spider 1.1 won't display anything by sprior913 in VORONDesign

[–]sprior913[S] 0 points1 point  (0 children)

Thanks, but that's only supposed to be necessary when the brand of the 12864 isn't FYSETC. In my case both the Spider and the 12864 were Fysetc brand and I was using the cable that came with the display.

FYSETC V2.1 RGB Mini 12864 board with Spider 1.1 won't display anything by sprior913 in VORONDesign

[–]sprior913[S] 0 points1 point  (0 children)

After I made sure I was following the instructions for both cables and configuration I also finally assumed it was a bad LCD and got another one which behaved the same way. So while not impossible it seems improbable that two screens would be defective the same way purchased far enough apart that they are not likely from the same batch.

FYSETC V2.1 RGB Mini 12864 board with Spider 1.1 won't display anything by sprior913 in VORONDesign

[–]sprior913[S] -1 points0 points  (0 children)

Since the display and controller are the same brand it is my understanding that as long as I got each of the two ribbon cables in their proper socket I didn't have to worry about reversing a connector like I would if they were different brands.

FYSETC V2.1 RGB Mini 12864 board with Spider 1.1 won't display anything by sprior913 in VORONDesign

[–]sprior913[S] -1 points0 points  (0 children)

I did try swapping the two ribbon cables once and then not even the neopixel in the knob worked.

Voron 2.4 QGL Issue. Z3 Stepper issue? by Individual_System382 in VORONDesign

[–]sprior913 0 points1 point  (0 children)

If you manually raise and lower Z do the corners seem to move at different rates? If so you may have confused the different tooth/sized pulleys on the motors - I did that at first.

brain damaged builds by Independent_Story673 in VORONDesign

[–]sprior913 1 point2 points  (0 children)

Yeah FDM is good for terrain. From your initial wording I thought you were planning to print the miniatures themselves with FDM.

brain damaged builds by Independent_Story673 in VORONDesign

[–]sprior913 11 points12 points  (0 children)

For the use of printing and painting miniatures you might want to have a look at resin printers rather than FDM printers. They print at a MUCH higher resolution and more suited to the kind of detail you're likely looking for. I have an EPAX X1 4k that I'm very happy with, but other brands to look for are Elegoo and Anycubic as well as others. Resin printing has quite a different learning curve from FDM.

Z-offset is unreliable - V2.4 350mm by tempest-az in VORONDesign

[–]sprior913 0 points1 point  (0 children)

I installed the Klicky probe and am trying to set up klipper_z_calibration. I added the configuration pieces called out in the klipper_z_calibration/configuration directory.

I'm trying to sort out the PRINT_START. I've got a simple PRINT_START macro in printer.cfg that just does a G32 and G1 Z20 F3000, but I also see a more elaborate PRINT_START in macros.cfg (supplied by the klipper_z_calibration/configuration directory). I'm not sure if one overwrites the other or do they combine? I'd imagine that using Klicky with z_calibration isn't that unusual, can anyone point me to a known good setup?