DSF Failed to serialize code

NineMile

I had a user try to run the MillenniumOS config wizard yesterday on a new SBC setup of RRF 3.5.4 on a BTT Kraken board, and they received the following errors:

I've not seen this before on a standalone setup, and this may well be the first person to try using SBC mode with MillenniumOS as I personally don't have an SBC setup to test with.

We managed to narrow it down to MillenniumOS usage of html codes within the M291 dialog commands, the file being run to cause these errors is here: https://github.com/MillenniumMachines/MillenniumOS/blob/main/macro%2Fmovement%2FG8000.g

I'm aware that this is problematic if used on something not-a-browser but MillenniumOS was always designed with browser usage in mind, and has been using HTML styling in dialog boxes since very early in development to make some of the information clearer.

Do you think this is something that can be fixed? I assume special characters are limited for some reason but I have no context as to why that would be the case in DSF and not in standalone mode.

chrishamm

@NineMile I think the messages from M291 are too long, so DSF cannot send them to RRF. The maximum length of a G-code is 256 bytes, which is exceeded by your logic, and depending on the number of parameters it's a bit lower in SBC mode due to the way G-codes are transferred. If you reduce the message length, it should work again.

I'm going to change the error message in v3.6 to be more specfic.

NineMile

@chrishamm said in DSF Failed to serialize code:

@NineMile I think the messages from M291 are too long, so DSF cannot send them to RRF. The maximum length of a G-code is 256 bytes, which is exceeded by your logic, and depending on the number of parameters it's a bit lower in SBC mode due to the way G-codes are transferred. If you reduce the message length, it should work again.

I'm going to change the error message in v3.6 to be more specfic.

Gotcha, thanks for the clarification. It has definitely been fun trying to fit the M291 dialog contents into 256 bytes so yes, some of these could be right up against the limit (I know I pushed some over by adding the J2 parameter on some dialogs while testing with v3.6.

I'll take another look at dialog lengths and see where these need to be sorted out.

Thanks again