@jay_s_uk just found the issue. the connector bringing power to the hotend is slightly melted. I wiggle it and see the graph get corrected. my god, the simple things, huh?

@jay_s_uk said in 12864 Display Unresponsive on Preheat Page 3.3b2:

@leckietech Theres a dropdown menu top left in system to switch to the menu/display files

Ah, got it. Thanks, heres a photo for anyone stuck in the future:

@dc42 YES! M150 finally controls some 2811 LEDs on my Wifi2! Thank you for this!

@bearer I'm confident a static discharge strap would have saved the board in a passive operation as routine as swapping out a bowden tube. But now that I've been here, I will certainly take more care next time and clip a ground cable to my cutters or make sure there is no place for the discharge to arc to. Live and learn!

@jadonm did you ever figure it out? Ive got 2 machines on my bench testing the Fysetc 12864 display and Im seeing this issue only within the preheat menu. The text file looks ok and nothing seems out of the ordinary. its doing it on a duet3 mini and a duet 2. Both have the same symptom that can be cleared by resetting the board. Ill probably go in and delete one function at a time to see what is triggering this to happen.

I print tonnes of PETG and something that I realized the hard way early on is like pla and abs, not all petg's are made equally. Some print super nice with basic settings and some need excessive work in my experience. But in all cases, I've never had peeling problems printing on glass or aluminum beds with a piece of Kapton tape. You can usually get pretty high mileage out of it too if you get a quality tape. I definitely do not recommend printing directly on glass. Youll have lifting.. more lifting and all of a sudden like DC42 says, its sticks and sticks too well. I've taken chunks out of glass beds! Youll need to remove it by heating your bed to something high like 115c and destroy your part to get it off the bed without chipping the glass.

And for warping, I don't get any of that printing inside a fully enclosed build chamber where the ambient temp is around 45 with a 85c bed temp.

@jay_s_uk ok this was very helpful thank you. I added the daemon.g file to my card with the code, hope I can catch this thing.. I'm about 3 hours into a print now and just noticing some ripple in the graph that wasn't there about 30 mins ago. it would appear there is a pattern which to me, indicates there is a position the printer gets into that is causing this.

@dc42 I tried every combination of this, still no go. Jumped over to the simplified forums, seems it cant be done.

@owend said in Conditional Code For daemon.g:

About the only way I can think of achieving what you want might be to use M559 or M560 to upload the file.

Thanks for the response. I did look into this, we load our files from the desktop, our phones, ipads, all kinds of stuff and we have thousands of files so loading the file by Gcode command or scrips might not be the way. I did however come up with another way to solve half the problem, at least.

I've made a system file: printBEGIN.g
We use Simplify3d - in the post-processing window Im using the following script

{REPLACE "G90" "G90 ; This is a trigger in post for M98 printBEGIN\nM98 P"printBEGIN.g" "}

G90 is the first command of the start of the print and there is only one for the entire slice file. This will point to M98 P"printBEGIN" which the very first line of that file starts with

M291 S3 R"Ready to run file?" P{job.file.fileName}

This will at least halt the printer and display the file via the 12864 screen on the printer itself as well as any DWC device running. The only issue is: S3D doesn't like the command with quotations in it.

The post command:
{REPLACE "G90" "G90 ; This is a trigger in post for M98 printBEGIN\nM98 P"printBEGIN.g" "}

Gcode output:

G90 ; This is a trigger in post for M98 printBEGIN
M98 P

The post-processor skips over the "printBEGIN" portion in quotes.
Any ideas?

@o_lampe I think I can do it with some external triggers, maybe an arduino too just to handle the logic, yes. It would just be so much nicer to do it with the onboard can.

@javajoeuk said in Can Duet3's talk to each other over CAN?:

can you not use a duet 3 and then use duet 3 expansion boards after that then you could have 8 of them chained together , that might solve the problem

How would you use one mainboard to run 3 individual files regardless of how many expansion boards are running?

@dc42 I have a concept for a printer that I believe has never been done before and our farm will benefit a lot from it. It requires to have 3 individual boards because my concept is actually 3 printers stacked high sharing one z axis rail as a spine and the beds can migrate print areas. Our racks here go to the 8.5' ceiling with printers so clearing the 2 top printers is a real pain with the step stool. With a single z rail, I can have the top beds lower into the bottom build volume upon completing jobs. Viceversa for the printers on the floor. The other benefit is that you can lower all the beds and run the top printer as an ultra-tall build volume if we ever needed to. Hope the ability gets implemented, I've already started the prototype!

Can Duet3's talk to each other over CAN? If multiple Duet3 boards are all connected parallel over CAN, could one printer call an M98 sub-program on another?

@owend said in Conditional Code For daemon.g:

@leckietech

job.layer will be null at the start of the print.

You need to allow for that

Ah! Makes so much sense, I knew it was going to be simple!

On another note, daemon.g by default only runs once every 10 seconds,
If you need to sample faster than that then you need to set up a loop within daemon.g

Thank you for the tip!
Next up, Ive looked throughout the Object Model and cant seem to find a node that keeps track of files being uploaded. We have so many printers here and so may operators, often we have someone run a print from an sd card while someone else is uploading. So logical solution: Change the LCD color and put a message on the screen "uploading file". I will also need a way to display on the screen if the file failed to upload - as this is something that happens here all the time.
Any suggestions on how to achieve this?

I have a few tasks for daemon.g if I can get some help working out the bugs, that would be awesome! First up, I run a lot of different printers here so to streamline my slicer would save me some time as fans have different names in my case. Im trying to run a part fan based on height however I'm getting an error:

if job.layer >= 2	; Set part fan to 100% when print gets to layer 2
	M106 P1 S255

Error: in file macro line 1 column 19: meta command: cannot convert operands to same type

I believe this error is in reference to the "2" in my argument. What am I doing wrong?

@dc42 Ok, well I already ordered a few encoders from bourns. Ill try that out and report back.

@dc42 Here is another example in my home menu. If the knob is turned so it lands between bumps in the encoder, it will actually somewhat oddly select 2 items at once. During this time the scope is flat-lined, so I can 100% confirm there is no noise with the switch in that position.