C dev Modify Motion MMAL for Rasp Pi 2/NOIR camera

Looking for a C developer to do major modifications to the MMAL implementation of Motion for Raspberry Pi 2 using NOIR camera. [login to view URL] We provide system OVERALL REQUIREMENT: Utilizing a camera on a stepper motor, step through zones and allow for the motion code to attempt to detect motion inside the zone. Furthermore, allow for interruption of scans by a PIR detection causing the camera to step into that zone and begin detection of movement. Consideration for IR lighting and time of day will also be necessary. The PIR detection is happening through a polling mechanism that is receiving data from GPIO ports. Mod for camera - This requires using Raspberry Pi 2 with a NOIR Raspberry Pi camera. Mod to movement - Through a configuration, a stepper motor configured on the Raspberry Pi 2 GPIO ports will rotate 360 degrees in a series of steps. Each step will be identified as a zone. The loop of scanning will stop in each zone for a configured amount of time and scan for movement. It will then proceed to the next zone until all zones are cycled. It will then spin the motor back to the original position and do it again. Track movement - Through config, the stepper motor knows the width of the camera angle and can track the motion attempting to center the motion into the camera. Scan vs detect - Other means of detection can cause the camera to break the scan pattern. When a detection is found, the camera will turn into the detection and begin scanning from that detection. If no motion is detected, it returns to its previous scan pattern. The Other Means is a polled method that will programmatically be looking at signals from the GPIO. If it detects something, the detect algorithm will cause the camera to turn into it and begin the camera scan. The motion MMAL implementation will need to utilize the rectangle method to identify where in the image the motion has been detected. The motion MMAL implementation will need to be altered to identify through the naming of the image where the camera was pointed. {SysName}_{Angle}_{DateTime}.jpg The variables involved: fViewWidth, Width of Camera View: a value from 1 to 360 which states in the number of degrees the width of the camera view. fPulsePerDegree, Pulse per degree of step motor: A value that identifies the pulse value of the step motor to rotate the step motor 1 degree Number of Zones: a value from 1 to 360 to identify the number of zones that the step motor full view should be divided into in order to scan Degrees per Zone: a value that tells the number of degrees to provide for each zone. If Degrees Per Zone * Number of Zones > 360, then the configuration is in error. This does allow for the total of all zones to be less than 360 however. Seconds of Detection Per Zone: a value that tells in seconds the amount of time to scan the zone before moving to the next zone Time to traverse zone in seconds: a value that delays scanning while the camera is being moved into the next zone. Absolute degrees before reset required: this value defaults to 360 but allows the system to make sure that a configuration does not over wrap the cables while scanning. Path to post image of movement: an absolute path where an image is posted when motion is detected Size of motion: from the motion application, determines the size of change before "motion" is declared. StartTimeOfDay: Indicates the time that the camera is scanning EndTimeOfDay: Indicates the time that the camera stops scanning Use IR: Indicates whether to send a message to turn on the lights of a zone (true/false), when true, when the zone is being scanned, a message is sent to the devices in the zone to turn on the infrared lights to allow for a scan to occur. The stepper motor has been configured just like this: [login to view URL]