Page 1 of 1

Issue with the CST assignment to [Shift] [Up]

Posted: Thu Oct 15, 2020 3:02 pm
by dlachieze
I’ve identified an issue with the CST assignment to [Shift] [Up]. It is not working with the latest firmware V2.0 nor with V1.15, however it’s working correctly with V1.14.

I used to assign FAST to [Shift] [Up] and SLOW to [Shift] [Down] as suggested in the manual. I didn’t had to change the speed while using V1.15 so I didn’t notice it was broken.

To reproduce it:
  • flash the firmware (V2.0 or V1.5)
  • press [Shift] [CONF] to assign FAST to [Shift] [UP] and SLOW to [Shift] [Down]
  • go to SI or Stack view
  • press [Shift] [Down] => SLOW is displayed and executed
  • press [Shift] [Up] => instead of FAST, the current step of the current program is displayed and executed, so [Shift] [Up] is acting as SST
I’ve verified this with both V1.15 and V2.0, however with V1.14 [Shift] [Up] is correctly executing the FAST command.

Note: after each firmware flashing, you need to go re-assign FAST and SLOW to [Shift] [Up] and [Shift] [Down]

Re: Issue with the CST assignment to [Shift] [Up]

Posted: Thu Oct 15, 2020 3:10 pm
by rprosperi
Thanks for reporting this DIdier, we'll look into it; it's strange we've not seen this as FAST/SLOW are used often in testing... hmmmm...

Re: Issue with the CST assignment to [Shift] [Up]

Posted: Thu Oct 15, 2020 4:16 pm
by ecsfang
The behaviour is a little bit different then described.
  • If I assign FAST and SLOW as described, they execute when I press them (normal keypress).
  • If I press and hold [shift] [down] then "SLOW" is shown and executed - as expected.
  • But with [shift] [up], then it doesn't show "FAST" but it is executed (enters fast mode) AND then it works as [SST] showing and executing the next step.
    • Note - this only happens if I hold the key long enough (a quick press only execute FAST).
  • If I assign something else, like "BEEP", it will beep, and then show the next step and execute it if I don't release the key (e.g as [SST]).
So assigning something to [shift] [up] will execute the command (without showing it) and then (if pressed long enough) also execute [SST].
Seems like [shift]-flag is cleared by executing the assigned command, and then the up-key is handled as being pressed without [shift] --> [SST].

I have v2.0 in my device.

Regards,
Thomas

Re: Issue with the CST assignment to [Shift] [Up]

Posted: Thu Oct 15, 2020 4:49 pm
by dlachieze
ecsfang wrote:
Thu Oct 15, 2020 4:16 pm
The behaviour is a little bit different then described.

So assigning something to [shift] [up] will execute the command (without showing it) and then (if pressed long enough) also execute [SST].
Seems like [shift]-flag is cleared by executing the assigned command, and then the up-key is handled as being pressed without [shift] --> [SST].
You're right that the command assigned to [Shift] [Up] is executed, I missed that because it was not displayed on a long press.

So I replaced FAST by CHS and rechecked with V2.0:
  • each press on [Shift] [Up], short or long, will execute CHS
  • after each press on [Shift] [Up], short or long, if I go to PRG mode, the program counter has moved one step ahead, so SST was also executed on each press.
    EDIT: if the press is VERY short, then only CHS is executed, but with a normal key press on my DM41X beta (not too long to display the function name) both CHS and SST are executed
  • up-key without [Shift] is BST, not SST, so I don't think it's an issue with the Shift flag
One more thing: the description above applies when the DM41X is in FAST mode, when it is in SLOW mode a normal key press on [Shift] [Up] just executes CHS and not SST, however it takes a long time to change the sign of the X value, much more than the normal CHS key*. If you keep pressing on [Up] after [Shift] in SLOW mode, then after ~3 seconds you see the sign of X changing and then the current program step is displayed and SST is executed unless you keep pressing until NULL is displayed.

*note: this long time applies also in SLOW mode to other keys, I've assigned CHS to [Shift] [Down] and also to [C] and it all cases execution of CHS through the CST assignment is much longer than with the CHS key.

(Edited to add the note above)

Re: Issue with the CST assignment to [Shift] [Up]

Posted: Thu Oct 15, 2020 5:12 pm
by ecsfang
Hi DIdier,

Yes, that is similar to what I found when I read your post.

Regarding the disappearing [shift] - I was just thinking about that the [UP] is in fact coded as [shift] + [SST] = [BST].
See another post where it is noted that somtimes when you press the [UP]-key, the [shift] annunciator is lit, and the explanation is that [UP] is actually coded as [shift] [DOWN] == [shift] [SST] == [BST] (since [BST] doesn't have it's own unique key-code).

So with some logical deduction I thought that [shift] + [UP] - [shift] == [shift] + [SST] - [shift] == [SST] ... :lol:

Regards,
Thomas

Re: Issue with the CST assignment to [Shift] [Up]

Posted: Thu Oct 15, 2020 6:29 pm
by rprosperi
Thank you guys for the additional observations and testing to clarify the actual situation, it's very helpful, and also really good timing! :mrgreen:

Thanks again!

Re: Issue with the CST assignment to [Shift] [Up]

Posted: Sat Nov 14, 2020 5:13 pm
by dlachieze
Fixed with firmware V2.1. Great support from SwissMicros !