DCL and ASSR bug

Jan Kargul (1497576)

Hi,
Few days ago me and few other controllers from Polish VACC have came across bug with DCL and ASSR. Below I attach TopSkyCPDLC file (DCL part).

DCL Bug
We are using DCL from TopSky, but it is not working everytime.
Today one of the controllers had tried to send DCL. After filling all required boxes, he tried to SEND it, but it wasn't working - he said it isn't the first time. Me and some other controllers had pretty same issue recently: "I get this every now and then. Sometimes changing something (e.g., initial climb) and reopening the window helps. And sometimes it doesn't, and no matter what I do, SEND is disabled.".
Tl;dr SEND button is disabled when all required windows are filled.
Below: alert window from TopSky from the first controller

This is my alert window when I had this issue, but I don't know if it was the reason of the issue.

ASSR Bug
One of the controllers couldn't assign SSR code for WZZ4NU (link to the flight). Firstly, he tried to do it automatically a couple of times. Then, he tried manual assignement using numpad on ASSR window. He couldn't assign any squawk with any method than default Euroscope assignement. After he did it, he couldn't assign sq once more from TopSky ASSR window. After few minutes something has changed in the departure list and the WZZ position will appear in the stand column (it wasn't visible before, we are using Departure stand from GRP) and SQ had then been assigned normally.

[DCL]

DCL:EPGD,EPKK,EPKT,EPMO,EPPO,EPRZ,EPWA,EPWR:SID:CLD <hour><min> <year2><month2><day> <adep> PDC <number> <callsign> CLRD TO <ades> OFF <drwy> VIA <sid> SQUAWK <assr> NEXT FREQ <freq_own> <atis> SID INITIAL CLIMB ALTITUDE <cfl>. AIRBORNE FREQUENCY <freq_dep>. <rmk>

DCL:EPGD,EPKK,EPKT,EPMO,EPPO,EPRZ,EPWA,EPWR:AHDG:CLD <hour><min> <year2><month2><day> <adep> PDC <number> <callsign> CLRD TO <ades> OFF <drwy> VIA RUNWAY HEADING SQUAWK <assr> NEXT FREQ <freq_own> <atis> INITIAL CLIMB ALTITUDE <cfl>. AIRBORNE FREQUENCY <freq_dep>. <rmk>

Juha Holopainen (839337)

Jan Kargul (1497576) DCL Bug

The "Send MSG" button is active when all the following are true:

you are a controller
you are tracking the aircraft, or no-one is tracking it
the aircraft's "clearance received" flag is not set
a defined clearance format is available for the aircraft
all the required fields are filled (RWY, CFL and ASSR are always required, NPT, NFREQ and DFREQ are required when present in the clearance format definition)

The last two requirements seem to be met in the images, so it's one or more of the three first ones that aren't. The conditions are checked each time the window is refreshed - usually once every second.

Jan Kargul (1497576) ASSR Bug

The error message means that the plugin has selected a code to be assigned - 5445 in that case - and called the API function to set it as the assigned code, but the function has returned "false" which means EuroScope did not set the value. It is not possible to determine why that happened, but if the aircraft's departure stand information wasn't available at the time, that tells that the plugins could not see the aircraft - just its flightplan, and that would prevent the code assignment and finding the departure stand.

Jan Kargul (1497576)

Today's causes - SEND button is inactive. Controller tried to send clearance, filled all required window, without success

Screenshots from EPWA GND