interesting error getting from the firmware, this was a minor edit of the photgrid lua download
LOG: Starting The Photo Grid
Device is busy
LOG: The Lighting peripheral value is ON (digital)
LOG: Finding home on all axes
Device is idle
Device is busy
Device is idle
Device is busy
Device is idle
Device is busy
LOG: Moving to (0, 0, 0)
LOG: The Lighting peripheral value is ON (digital)
Device is idle
LOG: Taking a grid photo 1 of 52
Device is busy
LOG: Uploaded image: /tmp/images/rotated_1685565899.jpg
Device is idle
LOG: Taking a grid photo 2 of 52
LOG: [take-photo] Problem getting image.
ERROR: 85d01ac9-61f9-44b6-a9c3-8cc37b00667c
Reason(s) for failure: [‘Lua failure’]
LOG: {:noproc, {GenServer, :call, [FarmbotOS.Firmware.UARTCore, {:start_job, %Fa rmbotOS.Firmware.GCode{command: :G00, echo: nil, params: [X: 59.664000000000016, Y: 69
LOG: Failed to execute command: Lua failure
wonder to add a pause between snapshots
- Is that failure repeatable ?
- Is your bot otherwise doing its work with no errors ?
- Do you mean you edited the FarmBot Lua sequence code ?
- If Yes, then does the failure occur when you back out your edit ?
its a random failure
no change in Lua code, just added other steps.
@jturbett if your bot is a Genesis model try a new USB data cable between the Pi and the Farmduino ?
That log shows that FBOS (Erlang) process FarmbotOS.Firmware.UARTCore had terminated unexpectedly.
From the Erlang docs:
noproc
The ServerRef refers to a server by name (it is not a pid()) and looking up the server process failed, or the pid() was already terminated.
At this point it would be useful to see the full console logs from the RPi around this UART error report (preceding and succeeding)
Can you show us that ? ( next occurrence 
)
1 Like
" cleared by testing" has not returned… I think it was solar flares and or reset all connections
2 Likes
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.