>> [ 1 ] RX trigger mode test
>> When do I need to do this test?
>> [ 2 ] RX continuous mode test
>> When do I need to do this test?
Short answer:
If PER measurement required, use trigger mode. Else use continuous mode.
Trigger mode needs a trigger signal from the tester. Continuous mode doesn't.
Long answer:
For Rx continuous mode test, the DUT (device-under-test, aka, your design) just keeps receiving all packets, sent from a reference tester. At the end, software counts how many good packets are received (CRC check ok).
If any packet lost in the air, because of the RF interference or other reasons, in the Rx continuous test we will not know. Because we don't know how many packet in total should be received.
So we need the Rx trigger mode test. When the reference tester sends a packet, it also gives a pulse on a wire. This wire would be connected to the Rx side. By counting how many pulses on the wire, the Rx would know how many packet in total. And then it can calculated how many actual packet it received, as well as the PER (packet error rate).
>> What signal generator is used?
Check the RF tester being used. It probably has a trigger signal output, that will connect to your IUT device.
>> No DIO17 pins on the circuit?
I am not sure on this. I suggest you to check the SW implementation of the Certi tool on K32W and QN9090/30
