PINE crashes during multi-key-frame-timelapse in slave mode.
during today's testing session of my 3-axis BFM bundle (which I am very happy with, so far, by the way 😉) I came across a potential bug in PINE.
I noticed, that when shooting a shoot-move-shoot timelapse sequence with 3 or more key-frames in slave mode, PINE stops moving to the next interval, once the sequence reached the frame just before the second key frame i.e. externally released camera keeps shooting but the motion control freezes entirely. If the PINE-App is connected to the controller at my external device during this procedure, the App crashes, i.e. exits/shuts itself down without user interaction and home-screen is visible.
Here is the setup that I was testing with:
- External devices: iPhone (8) and iPad Air (2), both running on latest iOS
- Motors: BFM 14:1 + 2x NT Single Axis
- PINE APP: iOS v3.0.3
- Controller: PINE R, firmware v3.0
- Camera: Sony a7III; for slave mode: wired camera to AUX-inupt of PINE via hot shoe adapter and synch-cable
- Camera release: QDSLRDashboard-App, or camera's internal intervalometer (interval set to 5s).
- Power bank: XT-20000QC2, input voltage: 18-19V
This is the most simple test scenario that I have observed the error with:
- 1 motor
- Key frame 1: position 0
- Key frame 2: position 100 (5 frames)
- Key frame 3: position 0 (10 frames)
- The crash occurs after frame 4 has been captured by the camera
These are some further observations that I have made:
- The error occurs, whether the external devices are connected or not.
- The amount of involved motors does not matter.
- The error occurs, regardless which type of camera release I used.
- The error does NOT occur in regular mode (even for the exact same sequence), i.e. PINE controls camera release
- When set to slave mode, PINE performs the movement-test of the multi-key-frame sequence without errors.
- After the error occurred, reconnecting to PINE is possible without the necessity of re-starting the controller. The timelapse module of the app does not state that there is an active sequence and asks whether to re-load the key-frames, or start from scratch. The old key frames are loaded correctly.
My preliminary conclusion is, that the error is independent of the used camera, how the camera is released, or the motor type and therofre caused by a bug in the PINE controller, only. Can someone reproduce the error with a different setup? This would solidify the mentioned theory.
To help out the BFM development team to find a cause/solution, I have attached the bug analysis report that my iPhone generated for the PINE-App during one of my tests. Just let me know if you need anything else!
I am really curios about the cause of the error, and would be happy about a solution.
Best regards and stay healthy,