Hello,
looking for bit of guidance (after i got lost in zmotions product specs and refdesigns)
Unpacked my ZMOTION INTRUSION DETECTION devkit and got quickly thru the setup.
I just wonder how to get the detection of movement DIRECTION going.
Shall i work through Encore (with which i am not familiar with) or is there a faster way?
Looking forward to get a helping hand,
Jacob

Hello Jacob
To get the Motion Direction working, you need to set the Motion Direction Control bit (bit 3 of the EPIR_SC0) and read the Motion Direction (bit 2 of the EPIR_SC0) for the direction. If the bit is set (1) then is it positive (one direction), if the bit is cleared (0), then it is negative (opposite direction). The product spec PS0285, Page 23-25 gives the details.

So assuming you are using the sample application that comes with the ZMotion, you could change the following:



Note:
The directional polarity of PIR sensors is arbitrary at the time of manufacturing. Therefore it is necessary for the user application to calibrate to each individual PIR sensor using a controlled target (i.e. moving in a known direction) and internally record the polarity to identify which polarity represents that direction

Thanks, still some questions:
Should i see the motion bit status via hyperterminal (UART)?
Where to watch this bit?
Or is this a pin on the board that goes high/low?
I changed the code as you said, build says ok, but could not find where to check the bit.
Anyway: my API_INIT is not 04 but 09.h
And in the main function I could not find the code you refer to.
This is the copy
// ePIR_SC0 Default Configuration for Normal Scan Rate //////////////////////////////////////////////////////////////////////////
// Bit 6-7 - Extended Detction - Level 0 (00)
// Bit 5 - Engine Disabled - Engine Controlled (0)
// Bit 4 - MD Suspend - OFF (0)
// Bit 3 - Motion Direction Control - OFF (1)
// Bit 2 - Motion Direction - Engine Controlled (0)
// Bit 1 - Motion Detected - Engine Controlled (0)
// Bit 0 - PIR Stable - Engine Controlled (0)
#define EPIR_SC0_DEF 0x48

Looking forward to hear you,
Thanks again,
Jacob

Hi Jacob
Thank you for the information. It appears you are using the Intrusion sample apps.
Here are the modifications to show the direction on the console.

Modifications:

Under Application Variable Declarations
Add the following line:



In main() function, Find the code (close to the end):



Insert the following:



In the interrupt isrTimer0() function,
Find the code:



Add the following code:


When the application runs, you should now see a direction indicator (D:)

Let me know how it goes.

Dear Tom,
build says ok, but nothing visible happens in the terminal (only the usual M 00x @ xx)
Maybe i inserted the cDirection code on the wrong place, as i could not find the code you refer to as: (else if((ePIR_SC0 & SC0_MOTION_DETECTED) && !cMDCheck) // If the engine indicates a motion event{LED_ON; // Turn on the LED Output port (turned off in T0 int)
it is not in my file so i tried an insertion as follows:

///////////////////////////////////////////////////////////
//Interrupt routine for Timer 0 End of Count (50ms)
///////////////////////////////////////////////////////////
void interrupt isrTimer0(void)
{
if(cMDDelay > 0) // If the LED is still activated
{
cMDDelay--; // Decrement the LED activation time
if(cMDDelay == 0) // If the LED activation time has expired
{
LED_OFF; // Turn off the LED Output port
ePIR_SC0 &= ~SC0_MOTION_DETECTED; // Clear engine Motion detected flag
}
}
if(cMDCheck > 0) // When it hits 0, we check the MD bit in the main loop
{
cMDCheck--; // Decrement the MD check counter
cDirection = ((ePIR_SCO & SC0_MOTION_DIRECTION) ? 1 : 0);

#if (VERBOSE == 1)
ePIR_ASC0 &= ~ASC0_TRANSIENT_DETECTED;
ePIR_ASC0 &= ~ASC0_NOISE_DETECTED;
#endif
}
c50mSecond++;

Jacob
The line is in the wrong place.
Here is the entire ISR routine from the demo with the new line added:





Just in case, here is the entire main() application loop with the new line added:





It looks like your modification of your headfile is correct:

EPIR_SC0_DEF 0x48

Let me know if this helps.
Tom Ormiston