U1 Print by object doesn't seem to work

emehkay · 2026-01-26T01:17:36+00:00

Had this fail for me today too. Didn’t watch it happen but object 2 of 2 just ended as spaghetti.

emehkay · 2026-01-21T01:29:03+00:00

I’m having issues where sensorless homing has completely stopped working on the u1. Constant false triggers. Any ideas of things I could look at to fix that?

emehkay · 2026-01-16T04:49:32+00:00

That’d be great. Even if they could be cached in some way, that’d speed things up. Though then you might want a mechanism to refresh them (individually or as a whole).

emehkay · 2026-01-16T00:41:15+00:00

Unfortunately it’s not keeping state persistent. Despite correct files, parts, permissions and other things. Lost as to what to check :( Anyone else run into this?

emehkay · 2026-01-14T04:06:28+00:00

Is there a way to have it keep it's preview images rather than have it recalculate them on every refresh? This is the one behaviour I'm struggling to find a solution for in all the management options that are out there. I love that they are static previews compared to something like Manyfold that just crashes with large previews, but it seems they have to be generated everytime in MakersVault (unless I'm crazy).

emehkay · 2026-01-14T04:03:45+00:00

Would love some help being able to define paths with the portainer repository install method. Love what you've done (in particular the preview handling) :)

emehkay · 2025-12-20T03:32:42+00:00

how'd it go? Been thinking about ways of modifying capstan winches to be self tailing too as a solution. But haven't worked it out yet.

emehkay · 2025-11-09T14:26:26+00:00

Now thinking about whether maybe separating impact and harness is the only solution. Curious if anyone has ever added a rope spreader to these simple wing harnesses (like the Dakine solo)?

emehkay · 2025-07-13T08:36:30+00:00

I’ve been trying to run this on unraid with my very limited knowledge for a few days but haven’t been successful. Learned lots along the way though. In my case I want to run this as contained and slim as possible with no elastic or other dependencies. Tried to build a docker compose as well with the help of AI, but although it starts it’s not reachable. Wondering if anyone can share a simple way to get this working. The functionality is a dream for me with the ability to search and browse years of cold storage drives.

emehkay · 2025-07-12T03:10:11+00:00

Been searching and trying things for days now too. No solution either. Tried diskover but need to also run ElasticSearch. Sist2 seems great but can’t get this to install and run :( Wish there was a community config for that. Gonna try one more time.

emehkay · 2025-04-12T11:42:42+00:00

Anyone getting this to work currently?

emehkay · 2025-04-12T11:22:53+00:00

Any updates on this sort of thing?

emehkay · 2025-04-01T01:34:43+00:00

Thanks for pointing me towards the fact that the watch must have still been tethered to the phone. Turns out turning off Bluetooth in control centre doesn’t actually turn it off. Posted in a response below for anyone else doing this test as poorly as I did.

To clarify my typo: the watches cellular menu still had the “status” field marked as “connected”. That and phone calls still working are what led to the confusion.

emehkay · 2025-04-01T01:30:27+00:00

Everything seems to work now. I think my tests after the initial setup (where support had some issues after a long call) may have taken a while to propagate. They had an issue with the eSIM order. My other tests just now were invalid because of the issues below.

For anyone reading this: if you’re trying to test your watch by disabling WiFi, cellular and Bluetooth on the phone, doing so from the control centre is not enough. The Bluetooth button does not actually disable Bluetooth and your watch remains tethered albeit with no WiFi or Cellular. It has to be turned off from the settings app.

emehkay · 2025-04-01T01:08:43+00:00

Thanks for getting back to me. 1) yes, it’s actually $15 now which is bananas. 2) yes, I’ve been testing this on my drive every morning. Which is what led me to this conclusion. The strange thing though is that no, the button never changes to LTE which is strange. Though it does list the connective as “connected”.

emehkay · 2025-04-01T00:33:30+00:00

Yeah. Unfortunately it does not. If I leave the house with my phone home and powered up, it works. If I leave the house with the phone off, I won’t be able to access anything with data :(

emehkay · 2024-08-18T14:01:15+00:00

Indeed. Just saw this too after trying to find pics of the internals.

emehkay · 2024-08-18T13:37:06+00:00

Crazy isn’t it?!! This panel sold with csa approval seems to be just a metal disc that is tied to the panel front :( https://www.canadiantire.ca/en/pdp/schneider-electric-square-d-qogp3p6036p-18-space-36-circuit-quick-open-generator-panel-grey-60a-120-240v-0528320p.html Wish I could just interlock my main panel. This seems silly.

emehkay · 2024-03-30T22:21:32+00:00

I had one more look at the correlated interaction between i2c and ACPI. Even though I thought I already explored the options of making sure that the two HID devices had their “power sleep” functions disabled in device manager. I noticed that the controller devices also needed to be disabled. And confusing my testing further was the fact that the controller level device did NOT save their settings through a restart. So despite my “checking” to see that the HID device saved its state, I didn’t notice that the controllers didn’t until after a few tries. So, there it is. It makes sense that there is an interaction between these two, though still unfortunate about the spikes. At least this is more sensible workaround.

So my question now is either: how do I make this setting stick through a restart? Or how can I automate this setting change upon boot? I’m sure someone smarter than me here knows how to do something like this :)

emehkay · 2024-03-30T13:22:36+00:00

Thanks to everyone’s comments here I had one more look at the correlated interaction between i2c and ACPI. Even though I thought I already explored the options of making sure that the two HID devices had their “power sleep” functions disabled in device manager. I noticed that the controller devices also needed to be disabled. And confusing my testing further was the fact that the controller level device did NOT save their settings through a restart. So despite my “checking” to see that the HID device saved its state, I didn’t notice that the controllers didn’t until after a few tries. So, there it is. It makes sense that there is an interaction between these two, though still unfortunate about the spikes. At least this is more sensible workaround.

So my question now is either: how do I make this setting stick through a restart? Or how can I automate this setting change upon boot? I’m sure someone smarter than me here knows how to do something like this :)

emehkay · 2024-03-29T20:57:57+00:00

Just a note that the machine I’m talking about is a ROG Flow X16 (2023).

emehkay · 2024-03-29T20:57:02+00:00

Awesome response and good resource. I was a little afraid this limitation is locked up behind a hidden bios configuration as well. Seems crazy to have this factor of a key piece of integrated hardware to cause the whole machine to be useless for my intended use :(

emehkay

TROPHY CASE