“…When the current device sends the response on the bus, if the slot address does not match the device's ModbusE address for the corresponding response slots, the myTaskServerMBEcycle task moves the data from the application memory organized by Modbus data and addressing model into the slot with the function "void vexecuteRecvSlotWriteRegs(uint8_t SlotIndex)" given the Modbus read functions 1, 2, 3, 4, 7, 11, 23 based on the information in the MY_SLO_PARAM slot structure. For slots with Modbus APDU, i.e., when the slot address matches the Modbus address of the device, the myTaskServerMBEcycle task moves the data and responds if necessary according to the Modbus specifications for functions 1,2,3,4,5,6,7,11,15,16,22,23, directly using the information in the request with the function "void vModbusExecuteFunctions(void)". As the highest priority task, it will perform atomic read/write operations.…”