Here they are:
Thank you for the report.
I found the problem.
This farmware can be interrupted in the middle and restarted from the point where it was interrupted. This is needed to mitigate possible problem with the camera (black screen, etc). To be able to resume I need to save last position somewhere. I save it in the “Watering Tool”. In your case I was not able to find “Watering Tool” and it caused a problem. I added a check - so now if the tool is not found - I continue without error, but resume will not be possible
Please check 1.0.7
Thank you,
Eugene
Hello @etcipnja thanks for sharing the Farmware
i tried to run the farmware and the movement is perfectly fine, but it never took the photo even once. Here is my logs attached.
I suppose you are using the borescope camera that included in the Farmbot package, could it because i used Raspberry pi camera instead the boroscope camera be the problem?
Can you manually execute sequence TAKE A PHOTO and send me the logs?
I bet this sequence is empty and it is not doing anything
@skuter, sorry, I was asking @Julius
I believe @Julius created ‘TAE A PHOTO’ sequence but left it empty
Hey @etcipnja: Just realized that my webapp is not displaying your MLH and the Selfie despite it says if I install it again already installed and then it display these two super gadgets!!! Do you know if that is just a problem for your farmwares? The calibration and weed detection ones are always avail… -.- @Gabriel any idea?
This is I glitch of the platform. Try to reboot bot by sending reboot command from device page
Same problem different thread…
Yeah, I am back trying to catch up with things …
It was even funny today, I clicked to water, went away, saw that it didn´t move any more but just saw the last log entry pin bla bla on and jumped directly out because I thought it would flood my garden; but it was just the log not logging each message and the script stopped somewhere in between, with closed valve; so there´s still some work ahead with the log messages, as already known…
This was for MLH, sorry for xssing the threads, but as I understood the basis with all is the same, right?
Thanks very much for your good work!!!
Hey Eugene,
I too am catching up with things. I tried the latest version of Selfie with v1.3 hardware. The Farmware took all of the pictures successfully but I could not find the amalgamated selfie picture. Where should I look to find it? I did scour your documentation and the forum, but was unsuccessful.
did you calibrate your camera?
first you need to calibrate the camera so every time you take a picture - it is displayed in Farm Designer tab.
The full selfie will be built there as well from multiple individual shots.
Note: if camera calibration is not accurate - shots will not come together
also, if your plants are tall - you won’t see the nice picture either
Thank you,
Eugene
Hey @etcipnja: mine is not working even with calibrated cam:
Busy Image Watcher trying to upload /tmp/images/rotated_1533379717.jpg 0, 130, 0.17 Aug 4, 12:48pm
2Info Uploading: /tmp/images/rotated_1533379717.jpg 0, 130, 0.17 Aug 4, 12:48pm
1Success Image Watcher successfully uploaded: /tmp/images/rotated_1533379717.jpg 0, 130, 0.17 Aug 4, 12:48pm
2Error CS Failed: [execute_script] - “Farmware failed” 0, 130, 0.17 Aug 4, 12:48pm
2Warn #Farmware<Selfie(1.0.7)> completed with exit status: 1 0, 130, 0.17 Aug 4, 12:48pm
1Error [Selfie] HTTP error 500 {“status”:500,“error”:“Internal Server Error”} 0, 130, 0.17 Aug 4, 12:48pm
2Success #Farmware<take-photo(1.0.2)> completed without errors. 0, 130, 0.17 Aug 4, 12:48pm
3Busy Image Watcher trying to upload /tmp/images/rotated_1533379717.jpg 0, 130, 0.17 Aug 4, 12:48pm
2Info Uploading: /tmp/images/rotated_1533379717.jpg 0, 130, 0.17 Aug 4, 12:48pm
2Busy Beginning execution of #Farmware<take-photo(1.0.2)> 0, 130, 0.17 Aug 4, 12:48pm
2Info [TAKE A PHOTO] - Sequence Executing: TakePhoto 0, 130, 0.17 Aug 4, 12:48pm
2Busy [TAKE A PHOTO] - Sequence init. 0, 130, 0.17 Aug 4, 12:48pm
1Info [Selfie] Executing sequence: TAKE A PHOTO(8680) 0, 130, 0.17 Aug 4, 12:48pm
1Success Movement to (0.0, 130.0, 0.0) complete. 0, 130, 0.17 Aug 4, 12:48pm
1Busy Moving to (0.0, 130.0, 0.0) 0.4, 0, 0.17 Aug 4, 12:48pm
1Info [Selfie] Moving absolute: {‘y’: 130, ‘x’: 0, ‘z’: 0} 0.4, 0, 0.17 Aug 4, 12:48pm
1Info [Selfie] Selfie cache will be saved to tool id 45466 0.4, 0, 0.17 Aug 4, 12:48pm
1Info [Selfie] {‘action’: ‘real’, ‘stepsize’: (380, 500), ‘bottomleft’: (1250, 1250), ‘topright’: (0, 130), ‘default_z’: 0} 0.4, 0, 0.17 Aug 4, 12:48pm
2Busy Beginning execution of #Farmware<Selfie(1.0.7)> 0.4, 0, 0.17 Aug 4, 12:48pm
Any idea?
Your server is giving 500 error. Basically it rejects the commands sent by the farmware
Thank you,
Eugene
I haven’t had a chance to return to this, but the answer is ‘no’ as I had recently upgraded to v1.3 of the hardware. Oversight on my part: the calibration data was erased during the firmware flash. I will try again this evening or tomorrow during the next golden hour.
Same here! As I said before @connor please have a look into deletion of farmwares and calib parameters after firmware flash!
Hoi @etcipnja:
There must be something specific to whatever I am using here. Basically the bot is connected to the internet, no problem. Whenever I start the selfie farmware, it´ll take the first picture but spit out that error when it should take the second error.
So you cannot tell me that the bot always uses just in that millisecond the internetconnection when it is supposed to take the second picture?!
So what else could be the problem?
Cheers
Klim