The uplink payload Decoder Problem

HI TTN:

I found there are the size limit on the source code of uplink payload decoder.

It shows me that the max size of decoder coder is 4096 Bytes.

image

But we have some products, the function is complex and optional, the size of decoder code will beyond 4096 Bytes. When our customer copy the decoder code on your platform , it cnanot be svaed successfuully, as it shows that the size is beyond.

We have tried to simplify the program, but 4096 bytes is really too little. I hope you can increase it to 20480 bytes at least.

And, it cannot be saved in V2, it seems that the limiit of size is only in V3.

Please search the forum for prior discussion on this. And review the GitHub issues too.

Who are you asking?

I means that hope ttn can increase the size of decoder.

I’ve confirmed that’s where the problem lies, It would be nice if there were other solutions

There are - like the device repository - or reviewing the payload formatter as many of these problems seem to come from JS trying to cover too many types of devices - or minification or both.

If use the repository, we need update the product information in lorawan-device repository.
I ever push the product information once when we join in The Things Conference this year. But there are updates on these product recentenly.

Infact, the decoder only contains only one product, we have indenpent paylaod decoder for each product.

Anyway, i think 4096Bytes is too samll…

You will have to raise an issue on github for this feature request.

So you update your entry and it gets included in the main system - and you can do that on a twice daily basis if you want …

I get by just fine, so I don’t. I’m actively campaigning for the limit to be kept to 4KB because you shouldn’t rely on a decoder that may not run due to server pressures.

1 Like

What do you do or where do you display your node data you are collecting, you must have some type of application outside of TTN.

Why don’t you just decode there?