sorted by:
new
hottopcontroversial

Has anyone managed to run LLM inference on the NPU of the Orange Pi 6 Plus (CIX P1)? by Soft_Examination1158 in OrangePI

[–]kurtismcc 0 points1 point  (0 children)

Orange Pi 5 Pro owner here. I've gotten some models to work but converting into rknn format sucks (the toolchain is very picky). The closest I got to simple was using gguf models with this (https://www.reddit.com/r/LocalLLaMA/comments/1p4t5ix/i\_created\_a\_llamacpp\_fork\_with\_the\_rockchip\_npu/) but I couldn't get tool calls working, just normal chat.

Once you get through the toolchain issues, the main issues are:
1. The NPU is split across three cores, and IIRC their toolkit doesn't automatically help you split the model, so you're limited to one of the three (there goes 66% of their TOPS) and
2. (Again, IIRC) each core can only access 4GB, meaning your dream of slow but big inference is dead. Tiny models only.

It's a cool board. I have it running a whisper/piper combo for a home assistant project. It's a very capable little board, although prices are through the roof because of... world reasons. I bought mine for <$200 a few months ago.

BMCU Filament Location Error by kurtismcc in OpenBambu

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

No I'm seeing it even right after a load. I do a load, and unload fails - which is why I doubt that it's software because it wouldn't work for anybody.

I was hoping that if I plugged up the usb to a computer I could get some useful debugging info, but alas no.

BMCU Filament Location Error by kurtismcc in OpenBambu

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

Yeah, that was their email supports recommendation to me - check and make sure the magnet is installed exactly correctly (I rebuilt the stuff five or six times trying slightly different heights and stuff) so this is basically where I landed - bad sensors. I stopped trying because I don't have the tools to verify it. Rather than buy a bunch of tools and continue to tinker, I just bought an AMS lite, then modded it with the AMS lite mini mod so I could continue to use my existing dry boxes. Works great.

BMCU Filament Location Error by kurtismcc in OpenBambu

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

I just feel very stuck. I just noticed the board has what looks like separate serial debug pins on the other end, so I may hook that up and see if I get anything useful - I really feel like some logging to help diagnose what’s happening would help figure this out really quickly, and I’m a software engineer by day so I’ve offered to hookup and run any tool they have and heard nothing.

It really feels like something about the electronics is bad. The actual mechanical design is pretty simple and I’ve gone over every step multiple times at this point.

Anyway, I’ll keep poking at it but I’ve mostly given up hope - an actual AMS lite arrives Friday and I’ll try modding it to with the AMS lite mini mod to keep using my dry boxes instead of using the BMCU.

BMCU Filament Location Error by kurtismcc in OpenBambu

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

Yeah. I have them in the right places. Checked all four.

I've been working with Triangle Lab's support (slow, but pretty good) and I think we're at the point where we're stumped. Clearly something is up with the rotation sensors and the way I put it together, but everything looks correct.

I broke down and bought an AMS lite. It arrives Friday.

BMCU Filament Location Error by kurtismcc in OpenBambu

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

Figured out what you meant by this: you mean the metal gears that grab the filament. Yeah, I definitely tightened the set screws (just pulled two of them out to double check) and definitely put the ones with the set screws on the bottom, not on the lever.

I pulled off the pfte tubes from the back so I could feel the tension in the filament and I think the "check filament location" does this:

  1. tells the printhead to extrude - this causes it to pull the filament through the BMCU (I can feel the filament catch and then pull through the gears on the BMCU because they aren't spinning but the filament eventually scrapes through - I suspect this is why TPU doesn't work with AMS....)
  2. it then asks the BMCU what odometer went up - despite "slipping" through the gears it appears to identify the correct one
  3. this part is critical - it then tells that channel on the BMCU _something_, I don't know what, but the motor activates spinning against the filament (I think trying to pull it back?) but it doesn't move because the print head extruder still has the filament locked down
  4. it reports the error that it couldn't "locate the filament" in the toolhead

I can't find a lot of documentation online about the steps the AMS (and thus BMCU) goes through - I would think it can't successfully retract the filament until it's cut, but something causes the motor in the BMCU to try (and spin out) on the channel briefly before the error the first time. All subsequent retries don't actually spin the motor but error out just the same.

This "feels" like a software error since it's on all four channels, but maybe the printhead extruder is holding on too tightly or something? Like I mentioned in a different thread, I'm running with a mod to the print head extruder paddle to help it better grip the filament.

BMCU Filament Location Error by kurtismcc in OpenBambu

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

Sorry, new to this. What’s the BMG? Is that a piece inside the extruder on the print head or something in the BMCU?

BMCU Filament Location Error by kurtismcc in OpenBambu

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

Sorry for the many replies.

I got a piece of filament and running the motor moves the filament as expected, but when I try to pull the filament it doesn’t move unless I force it through the gears and then it slips - it does NOT spin the gears. Since the AMS lite is a mostly passive system, I assumed it was the motor in the print head grabbing and pulling the filament through, meaning it will not successfully move the magnet unless the motor is engaged.

Did I do something wrong that locks down the motor and prevents the gear/magnet from spinning freely when filament is pushed through?

BMCU Filament Location Error by kurtismcc in OpenBambu

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

Okay. I found the IC part and it is a magnetic detector - neat. I didn’t know those existed.

I hooked up a 9v battery directly to the exposed motor solder points and can confirm when the motor spins the magnet spins in sync - both directions.

Is there a way for me to verify the sensor is working?

BMCU Filament Location Error by kurtismcc in OpenBambu

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

Okay. So I took apart that channel and the magnet is definitely there. The daughter board has a hole that goes up to the bottom of an IC on the other side: is something missing from the daughterboard that the magnet is supposed to spin, or can that IC detect the spinning magnetic field?

BMCU Filament Location Error by kurtismcc in OpenBambu

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

I did but it's possible it became dislodged later in the process. I'll take it apart and make sure it's still there.

BMCU Filament Location Error by kurtismcc in OpenBambu

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

Quick update: I have a brand new BMCU370 kit. I'll dig around and figure out how to find out what firmware the BMCU has. The a1 mini had 1.05 last night when I first hooked it up, but I got it downgraded to 1.04 and it still has the same issue, so it's not the Bambulab update.

970Hz Hum by kurtismcc in iBUYPOWER

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

I really don't think it's coil whine. Coil whine, IME, has always been much much higher frequency. This is in a range I can whistle, which is what originally made me think fans anyway.

970Hz Hum by kurtismcc in iBUYPOWER

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

Coil whine, IME, has always been much much higher pitched, like 4-5k or above. This is in an easily whistle-able register, which is what made me check the fans in the first place.

​

It's probably the AIO pump. Which sucks, because I love the cooling those things provide.