There is no limit inside Jinx! for tpm2(net) channels. But as tpm2.net is network based you should try to use a smaller blocksize in the tpm2.net output, because sending 1466 channels in one network packet will result in fragmented packets on the network and most of the small tcpip stacks for microcontroller will not handle fragmented packets. Thats why a block size is implemented into tpm2.net, this has nothing directly to do with Jinx!.
If your implementation supports multiple blocks, you have to try or ask the author. It is cleanly defined inside the protocol for the given reasons. As far as I remember, we got good results by using a block size around 800channels with a SEDU3.Seddi Thank you for your answer but I would like to ask how I should set up another 512 to control the LEDs because I set Channels to 1536 and Chan / Block then automatically get 1 Block rightly so ?.
//edit
Looked into the source code, you linked. Seems like there are no multible blocks supported, like defined in the specs. So with this implementation, you will not be able to use a channel size that will break your mtu size (including protocol and udp overhead).
Seddi Thank you for your answer but I would like to ask how I should set up another 512 to control the LEDs because I set Channels to 1536 and Chan / Block then automatically get 1 Block rightly so ?.