Freeze of UI when updating Issues and Sollutions

56 views
Skip to first unread message

Fabian Kropp

unread,
Jan 31, 2023, 1:30:05 PM1/31/23
to OpenPnP
Hi,

I just figured after I spent a couple of minutes to update issues and solutions, after I try to refresh, OpenPNP is completely stuck.
Cannot open any of the menus (like saving the machine configuration to not having to do all the config I had done before)

Have to kill it.

Using Ubuntu linux.

BR

Fabian 

jbasia

unread,
Feb 1, 2023, 6:39:51 AM2/1/23
to OpenPnP
I had to do some kills with LinuxCNC (Debian 10 I believe). OpenPnP got stuck in 'test camera'. I moved on to Windows 10 since, and no freeze so far.

I always do specific backups of the 4 XML files. So I can use them as a starting point without typing in case I start again from zero.

mark maker

unread,
Feb 1, 2023, 6:59:18 AM2/1/23
to ope...@googlegroups.com

Can you sent the log of when that happened? Note, OpenPnP keeps the last 100 logs, so you should be able to find it.

Look here:

https://github.com/openpnp/openpnp/wiki/FAQ#where-are-configuration-and-log-files-located

_Mark

--
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/aa84f6dd-8111-4ccd-b5e8-2a9c520e4841n%40googlegroups.com.

Fabian Kropp

unread,
Feb 4, 2023, 3:21:28 AM2/4/23
to OpenPnP
finally it happened again today (before it once crashed somewhere inbetween)
Logfiles of both occurrences are attached 

OpenPnPStuck_random.log
OpenPnPStuck_InS_04022023_0807.log

mark maker

unread,
Feb 4, 2023, 7:07:10 AM2/4/23
to ope...@googlegroups.com

Hi Fabian,

Unfortunately, I don't get any conclusive evidence from the logs.

What I see it this:

  1. There are repeated vision problems with the nozzle tip calibration.

    2023-02-03 10:52:22.119 AbstractMachine TRACE: Exception caught, executing pending motion: java.lang.Exception: Subject not found.

    I recommend you update to the latest test version of OpenPnP, then disable the calibration on all the nozzle tips, do not forget to press Apply, and let Issues & Solutions propose the right calibration settings. This now includes replacing the pipeline with the self-tuning (Circular Symmetry) stock pipeline.

    You can also test the new Auto-Detection Next button, which would help me 😁:

    See also: https://github.com/openpnp/openpnp/pull/1516

  2. I see a strange Z Soft Limit:

    2023-02-03 10:29:56.466 AbstractMachine TRACE: Exception caught, executing pending motion: java.lang.Exception: Can't move Z to -1.000mm, lower than soft limit 0.000mm.

    Please read these two articles and report back.

    https://github.com/openpnp/openpnp/wiki/Machine-Axes#a-word-about-z-coordinates
    https://github.com/openpnp/openpnp/wiki/Kinematic-Solutions#special-considerations-for-z-axes

    If this is some kind of "Lumen recommendation", we need to correct it, before too many people start adopting that.

  3. Marlin M115 seems to report all kinds of capabilities:

    2023-02-03 10:37:50.040 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << FIRMWARE_NAME:Marlin bugfix-2.0.x (May 24 2022 15:57:56) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:Index Pick and Place EXTRUDER_COUNT:0 AXIS_COUNT:6 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
    2023-02-03 10:37:50.041 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:QUOTED_STRINGS:1
    2023-02-03 10:37:50.041 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:SERIAL_XON_XOFF:0
    2023-02-03 10:37:50.041 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:BINARY_FILE_TRANSFER:0
    2023-02-03 10:37:50.041 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:EEPROM:0
    2023-02-03 10:37:50.041 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:VOLUMETRIC:0
    2023-02-03 10:37:50.041 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:AUTOREPORT_POS:0
    2023-02-03 10:37:50.042 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:AUTOREPORT_TEMP:0
    2023-02-03 10:37:50.042 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:PROGRESS:0
    2023-02-03 10:37:50.042 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:PRINT_JOB:1
    2023-02-03 10:37:50.042 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:AUTOLEVEL:0
    2023-02-03 10:37:50.042 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:RUNOUT:0
    2023-02-03 10:37:50.042 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:Z_PROBE:0
    2023-02-03 10:37:50.043 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:LEVELING_DATA:0
    2023-02-03 10:37:50.044 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:BUILD_PERCENT:0
    2023-02-03 10:37:50.044 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:SOFTWARE_POWER:0
    2023-02-03 10:37:50.045 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:TOGGLE_LIGHTS:0
    2023-02-03 10:37:50.045 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:CASE_LIGHT_BRIGHTNESS:0
    2023-02-03 10:37:50.046 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:EMERGENCY_PARSER:0
    2023-02-03 10:37:50.046 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:HOST_ACTION_COMMANDS:0
    2023-02-03 10:37:50.046 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:PROMPT_SUPPORT:0
    2023-02-03 10:37:50.046 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:SDCARD:0
    2023-02-03 10:37:50.046 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:REPEAT:0
    2023-02-03 10:37:50.046 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:SD_WRITE:0
    2023-02-03 10:37:50.046 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:AUTOREPORT_SD_STATUS:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:LONG_FILENAME:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:LFN_WRITE:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:CUSTOM_FIRMWARE_UPLOAD:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:EXTENDED_M20:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:THERMAL_PROTECTION:1
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:MOTION_MODES:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:ARCS:1
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:BABYSTEPPING:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:CHAMBER_TEMPERATURE:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:COOLER_TEMPERATURE:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:MEATPACK:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << Cap:CONFIG_EXPORT:0
    2023-02-03 10:37:50.047 GcodeDriver$ReaderThread TRACE: [serial://ttyACM0] << ok

    That's actually OK, but the firmware detection facility in OpenPnP might be too simplistic for that, I'll look into it.

    Is there any chance you are pressing Find Issues & Solutions while the machine is in the middle of a calibration run? That could perhaps explain it in that case. Still a bug that I'd need to fix, but not doing it would probably help for now. 😅

_Mark

Fabian Kropp

unread,
Feb 4, 2023, 8:15:06 AM2/4/23
to OpenPnP
Hi,



ma...@makr.zone schrieb am Samstag, 4. Februar 2023 um 13:07:10 UTC+1:

Hi Fabian,

Unfortunately, I don't get any conclusive evidence from the logs.

What I see it this:

  1. There are repeated vision problems with the nozzle tip calibration.

    2023-02-03 10:52:22.119 AbstractMachine TRACE: Exception caught, executing pending motion: java.lang.Exception: Subject not found.

    I recommend you update to the latest test version of OpenPnP, then disable the calibration on all the nozzle tips, do not forget to press Apply, and let Issues & Solutions propose the right calibration settings. This now includes replacing the pipeline with the self-tuning (Circular Symmetry) stock pipeline.

    You can also test the new Auto-Detection Next button, which would help me 😁:

    See also: https://github.com/openpnp/openpnp/pull/1516

I already use that, maybe not the top latest. I will try with the latest update.
 


  2. I see a strange Z Soft Limit:

    2023-02-03 10:29:56.466 AbstractMachine TRACE: Exception caught, executing pending motion: java.lang.Exception: Can't move Z to -1.000mm, lower than soft limit 0.000mm.

    Please read these two articles and report back.

    https://github.com/openpnp/openpnp/wiki/Machine-Axes#a-word-about-z-coordinates
    https://github.com/openpnp/openpnp/wiki/Kinematic-Solutions#special-considerations-for-z-axes

    If this is some kind of "Lumen recommendation", we need to correct it, before too many people start adopting that.
I started calibration from scratch without any "special recommendation" just following the Issues & Solutions - which is fantastic btw. -.
That could be the case, sometimes you cannot determine easily if the calibration run is finished.
I will try to remember that. Is there any chance to identify that in the logs? (then I could sort out duplicate issues)
 
Thank you so much for all the great support :-)

Fabian
Reply all
Reply to author
Forward
0 new messages