Results are different between command line(generateSchedule.sh) and Eclipse java project(use src/*.java files)? about tsnsched HOT 1 CLOSED

Hello,

About your first question, it is possible that some of the optional constraints are enabled on the .jar file version, making your schedule different from what is generated when you run TSNsched on your IDE. I would have to double check that. Also, depending on how the solver handles the network that you give as input, the result can be slightly different, so even the order of creation of your devices can affect your output. Don't worry though, both schedules are valid.

About the slot duration (the transmission window size), TSNsched allows your transmission window to be greater than the transmission of a single packet. This can be useful to create more flexible schedules allowing the usage of a single transmission window to transmit more than one packet (given that they have the same priority/class). That said, TSNsched sometimes can create a slot with 50 microseconds of duration to transmit only one packet (that takes 13 microseconds to be transmitted). You can fine tune the duration of a slot controlling the maximumSlotDuration variable in the cycle. It is given as a parameter of the constructor method of the Cycle objects. Notice the "new Cycle(50);" commands on the GeneratedCode class, which basically means "create a new cycle where its slots cannot have their duration greater than 50".

I hope this clarifies your questions. Let me know if there is anything else that I can help you with.

from tsnsched.