Сannot read field "jobPlacement" because "plannedPlacement" is null

[Khammed Guseynov]

Hello! An error occurred during processing: Cannot read field "jobPlacement" because "plannedPlacement" is null
Message log:
2025-12-10 21:18:12.271 ReferencePnpJobProcessor DEBUG: Current rank is 0. Blocked up to rank 10
2025-12-10 21:18:12.272 ReferencePnpJobProcessor$Plan DEBUG: Placements sorting using PartHeight completed in 0ms
2025-12-10 21:18:12.272 ReferencePnpJobProcessor$Plan DEBUG: plannedJobPlacements [R24, DD4, DD3, DD2, DD1, DA2, DA3, DA9, DA8, DA7, DA6, DA5, DA4, C10, VD4, VD2, VD1, DA1, L1]
2025-12-10 21:18:12.272 ReferencePnpJobProcessor$SimplePnpJobPlanner DEBUG: No optimization possible: R24 rank 0
2025-12-10 21:18:12.273 ReferencePnpJobProcessor$SimplePnpJobPlanner DEBUG: Optimized: DD2 rank 0 from 14
2025-12-10 21:18:12.273 ReferencePnpJobProcessor$SimplePnpJobPlanner DEBUG: No optimization possible: R24 rank 0
2025-12-10 21:18:12.307 MessageBoxes DEBUG: Job error: java.lang.NullPointerException: Cannot read field "jobPlacement" because "plannedPlacement" is null

This is the second time this has happened. What is the error? How can it be fixed?

[Toby Dickenson]

Hi, this is an interesting error message. Thank you for testing the test branch.

Please can you confirm exactly what version you are running.

A full copy of your error log would be useful too. The extract you provided was interesting, but I hope the full log contains more clues.

This is the second time this has happened.

Does that mean you ran two jobs and they both failed? Or you have had two errors out of thousands of jobs?

Toby

[Khammed Guseynov]

Currently, it's 2.5_2025-10-11_16-19-43.5c21e7b.

The previous error occurred in OpenPnP version 2024-08-17_13-11-48.6572fa6.

Since the first error, I've already completed about 100 tasks.

To finish placing components on the board, I did the following: stopped the job, disabled the remaining unplaced components, enabled a few positions, and started the job. Then I did the same again, then the remaining components.

Afterwards, I noticed that one 0603 SMD resistor from the power supply was used too much. I started checking the resistors placed on the board and discovered that this resistor was placed incorrectly instead of another 0603 resistor (which has a different resistance value).

I've attached the full log.

среда, 10 декабря 2025 г. в 22:34:24 UTC+3, to...@tarind.com:

[Toby Dickenson]

Again, thank you for the report.

I have just merged a fix for this. Details are here: https://github.com/openpnp/openpnp/pull/1924

If you are running openpnp from source, you can pull the test branch and try the fix right away. If you are using a build from openpnp.org then you can track progress of the build here: https://github.com/openpnp/openpnp/actions/runs/20115111608

And when it is built you can download here: https://openpnp.org/test-downloads/

I am 99% sure that the bug I fixed is the same one causing your problem, but it would still be great to have some confirmation if this fixes the issue for you.

Toby

--
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 visit https://groups.google.com/d/msgid/openpnp/7da6c179-172e-4aff-abdf-12dccb8bf4c0n%40googlegroups.com.