Guy Harris wrote:
>> It would be reasonable to anticipate additional characteristics that
>> could make their way into a capture file for received traffic, such as
>> RSSI and noise levels, antenna selection, etc. For the requested link
>> types, the packet will start with the MA
On Sep 10, 2014, at 11:39 AM, Joshua Wright wrote:
> It would be reasonable to anticipate additional characteristics that could
> make their way into a capture file for received traffic, such as RSSI and
> noise levels, antenna selection, etc. For the requested link types, the
> packet will
>> R1 - 9.6 Kbps (908.42 North America, 868.42 Europe)
>> R2 - 40 Kbps (908.4, 868.4)
>> R3 - 100 Kbps (916, 869.85)
>>
>> The MAC format for R1 and R2 Z-Wave networks is identical, but the R3
>> MAC is different with additional fields and different bit mask
>> definitions.
>
> So there are diffe
On Sep 6, 2014, at 3:35 AM, Joshua Wright wrote:
> I request two DLTs for Z-Wave packet captures based on the ITU-T
> Recommendation G.9959 (http://www.itu.int/rec/T-REC-G.9959).
>
> My packet capture tool has support for three Z-Wave RF profiles
> (sometimes called "channel configurations"):
>
Hearing no questions, is there anything more I can do to get this request
authorized?
Thank you,
-Josh
On Sep 6, 2014, at 6:35 AM, Joshua Wright wrote:
> I request two DLTs for Z-Wave packet captures based on the ITU-T
> Recommendation G.9959 (http://www.itu.int/rec/T-REC-G.9959).
>
> My pa
