The YAMCS webapp does not warn the user when a string is bigger than what is defined on the XTCE. At the moment I do not know if this is intentional behavior(I suspect it is not). The current behavior is to send all of the bytes on the string, even if it exceeds the maximum packet length. While flight software warns the user of such error, it'd be nice if YAMCS webapp had some kind of feedback that will let the user know that the string is of X size. Or at the very least truncate the string to avoid issues such as bandwidth hogging and other potentially serious issues.
I still don't know if this is something wrong with YAMCS webapp itself, server or our XTCE definition(which is unlikely). I'll investigate nonetheless.
The YAMCS webapp does not warn the user when a string is bigger than what is defined on the XTCE. At the moment I do not know if this is intentional behavior(I suspect it is not). The current behavior is to send all of the bytes on the string, even if it exceeds the maximum packet length. While flight software warns the user of such error, it'd be nice if YAMCS webapp had some kind of feedback that will let the user know that the string is of X size. Or at the very least truncate the string to avoid issues such as bandwidth hogging and other potentially serious issues.
I still don't know if this is something wrong with YAMCS webapp itself, server or our XTCE definition(which is unlikely). I'll investigate nonetheless.