28/07/23 Until 26/07, protocol_2_level_3 was not coded correctly and it was behaving as protocol_1_leve_3.