data_length
Description
Specifies the Data Length which is the amount of memory addresses to make available for chirping. The larger the Data Length, the more frequencies that can be output.
Syntax
Read
Gets the current Data Length.
Example
unsigned wfDL;
wfDL = dsm.data_length;
Write
Sets the new Data Length.
Example
dsm.data_length = 0x40;
Notes
The Data Length should always be either shorter or equal to the Memory Depth. If you want the DSM to go back to the starting frequency before reaching the Memory Depth, you should turn on the Data Length using the data_length_enable property. You would use the Data Length if the number of frequencies you want to chirp is not one of the Memory Depth settings. Please note that even if the Data Length is disabled, you should still specify the correct Data Length. For example if the number of frequencies you want to chirp is 65,536 (which is one of the Memory Depth options) then you would set the Memory Depth to 65536 and disable the Data Length but you still would need to set Data Length to the hexadecimal equivalent of 65536 (4000).
The Data Length is useful for users who want a duty cycle chirp. To do this, set the Data Length but set the data_length_enable to "false". The DSM will chirp up to the Data Length then will output the start frequency until it reaches the Memory Depth. To see the different patterns of chirps available, please see the DSM Manual.
For users who want a duty cycle chirp but the total number of frequencies is not equal to one of the Memory Depth settings, you can use the user_define_bulk or the user_define_file functions.
Data Length will not work for chirps that are under 1000 frequencies long even if you have Data Length enabled.