Topics created by bug2k22

Thanks for all the suggestions, some really interesting designs.

I've been given a micro swiss ng extruder which takes e3d revo nozzles, I already have a printer running a hemera xs and have a few spare nozzles for that. It looks like it will be easy to mount with a simple adapter plate.
I don't know how this will perform compared to some of the newer 'exotic' extruders but it should be an improvement over the original setup. Hopefully it can handle flexible filaments too.

@bug2k22 said in Upgrade from 3.5.2 to 3.5.3, sbc mode, not connecting:

I think I'll perform any reprapfirmware updates first from the web interface

That will definitely result in issues. When using SBC mode you must use the Pi terminal to update. On the rare occasion when an update fails, that's when a usb reflash may be required, or if the firmware is still present but hasn't updated, you may send M997 to trigger a manual flash.

Ok, I've tried uploading the firmware bin file directly to the board and installed the update from there, this appears to have worked. I will run through some print tests and hopefully it's all working correctly now.

[edit]
Having run a few test prints at different layer heights, it seems the latest beta firmware 99% resolves the artifacts issue I was having with 3.5.3. There is still a very faint hint of artifacting in a few areas but not enough to be an issue for my prints.

I found another article on setting up the DSF software and found that there is a reference to gpiochip4 in the file /opt/dsf/conf/config.json, editing the value of of following line resolved the issue:

"GpioChipDevice": "/dev/gpiochip4",

Changing this to /dev/gpiochip0 and restarting resolved the issue and I can now access the web interface.

@bug2k22 Moved to firmware wishlist.

Ian

Typically in cases like this the cause is a physical/mechanical issue causing some unintended movement of the print head. Either some sag in the gantry, or rails being skewed or twisted to the XY plane. A small amount of tilt on the print head causes the probe offset and trigger height to change in relation to XY position so the map is distorted.

One way to check this is to switch the probe type to P0 which is manual probing and re-run G29 to create a map using the nozzle as the probe. It's slow to manually probe each point, but the resulting mesh should be accurate to the actual nozzle position.

@bug2k22

the output of 'M591 D0' above does show the min and max measured still between the original values.

Anything outside the defined range will not be reported but invoke an error instead. So it is perfectly fine to widen the tolerance. However, it might be helpful to tell us if this error occurs in the vicinity of noticeable retractions or in some other context - from a distance, we can only guess what happens.

@droftarts I've dismantled the filament monitor and it looked fine. I think I may have found the issue, I have about 20cm length of ptfe tubing to route the filament from the side of the frame in to the top of the monitor which sits on top of the bondtech bmg extruder which sits directly on top of an e3d v6 hotend. The tubing is a very shallow 15cm or so radius curve and it feels like there is very little if any resistance. I printed a couple more test prints with the tubing removed and just unrolling and feeding it manually and the prints competed successfully.
This is strange as I have other printers using more ptfe tubing to route the filament with no issues. I played with the tension on the extruder and it seemed to make no difference.
Hopefully this was not just an anomoly, I'll make up a new filament holder above the extruder which should fix the issue.

@bug2k22 Thanks!

@jay_s_uk Thanks, that's just what was needed. I had got caught up in the weeds of the wiki and never read the release notes for that release. I already had apparmor installed and configured, must have missed the 'apt install duetpimanagementplugin' bit.
This all looks to be working perfectly now, many thanks.

@bug2k22 The Duet3D images are based on the official RPi OS so it's definitely an easier choice. A few differences I can think of:

Different boot screen* Auto-setup of correct TfrRdy pin in DSF config (needed on RPi 5 only) Preinstalled packages from unstable package feed Auto-start of DWC in full-screen mode* A couple of extra preinstalled packages including required dependencies like AppArmor Only applies to GUI image

@bug2k22 said in Anycubic Kobra 2 Printhead pcb & z probe?:

If I do upgrade the print head with a 1LC is it possible to use the accelerometer on this for the x axis and another separate accelerometer on the print bed for the y axis?

Yes. Priod to the accelerometer being integrated into the toolboard itself you would have a separate board that you would attach to the appropriate axis for measurements and remove it afterwards.

@bug2k22 if you have a decent multimeter, you can measure the resistance of the bed to work out the current draw.

Ian

@oliof Thanks, most of the connections are obvious, I can probe out the cable from the print head to the board connector.
There are a couple of connections which I presume cannot be used, one to what looks to be a 'calibration' switch at the rear of the print bed and next to this an 'acc sensor'.

kobra2max_1.jpg

kobra2max_1b.jpg

kobra2max_2.jpg

kobra2max_3.jpg

kobra2max_4.jpg

@jay_s_uk It seems only moves in a positive direction are allowed. For example I can configure x -40 to 40 or y from -40 to 40 but not from 40 to -40.

It would be nice to be able to import a series of moves from an actual print or text file containing coordinates to move through.

@dc42 That seems to have worked fine, both the extruder thermocouple and the heated bed thermistor are working. I think the temperature readings are out, the bed shows ~31degC at idle whereas the extruder seems to show ~16degC which is probably about right for ambient.
I do think the extruder is under reading at working temps as printing at a reported 198 seems quite a bit higher than needed to print pla. I don't have a ir thermometer to check at the moment.