PanelDue firmware 1.22 released

brunofporto

@dragonn said in PanelDue firmware 1.22 released:

/dev/ttyACM0

Please, @dragonn do you know the command to show this address? I am using Ubuntu

Thank you very much.

dragonn

@brunofporto said in PanelDue firmware 1.22 released:

@dragonn said in PanelDue firmware 1.22 released:

/dev/ttyACM0

Please, @dragonn do you know the command to show this address? I am using Ubuntu

Thank you very much.

Connect you PanelDue via USB and run:

dmesg

At end of the log you should see that you PanelDue connected and at with port.

brunofporto

@dragonn Do I need some special driver or anything?? I just can not find it...

brunofporto

@dragonn It is the same issue I had before... I just do not show up anywhere
Tested using different USB ports and cables to be sure.

brunofporto

@dragonn ok....

Well.... Now it appeared. After pressing the ERASE button... I show up as ttyACM0 But whenI use bossac it claims "No device found on /dev/ttyACM0"

garyd9

@dc42, I was browsing the github commit for 1.22 and noticed that in UserInterface.cpp, the "extrudeSpeedValues" array was changed to have new display values for extrusion rates. However, the "extrudeSpeedParams" array was not changed and still reflects the old extrusion rates:

static const char * array extrudeSpeedValues[] = { "50", "20", "10", "5", "2" };
static const char * array extrudeSpeedParams[] = { "3000", "2400", "1200", "600", "300" };

dc42

@garyd9 said in PanelDue firmware 1.22 released:

@dc42, I was browsing the github commit for 1.22 and noticed that in UserInterface.cpp, the "extrudeSpeedValues" array was changed to have new display values for extrusion rates. However, the "extrudeSpeedParams" array was not changed and still reflects the old extrusion rates:

static const char * array extrudeSpeedValues[] = { "50", "20", "10", "5", "2" };
static const char * array extrudeSpeedParams[] = { "3000", "2400", "1200", "600", "300" };

Thanks for pointing that out. I'll fix that in a 1.22.1 release. I'll wait a few days first to see what other issues with the new firmware arise.

garyd9

@dc42 I didn't send a pull request for that extrudespeedparams as I wasn't really sure about it. I did send a pull request for an issue that popped up many versions ago and I was too lazy to fix. (Dim on Idle should treat "off" as being idle.)

Please, Please, PLEASE forgive the parenthesis mess.

dragonn

@brunofporto said in PanelDue firmware 1.22 released:

@dragonn ok....

Well.... Now it appeared. After pressing the ERASE button... I show up as ttyACM0 But whenI use bossac it claims "No device found on /dev/ttyACM0"

You know that you need press the erase button?
You should really read the instruction https://miscsolutions.wordpress.com/paneldue/
You are just doing something wrong, it works perfectly fine. Even easier the on Windows.

garyd9

@dc42 said in PanelDue firmware 1.22 released:

@garyd9 said in PanelDue firmware 1.22 released:

This isn't good. It's popping up WAY too often and there's no way to disable it. It also exposes a problem if there's another popup already on the screen.
For example, it's no longer possible to "baby step" twice in a row quickly via the paneldue. From the PanelDue "print" page, I tap "baby step" and I see the +0.02 and -0.02 buttons. As soon as I press one, I get a "Response" titled popup telling me that "Baby stepping offset is -0.02mm".

I think I should change the Duet firmware not to generate those messages.

Some more: I'm using the paneldue to PAUSE a print. I have a big popup telling me I just paused the print. (Really? No! Is THAT what the "pause" button does??) Then I use the paneldue to CANCEL that print. Guess what happens? It pops up a message telling me I just canceled the print.

This makes the paneldue miserable to use.

brunofporto

@dragonn I quit....

Even with the device detected and correctly identified within the bossac command it simply did not work...

I bring it home to update it using Windows again..... But thank you very much for your help. Maybe next time I'll discover what I did wrong....

wesc

It also tells me with an annoying pop up when the duet joins the network.

I was excited for this pop up status feature mostly to see the results of the delta bed probing.

It’d be really nice if paneldue parsed that response and displayed it next to the bed level button.

brunofporto

I am having some issues.

1- If I call M591 D0 it still not enough text room for the entire response.
2- The stop button at the top left did not work like the equivalent at DWC and after pressing it PanelDue was not able to connect again until I hit the emergency stop at DWC
3- I run a macro for my Z-Probe tunning, that have some issues of not selecting the tool, but if called from PanelDue I do not get any warnings - it just locks as busy and do nothing (that is why I hit the Stop....)

garyd9

@brunofporto said in PanelDue firmware 1.22 released:

3- I run a macro for my Z-Probe tunning, that have some issues of not selecting the tool, but if called from PanelDue I do not get any warnings - it just locks as busy and do nothing (that is why I hit the Stop....)

When that happened, did the top of the PanelDue say "changing tool..."? (If so, I've had the same thing happen, but I have no idea why and I haven't been able to repeat on demand.)

dc42

@garyd9 said in PanelDue firmware 1.22 released:

For example, it's no longer possible to "baby step" twice in a row quickly via the paneldue. From the PanelDue "print" page, I tap "baby step" and I see the +0.02 and -0.02 buttons. As soon as I press one, I get a "Response" titled popup telling me that "Baby stepping offset is -0.02mm". I can't baby step again because that popup is "in the way." However, I can't tap the red X on the popup either (probably because the baby step popup is also up, behind the "response" popup.) The only escape is to wait a few seconds, or tap something like "Control" at the bottom - which will close BOTH the response popup and the baby step popup.

This was caused by a combination of 2 bugs. First, the baby stepping buttons were sending extra M290 commands that caused the existing baby stepping amount to be reported. Second, it wasn't possible to close a window if the close button was above or to the left of the previous window. These are both fixed in the forthcoming 1.22.1 release.

dc42

@brunofporto said in PanelDue firmware 1.22 released:

If I call M591 D0 it still not enough text room for the entire response.

Fixed in the forthcoming 1.22.1 release.

dc42

@brunofporto said in PanelDue firmware 1.22 released:

The stop button at the top left did not work like the equivalent at DWC and after pressing it PanelDue was not able to connect again until I hit the emergency stop at DWC

I'm sorry, I can't reproduce this. There is the problem that the STOP button on PanelDue doesn't always work instantly, because the command gets queued up; but other than that nit does the same as DWC i.e. resets the Duet after stopping it.

dc42

I'm closing this thread because I have just released PanelDueFirmware version 1.22.1 and I am about to create a thread about it.