Posts made by Ce72

@Notepad Hi, I built my HevORT 3 years ago this year. Yes, I have been using the WobbleX rings for over a year now. I have even upgraded to the experimental 2.6 (I think) version on the wiki, that I remodelled to suit my setup, I have added the pic so you can see what I mean, But I did this upgrade back in September along with going to AWD and everything has been working fine.

To be honest I have only had this issue start around Christmas when I had to strip the bedplate off to reapply the bed heater as the old adhesive had started to let go. I have done multiple P.I.D tunes to try and see if that eliminates the problem and I have been chasing my tail ever since.

@droftarts Hi Ian, thank you for your response, and also for the great links. After extensive trawling I also found a helpful video from MirageC pointing me in the same direction.

I'm using the E3D HemeraXS Revo extruder so there's not a lot of wiggle room for modding or testing. I have odered a new set of drive gears to see if that helps, the only other thing I can think of is to try and make an undriven idler for the tension arm. But hopefully it won't come to that.

Once again thank you for the input.

Hi Everyone
I’m looking for some help and suggestions to try and eliminate a Z banding like artifact on flat surfaces (shown in the pics). I’m running an AWD HevORT core XY with a Hemera XS Roto extruder on a Duet3D 6HC mainboard with a Pi5 SBC, on 3.6.0-beta.3 firmware.

To me it’s not mechanical as the 40mm tube pic shows no evidence of the banding.

What I have tried so far:
Bed heater P.I.D tune, Extruder P.I.D tune, Belt tension balanced, Extruder E-steps checked, Various PA values tried, Wall print speeds from 100-200mms And a few acceleration speeds 7000 – 10000 on outerwalls, all with no variation in frequency.

Any suggestion to what might be causing this or what else to try would be much appreciated.

Hi
I'm using the 6HC mainboard in SBC mode on 3.5.0-rc.1, and I have a Neopixel led strip with 31 LEDs connected to the LED header on the board. When I first power on the machine the LEDs all work fine. However after a short period of time or after running a print, only the first 10 LEDs respond to any commands and the others stay on what they were first set too. so far the only way I have found to clear the issue is to power cycle the whole machine, restarting the mainboard does nothing to help.

Is this a software bug or is there somthing I'm missing

@chrishamm Thank you for the suggestion. I used a spare SD card with a fresh full bullseye image, then installed the DSF software as per the link and unfortunately, I ended up back where I started with the dropdowns still not working. I guess it’s the same issues with working with the Bullseye OS. as everything was working perfectly with the Buster install. It’s not a big problem as the machine is still working great. It is only when I want to change materials, I then have to set the temperature remotely (I’m not a great fan of the onscreen keyboard) and ultimately as a work around I can easily create a couple macros to heat up and cooldown until Bullseye is fully compatible.

@chrishamm That's great, thank you for getting back to me, I was hoping that it might have been a quick fix. But I look forward to updates

@chrishamm I tried clearing the cache (Ctrl+Shift+R) a couple of times during the process above, sorry I should have put that in.
Normally I only use steps you linked to as an upgrade / downgrade path as my Linux knowledge is very limited. Regarding using the Bullseye image, I was fully aware that it was experimental (preview) image. But I needed the updated versions of Libcamera and PIcamera2 to be able to use the Pi camera V3 as a webcam on the machine. And because it was an experimental release on first use, I went through the commissioning process as if my machine was a new build and nurse maided it through the first couple of prints. and also the printer has been running for a couple of weeks before I raised this post just in case. But the dropdown issue is the only problems I have experienced.

Otherwise I would not have brought experimental problems to the forum.

Hi
Thank you both for your help.
It seems that my original post was slightly out, in that the upgrade from the initial boot had taken me up to the stable version 3.4.5 rather than the 3.5.0.beta3 I thought I was on.
However, moving on these are the steps I tried.

1. I downloaded the DWC beta3.zip and tried to install it through the systems page, but it was not recognised (I now know for the reason above)
2. Then I recreated the www file as per the documentation pages to install the beta3 package as a separate component to see if this helped but DWC still showed up as 3.4.5 (probably the same reason)
3. My next step as I was having no luck was to go up to the unstable release to see if a fresh update would resolve my issues. It was during this process that I realised which firmware I was actually working with as the update took me on to V3.5.0.beta3. All went well after the reboot and DWC was showing the right version beta3 However, the temperature dropdown is still not working, the button recognises the click as the button arrow changes direction but no temperature dropdown. (Machine-specific info still present and correct)
4. As a last attempt I tried going back onto the stable releases my thinking being I might have a broken link somewhere. This took me back to V3.4.5 But on reboot I had a software mismatch alarm on the Duet screen, this was due to DWC still being V3.5.0.beta3 so the downgrade process did not bring DWC with it.
   At this point I’m at a lose again, I have gone back to the unstable V3.5.0.beta to clear the alarm on boot so to keep the printer working. Is this an inherent problem with going onto the Bullseye release?

Hi All

I’m using the 6HC mainboard in SBC mode, and recently I had to upgrade the SBC firmware to the Raspbian Bullseye image. I’m using the DuetPi 2023-01-24 (Bullseye) image, I needed to do this so to get the full functionality of the Rpi V3 Camera.

I can appreciate this is somewhat an experimental image and I’m pleased to say that everything is working fine, except the issue of the temperature dropdowns in DWC not working, which makes thing a bit of a pain when trying to preheat the printer from the touchscreen.

This is what I have done so far:
From the initial boot, I have run the apt update / upgrade which has brought me up to the latest stable release 3.5.0-beta.3 and my DWC is version 3.4.5 and reading the documentation it shows the dropdowns are referenced from the information on the Settings/Machine-specific page and these are correct, from here I’m at a bit of a lose.

Any suggestions to help with this would be very much appreciated.

@chrishamm Thank you for your help, Reflashing with Bossa has got me back up and running

@chrishamm
Hi
I belive that I am running DuetPi as I have been running the printer in SBC mode from the start, everything has been working fine up untill today when I run the "sudo update" process which has worked fine in the past.

The diag LED is barly on lite. The update did fail at the firmware updating stage which makes sence, but I have been unsure how to reinstall.

With the "bosse" process do I need to disconect the Pi? also which firmware image would be best to load? I have been running on 3.4.4. Is it better to go older then reupdate through the Pi after

Thank you for the help in advance

I done a random update check on my machine today, just to find a new version had been released today. Everthing went fine upto updating the mainboard firmware which failed. and I now cannot connect please help? Errors below

i'm runnung a duet3 6HC mainboard in SBC mode with RPI 4B.connectin through VNC

things In have tried:
re-run update process = no help
power cycle re-run update process = no
I then tried to downgrade back using the processs described on "Duet Software Framework (DSF) on Raspberry Pi" page. this process failed at the Downgrade DSF: step with the following message in the terminal:

"pi@HevORT:~ $ sudo dpkg -i --force-depends ./reprapfirmware*.deb
(Reading database ... 103254 files and directories currently installed.)
Preparing to unpack .../reprapfirmware_3.4.5-1_all.deb ...
Unpacking reprapfirmware (3.4.5-1) over (3.4.5-1) ...
Setting up reprapfirmware (3.4.5-1) ...
[fatal] Failed to open IO device: Error 16. Cannot put line into event mode.
pi@HevORT:~ $ "

Also when I try to connect via DWC I get the following:

Please could someone advise me how to get back up and running

@ce72
I wired up the PWM to voltage converter as above, and found I needed the jumper to get an output. So I put the jumper in the 24v side and I was able to tune the voltage down to around 6.5v output, from this i added a "F" value on the M106 line of my config file to limit the output to the required 5v with full control.

I'm pleased to say all is now working great I will also order the required risistors and cap to try the other way, to make a cleaner install and not need the work around in the config.

@dc42 Sorry to be a pain but to clarify. and so that I fully understand, Am I right with these two options in sketch form:

OR

@dc42 Hi, I've got the 24v variant, so I could provide power straight from the PSU.

Regarding the wiring, I tried connecting:

6HC (out5) converter
pin1 (GND) GND on the 12-30V side
pin2 (VIN) 12-30V
pin3 (out5.tach) PWM +
pin4 (out5) PWM -

I had a multimeter across AO and ground on the output, (rather than connecting anything else) and had an output of 0 - 0.48V that varied with the "s" parameter.

VIN was 23.9V on the same multimeter

I hope this helps to find where I have gone wrong

@ce72 I have received my PWM to voltage converter and I'm have troubles connecting it and getting the right output. I have checked the port on the board with a pigtail and multimeter and I'm getting the right output from there as it is the same as the other ports which are now working.

Here is how I'm trying to connect the converter

port6
V_OUTLC1 red wire to 12-30V on the converter
OUT6(-) black wire to PWM- on the converter

yellow & blue going to the multimeter (leave other components out of the way)

I'm only getting 0.2v out

Please advise (I've managed to get the acceleromter working no problem, but I'm getting beaten by a fan )

@jay_s_uk oh fair enough, thank you for pointing that out, I will check the output before fully conecting them up.

I'll post back with the outcome when the convertor arrives

thank you again

@jay_s_uk so if I understand you correctly that would be

"out4" jumper in VFused
pin1 = GND:Ground
pin2 = VCC:DC 12V-30V
pin3 = PWM:Positive of PWM input signal
pin4 = GND:Negative of input signal

"fan control board"
VSR = VOUT:Output Voltage 0-10V
GND = GND:Output Voltage Ground
PG = Not connected

Is this is for the 24v version of the Cpap?

You also mentioned earlier about the frequency on the E3d fan? how do I determine this value and could this be the reason for it not working at the moment

Thank you for all your help it is very much appreciated, As I feel like I have been banging my head against a brick wall trying to work this out

@jay_s_uk That's fair enough. I have just ordered the one that you linked, The next question is could you tell me how I need to wire it in and configure it

@jay_s_uk
Thank you for pointing that out, the fun of google search same words wrong place

On the the off chance and please pardon my ignorance here, but I have got this with another air pump system, would it be what I need?

If not I will happily grab the one you linked to