@dc42
Ah, thank you for the clarification. Now that i know what I am looking at it makes much more sense.

Thanks for the additional tips but still no luck. Looks like a warranty exchange is in my future.

I had this issue also. In my case I had flashed it with the wrong firmware and not the 7.0i firmware.

I think this is the same issue as reported here: https://github.com/dc42/PanelDueFirmware/issues/39

nikscha created this issue in dc42/PanelDueFirmware closed wrong layout when using only heater 2 #39

@bret4 said in Paneldue button location incorrect:

Even with calibrate my big fingers sometimes push the wrong buttons on the touch screen. I have used a touch stylus at times to make it easier.

Try using the tip of your fingernail.

@wyvern said in Panel Due 5/7i functionality update in store?:

Just curious, I like the panel due, especially the backup if wifi goes out and you can still use the backup SD slot, but wondering if there will ever be an update where you can access system folders like config and home and program it right there on the spot?

It would great for people like me where my PC is in my room and the printer is in the garage.

Unlikely, because of the low screen resolution and limited memory. But if you get something wrong in config.g that stops the WiFi working, you can use the keyboard on the Console page to send the commands needed to get WiFi working again.

Yes the ribbon cable is straight through and can be reversed. You can use both cables, but I can't see any advantage in doing that unless one of the cables has a bad connection.

Well, I'd volunteer to do the tool/heater work but it's not going to do anyone any good if it never gets merged. 🙂

I suppose I could do it in my fork and release it from there but having two versions isn't really a good idea and it would be hard to merge any changes you make in your repo.

I guess I'll just do my own thing in my fork and keep it private.

It is probably the first version with a 5" screen.

hi i posted my design on thingerverse recently
https://www.thingiverse.com/thing:3300113

@mwinterm said in Extension of M408:

Further does does the Firmware update position at all during a move or is the position only updated at the beginning / end of the move? I realized that feed adaptions are only executed for the next G-code line coming up...

The user positions are updated at the start of as move, and the machine positions at the end of a move.

Progress bar on panel due based on where in the file it is progress bar on DWC depends on what it reads from the gcode file, if the gcode file has information about filament usage, it will use that -- there is a tail section appended by S3D which indicates filament usage. The firmware figures out time left for file position, filament usage and layer time -- the progress bar in DWC doesn't use that (I'm having an issue with that myself with ditto printing since the DWC progress bar is very confused). If filament usage is not available the progress bar in DWC goes by layer height position, provided it's the same -- current out of total, otherwise as a last resort it takes % printed as reported by the firmware -- it's rather confusing why DWC does so much on it's own to figure out progress.

@patakopecek said in Bed Level Calibration button:

BTW if the G32 is deprecated then why don't you remap it by default? @dc42

It's only bed compensation using G32 that is deprecated. It's still needed for automatic or manual bed level adjustment and for delta printer calibration.

One way to implement a hardware lock is simply to put a toggle switch in the power line (plus, not ground). Literally power it off when it is not being used. When powered up, it will "re-sync" itself.

Neither "disappearing" or "reappearing" will affect the actual Duet and/or print job progress.

DC42 and the folks at Duet/Escher can't really "recommend" or "support" this, because, in theory, power cycling COULD cause some kind of problem someday... and power cycling just flatly makes design engineers uncomfortable. 🙂

However, as an end user, I can say I've unplugged and re-plugged PanelDue devices from Duets that were printing, many times. I've even upgraded PanelDue firmware (unplug, carry to computer, upgrade, carry back to printer, plug in) during the middle of a multi day print.

Your decision...

The volume should definitely change with the setting. Have you tried different frequencies? AFAIR the piezo buzzer is loudest at around 2400Hz.

You need at least RRF2.02RC4 for this to work: https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md#version-202rc4

OK, thanks. I went back and looked again. There is nothing on my version (1.20beta4). I guess I need to update to the latest.

I know, but where to add them?

Ahh! Thanks! I think so 🙂 Will try!