Machine not working after upgrading from 5.5.12 to 5.8.1

Troubleshooting the Pocket NC
#1

I’ve upgraded my pocketnc v2-10 from software version 5.5.12 to 5.8.1 this morning.

However, after rebooting I get this error:
Named parameter #<_ini[penta_features]probing> not defined

When I try to probe, I get this additional error, and probing does not work as this error keeps popping up:
Named parameter #<_ini[penta_features]v2_tcpc> not defined
After reverting back to 5.5.12 it works fine again.
How can I fix this?

Greetings -James

Screenshot 2025-01-13 at 11-38-05 Penta - Kinetic Control UI

#2

Hi James,

Thanks for reporting this issue. I’ll look into what is going on.

When you say you try to probe, are you talking about measuring your tool length, or do you have a probe for measuring stock or part features?

-John

#3

Hi John,
Thank you,
Sorry, I mean measuring my tool length :slight_smile:
-James

#4

I wasn’t able to reproduce this issue. Do you have any custom modifications to your configuration on your machine?

#5

I don’t have any custom modifications. Serial number is 1224, it was upgraded to kinetic control a couple of years ago.

#6

Thanks for the extra information. I am now able to reproduce the issue. It looks like there is a bug for older machines like yours. I’ll try to get a fix out for it by the next release. We should be getting a new release out within the next week or so.

#7

I believe you could work around this issue by manually adding a couple configuration options, [PENTA_FEATURES]V2_TCPC=1 and [PENTA_FEATURES]PROBING=0, in the Config tab > Server tab > Machine Config panel:

Screenshot 2025-01-13 at 3.19.27 PM
Screenshot 2025-01-13 at 3.19.27 PM3620×1208 172 KB

We’ll set these automatically in the next release.

#8

I tried to upgrade to 5.8.1 again with the two configuration options as suggested:
[PENTA_FEATURES]V2_TCPC=1 and [PENTA_FEATURES]PROBING=0
After rebooting, the first error message that now pops up is:
“Errors
Parameter file name is missing”
At the left, bottom, it says it is “connected”
However, I cannot home, or do anything.
There is no x,y,z,a or b.

Screenshot 2025-01-14 195713
Screenshot 2025-01-14 1957131778×1086 82.2 KB

When I try homing, it gives this error:
“Errors
Cannot home while running a program or MDI command”
Clicking reset at the bottom has no effect.
Rebooting takes a long time, about 5 minutes.
After about waiting for 10 minutes, it was still showing as ‘disconnected’
So, I reverted back to 5.5.12 :slight_smile:

#9

Ok, thanks for testing that. I’ll keep you posted about the next release.