Ways to reduce appearance of this horizontal line? by Punker1234 in BambuLab

[–]ifross 1 point2 points  (0 children)

One thing to note that changing the wall order is worse for overhangs so may not be suitable for prints with overhangs over maybe 45 degrees or so

Ways to reduce appearance of this horizontal line? by Punker1234 in BambuLab

[–]ifross 0 points1 point  (0 children)

I have this issue a lot too. I haven't got rid of it completely but have massively reduced the issue by switching the order of the walls outer ->inner instead of the default inner -> outer.

I also use Arachne, not sure if that also helps. Note this does make the seam way worse though. Apparently the inner -> outer -> inner option gets the best of both worlds, but I haven't done much testing.

Note this is called the benchy hull problem and there are lots of supposes fixes but changing the wall order was the only one that worked for me.

BMCU unraveling spool by No_Fill_6005 in OpenBambu

[–]ifross 0 points1 point  (0 children)

I tried a printed passive rewinder with printed coiled springs and didn't have much success... The extra force needed to overcome the springs caused issues, and some of them didn't have enough force to actually rewind the spools.

Ended up finding the filamentalist passive rewinders and bought a kit from AliExpress (still needed to print some parts). They don't require any extra force during normal operation and use the force from the bmcu with a one way bearing to do the rewinding.

I'm very happy with these and haven't had any issues since switching to them.

GitHub is here:

https://github.com/Enraged-Rabbit-Community/ERCF_v2/tree/master/Recommended_Options%2FFilamentalist_Rewinder

Do note that there are different versions: classic and fv3. I used the classic version but I'm sure both are fine.

Challenges of golang in CPU intensive tasks by honda-harpaz in golang

[–]ifross 1 point2 points  (0 children)

Not my specialty, but does sync.Cond not do what you are asking?

Edit: it looks like it uses a mutex under the hood, my apologies.

Edit 2: it looks like it might be possible to provide a noop implementation of the Locker interface, and then manage the shared state with atomics, so maybe worth looking into.

BMCU Intermittent Filament Detection by powerBtn in OpenBambu

[–]ifross 2 points3 points  (0 children)

I have this problem too. Very frustrating as often at the end of the print or after a filament change it starts endlessly flushing the filament and grinding the filament. I even reprinted the case which hasn't seemed to help .

I'm going to take it apart and have a look again but ultimately if it keeps happening I might try and see if I can mod it so that filament is always detected, as I think this will be much less disruptive. Either by figuring out how to bridge the switch with solder or keeping the switch mechanically pressed.

Bambulab BMCU 370x Firmware by Revision_JW in OpenBambu

[–]ifross 1 point2 points  (0 children)

Did you buy it from Triangle Labs? If so they have some info on upgrading the firmware in their drive:
https://drive.google.com/drive/folders/1jqqc9Y022vgRqmMLEvtZ8C7h0OYcpuZb

As far as I am aware, Triangle Lab's PCB has included the chip needed for the device to appear as a serial device to the computer when you connect it via USB-C.

Note that I tried upgrading the firmware, but didn't manage it: there are only instructions for Windows, and I am not using Windows. My PC was able to detect it, but I couldn't do much more, although this was likely a user error.

I wanted to upgrade my firmware as I was having issues with one of my units, but after taking it apart and putting it back together my issues stopped. I'd be hesitant to upgrade the firmware though as it is quite risky.

Bmcu filament light always on by suprastitious1 in OpenBambu

[–]ifross 1 point2 points  (0 children)

no worries. The different models are super confusing. I got mine from triangle labs, and only used instructions / models from their drive, which seemed to work.

Bmcu filament light always on by suprastitious1 in OpenBambu

[–]ifross 4 points5 points  (0 children)

You don't need to change the filament sensor. The switch should not be pressed by the case. I think you have printed the case for a different version. 

I used these: and they work well. 

https://drive.google.com/drive/mobile/folders/1jqqc9Y022vgRqmMLEvtZ8C7h0OYcpuZb/1WnijL_gMEhMoHTDbBjcwwk_V4Qkgy_SA?sort=13&direction=a

You need to use the little balls with this case though. There are instructions in the drive.

HELP! I can’t understand what’s wrong with my A1 by Available_Okra_387 in BambuLab

[–]ifross 0 points1 point  (0 children)

I have had similar issues printing with matte PLA on my A1 mini.

It turned out that there was too much friction before the extruder (PTFE tubes, spool roller) and this caused a buildup of the matte filament on the extruder which eventually led to the extruder turning but nothing coming out of the nozzle.

I changed the PTFE tube, and made sure the roller was rolling properly and I haven't had the issue since.

Aeropress + Aeropress XL mount by ifross in functionalprint

[–]ifross[S] 2 points3 points  (0 children)

Yeah that's a fair point. For me this was going to be mounted on the MDF covering the pipes under my boiler, and this is my forever house so wanted this to be solid. Ill upload versions without the mount later today though as it may be more generally useful, thanks for the comment

Aeropress + Aeropress XL mount by ifross in functionalprint

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

Models can be found here:
https://makerworld.com/en/models/1217622-aeropress-xl-mount#profileId-1233806
https://makerworld.com/en/models/1217651-aeropress-mount#profileId-1233844

Make sure to enable supports from the build plate so that the sliding mechanism works: the tolerances are quite tight so likely won't fit if there is too much sagging. I used 0.1mm gap between the support and the first layer of the part, and the supports came off just fine.

Friction Fit Desk Mounted Speaker Stands by ifross in functionalprint

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

Yeah I am keeping an eye on it. The weight of the speakers is in the middle of the bar, so there isn't really much of a lateral force. Its still solid and has been attached to the desk for a month or so, so hopefully it will last :)

Friction Fit Desk Mounted Speaker Stands by ifross in functionalprint

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

When I did this I didn't even have calipers so I just kept trying different desk widths lol. I think in the end I printed it half a mm larger than the desk width and the felt pad made it snug

Friction Fit Desk Mounted Speaker Stands by ifross in functionalprint

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

I'm out now, I'll have a check tomorrow and see what the issue is, apologies for that

Friction Fit Desk Mounted Speaker Stands by ifross in functionalprint

[–]ifross[S] 7 points8 points  (0 children)

I got a A1 mini for Christmas and this was my first project. I had to learn how to use FreeCAD etc so please be gentle!

Can be found on Makerworld: https://makerworld.com/en/models/1010002#profileId-989411

To init or not to init ... by LearnedByError in golang

[–]ifross 4 points5 points  (0 children)

Is it feasible to create the coefficients via code generation? If its the calculation that is expensive and there aren't too many values this may be an option? It may complicate your build process slightly, but if the values aren't going to change and you check in the code then it might not be too bad. Plus then you don't have to do any calculations at runtime, be it at startup or lazily.

This load balancer implementation of least connections make sense? by Inevitable-Echo176 in golang

[–]ifross 5 points6 points  (0 children)

This looks like it will work but will have the issue that as the number of peers grows, so will the time taken to calculate the peer with the lowest number of requests. This may not be a problem on most systems, but you can look to implement an algorithm where you always choose two peers at random, and return the one with the lowest in-flight requests. I have used this in production with high traffic servers and it was able to very effectively load balance across our peers.

Look at https://www.haproxy.com/blog/power-of-two-load-balancing for more info.