Iyán, Yes, both strategies seem to work.
Here is my config file https://gist.github.com/phrocker/a209b5163044a5bb3c2e6ac4662ce143 Below is the output form my pi. Due to the time it takes to create a PNG and the scheduling strategy it usually ends up being about a second between pictures. When I reduce my configuration to what you have ( for the timing config options ) I maintain the same pattern of taking a picture every 900 ms. Logs may help further diagnose the issue. [2018-04-23 11:11:17.484] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:18.690] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:19.850] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:20.998] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:22.145] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:23.284] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:24.427] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:25.573] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:26.718] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:27.860] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:28.998] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:30.143] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:31.286] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:32.429] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:33.573] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:34.717] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:35.875] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:36.999] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:38.129] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:39.255] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:40.384] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:41.513] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame [2018-04-23 11:11:42.639] [org::apache::nifi::minifi::processors::GetUSBCamera] [debug] Got frame On Mon, Apr 23, 2018 at 6:27 AM, Mendez Veiga, Iyan <[email protected]> wrote: > Ok, thanks Marc! > > > > And do they work for you both TIMER_DRIVEN and EVENT_DRIVEN in the > raspberry? Can you send me a config.yml you have using the GetUSBCamera? > > > > Best regards, > > Iyán > > > > > > De: Marc [mailto:[email protected]] > Enviado el: lunes, 23 de abril de 2018 0:22 > Para: [email protected] > Asunto: Re: [NIFI-CPP] Issues with TIMER_DRIVEN and CRON_DRIVEN > > > > **This Message originated from a Non-ArcelorMittal source** > > I wanted to follow up and say that timer driven and event driven are the > only scheduling strategies available in minifi c++. Cron is not a supported > strategy yet. Sorry for not mentioning this earlier > > > > On Sun, Apr 22, 2018, 4:05 PM Iyán Méndez Veiga <[email protected]> wrote: > > Hi, > > I haven't been able to configure MiNiFi to take pictures every 30 seconds > using GetUSBCamera processor. I have the following in the config.yml > > - name: take_picture > class: GetUSBCamera > max concurrent tasks: 1 > scheduling strategy: TIMER_DRIVEN > scheduling period: 30 sec > auto-terminated relationships list: > - failure > Properties: > FPS: 1 > Format: PNG > USB Vendor ID: 0x046d > USB Product ID: 0x082d > > The processor ignores the scheduling period and it takes pictures > continuously. I tried to use the CRON_DRIVEN but any processor seems to > work. > Perhaps is that I didn't understand how to use it reading this: > http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/ > crontrigger.html > > - name: take_picture > class: GetUSBCamera > max concurrent tasks: 1 > scheduling strategy: CRON_DRIVEN > scheduling period: 0/30 * * * * * > auto-terminated relationships list: > - failure > Properties: > FPS: 1 > Format: PNG > USB Vendor ID: 0x046d > USB Product ID: 0x082d > > Hope anyone can help me. By the way, is there any place to check current > open/ > known issues and bugs? > > Thanks, > Iyán > > -- > Iyán Méndez Veiga | Physicist > GPG: 0x422E3694311E5AC1 > Web: https://iyanmv.com > > ♫♪.ılılıll|̲̅̅●̲̅̅|̲̅̅=̲̅̅|̲̅̅●̲̅̅|llılılı.♫♪
