Everyone,
The frequency hopping implementation in the PurePath Wireless protocol is not fulfilling the FHSS requirements in EN 300 328 V1.8.1
Even though we implement a LBT at the start of every timeslot in release, the protocol actually has mechanisms to ensure latency and a minimum throughput is enforced. If LBT fails, there will be no RF activity in the following timeslot, however, in the next two timeslots we are enforcing transmission independent of the LBT results. For this reason we can’t claim adaptivity per ETSI EN 300 328 V1.8.1.
To pass this new ETSI standard with v1.4.2, one needs to be below 10 dBm e.i.r.p
Best regards,
The PurePath Wireless team