Topics created by that guy E

@jay_s_uk

Unfortunately the buttons aren't accessible without removing the screen. Not the end of the world, but just wanted to see if there was something I was doing wrong.

@that-guy-e not really. It's just a standard warning from the firmware

@phaedrux

I had to change P1 to P0. Looks like its working now.

If I left the P parameter out, the panel due creates two chamber heaters, 0 and 1. Not exactly sure why.

@jay_s_uk

Thanks for the clarification.

@phaedrux

I will try moving it to start.g

I have a print_start.g which is called out after setting bed and nozzle temps. I was hoping to automate some retract sequences in the filament runout, but I can't include them without first having the nozzle hot.

I might just define it as an external trigger, so I can set it so it to only trigger during a print. Assuming triggers still behave the same

@that-guy-e

Connecting ground to the daughter board and the VCC to the io.7 appears to have solved the problem.

I'll continue to monitor and test on another controller.

You've been helpful as always

@droftarts

I went back and reviewed the instructions and it looks like I miss read that table.

Thank you for the clarification

@phaedrux

sorry for the late reply, I just saw this. I'll do a direct connection and see what happens.

In RRF 3 you can use conditional gcode and daemon.g to monitor the voltage and perhaps take an appropriate action.

@that-guy-e said in Panel Due Jog Axis In Message Not Displaying:

@dc42 @mfs12

Thank you. I can reassign A to U and post process gcode for the interim. Do you guys have any timeline for the next panel due firmware update?

Note yet, but we may have news soon.

For future reference are thing like this best brought up here or github?

Here, because it's not always obvious whether an issue needs fixing in RRF, PanelDue, or both.

@dc42

I have not run into further upload error using the beta firmware you provided.

Issue couldn't be reproduced. Closing it for now.

Please refer to comment on github for detailed testing procedure.

If issue still persists, please reopen issue and add details on howto reproduce it.

https://github.com/Duet3D/PanelDueFirmware/issues/240#issuecomment-1700942480

mfs12 created this issue in Duet3D/PanelDueFirmware closed m291 message from start.g not displayed before print after issuing either M112 or M999 during print #240

@dc42

On a duet2 running RRF 2.x the board would reboot after an estop trigger without issuing a M999.

I think my current approach using the reset input on the duet3 should work. And I also don't see all of the driver errors like I do with m112.

If I was to upgrade an duet2 to RRF3.3 with a duet expansion how would I reset the board via an external input? If memory serves the reset pins on the duet2 are in the 50 pin.

@rjenkinsgb Appreciate the info, reconsidering my original plan

@dc42

Have any additional plans been made to add the ability to use a secondary SD card on the Duet3?

@that-guy-e open circuit for a thermistor has always been -273C AFAIR, although I can't be certain that's true for every RRF version. Open circuit for a PT1000 is 2000C. However, with a -273C reading you should still get a heater fault if a heater uses that sensor and you try to heat it.

@dc42 looks like i may've had an old IAP file. went back and download the 2.02 IAP fil and then i was able to upload to 3.0

Thanks for the quick response.

@mfs12

Just saw this response. I appreciate the follow up. Just updated to 3.3 on a new build and got everything working. Will update my panel due this evening and check it.

It may be worth trying a fresh SD card. The web files are loaded from the SD card, so if they can't load, the page can't load.

Seems to be working today. Not sure what the deal was.

Thanks again for the quick response.