clock base is not valid with U3 hardware version 1.20.ĪddRequest (lngHandle, LJ_ioPUT_CONFIG, LJ_chTIMER_CLOCK_BASE, LJ_tc48MHZ_DIV, 0, 0) is supported and Counter0 is not available. base clock is set to 48MHZ_DIV, meaning that the clock divisor All output timers use the same timer clock, configured here. It will use the next available line, FIO6.ĪddRequest (lngHandle, LJ_ioPUT_COUNTER_ENABLE, 1, 1, 0, 0) They will use FIO4-FIO5ĪddRequest (lngHandle, LJ_ioPUT_CONFIG, LJ_chNUMBER_TIMERS_ENABLED, 2, 0, 0) ĪddRequest (lngHandle, LJ_ioPUT_COUNTER_ENABLE, 0, 0, 0, 0) Set the pin offset to 4, which causes the timers to start on FIO4.ĪddRequest (lngHandle, LJ_ioPUT_CONFIG, LJ_chTIMER_COUNTER_PIN_OFFSET, 4, 0, 0) First, an add/go/get block to configure the timers and counters. The ePut function is used, which combines the add/go/get.ĮPut (lngHandle, LJ_ioPIN_CONFIGURATION_RESET, 0, 0, 0) pin assignments are in the factory default condition. Execute the pin_configuration_reset IOType so that all Table 2.9-2 documents these values.įollowing is example pseudocode for configuring various timers and a hardware counter: LJ_tc48MHZ_DIV //48 MHz clock base w/ divisor (no Counter0)Ĭonstant values used to set (put) the timer clock base differ from the low-level timer clock base retrieved (get) from the device. LJ_tc12MHZ_DIV //12 MHz clock base w/ divisor (no Counter0) LJ_tc4MHZ_DIV //4 MHz clock base w/ divisor (no Counter0) LJ_tc1MHZ_DIV //1 MHz clock base w/ divisor (no Counter0) With the clock base special channel above, the following constants are passed in the value parameter to select the frequency: LJ_chTIMER_COUNTER_PIN_OFFSET //4-8 only starting with hardware rev 1.30. LJ_chTIMER_CLOCK_BASE //Set with the constant values below.
The following are special channels, used with the get/put config IOTypes, to configure a parameter that applies to all timers/counters: LJ_tmFALLINGEDGES16 //Period input (16-bit, falling edges) LJ_tmRISINGEDGES16 //Period input (16-bit, rising edges) LJ_tmSYSTIMERHIGH //System timer high read LJ_tmTIMERSTOP //Timer stop input (odd timers only) LJ_tmFIRMCOUNTERDEBOUNCE //Firmware counter input (with debounce)
LJ_tmFIRMCOUNTER //Firmware counter input LJ_tmFALLINGEDGES32 //Period input (32-bit, falling edges) LJ_tmRISINGEDGES32 //Period input (32-bit, rising edges) In addition to specifying the channel number, the following mode constants are passed in the value parameter when doing a request with the timer mode IOType: LJ_ioPUT_COUNTER_RESET //Sets flag to reset on next read. There are eight IOTypes used to write or read timer and counter information: In applicable functions such as eGet/ePut, the x1 parameter is unused for timers/counters, so it can be set to 0. Timer/counter data can be obtained using any of AddRequest, Go/ GoOne, and GetResult/ GetNextResult eGet/ePut or eAddGoGet. 23th May 2008 : Version 4.20 - Added: Mail library - Added: Ftp library - Added: RegularExpression library - Added: Http library - Added: SerialPort library - Added: FLAC library - Added: SQLite library - Added: DirectX 9 subsystem - Added: Sound Streaming for OGG and FLAC - Added: #PB_Sound_MultiChannel support for the sound library - Added: CreateImageMenu(), CreatePopupImageMenu(), SHA1FingerPrint(), SHA1FileFingerPrint() - Added: CRC32FileFingerprint(), ExamineMD5FingerPrint(), ExamineSHA1FingerPrint(), - Added: NextFingerPrint(), FinishFingerPrint(), IsFingerPrint() - Added: Hexadecimal and binary support for Val() and ValQ() - Added: #PB_Compiler_Procedure compiler constant - Added: #PB_Round_Nearest support for Round() - Added: 'XOr' drawing support for Linux/SDL and MacOS X - Added: New "Profiler" tool for the Debugger menu to monitor how often lines are called in the code - Added: Debugger can now evaluate expressions (see Debug output) - Added: The Memory Viewer can accept any expression as the start/end address - Added: Adding a "+" at the "end address" field of the Memory viewer makes the end address relative - Added: Placing the mouse over a Variable will display its value while the program runs.All timer/counter feature configurations should be set with a single transaction using using eTCConfig AddRequest, Go/ GoOne, and GetResult/ GetNextResult or eAddGoGet.
0 kommentar(er)
