NonBoolean Receiver - proceed for truth

[[Do...]]

Hi all,
We've recently swapped out an old PC with a new one that has Calypso 2021 installed. The machine has now encountered this error message "NonBoolean Receiver - proceed for truth".

Has anyone seen this message before and/or know how to address it? I did not see anything on the forums about it, but I did find an article about it here : https://carl-zeiss-industrial-metrology ... -for-truth

This tutorial did not correct the issue. An interesting thing I noticed was that the error report states that the machine OS is Windows 10, however, with the new PC we are running Windows 11. I believe this may have something to do with it.

Here is the full error report:

SYSTEM STATE
CALYPSO
Inspection: 6141403_RevA_Final_658
Creation software version: 5.8.12
Date and time: #(24 January 2024 09:03:47)
Actual characteristic: Perpendicularity Perpendicularity2
Actual feature: Path Path CNC End Park Position
Creation DME: CON_2014_G2
Hostname: Hil-D-28D5PZ3
Mancnc active: false
Navi mode: nil
Run mode: manuel
OS Windows 10 Enterprise win32 V6.2 nt i386 ucs2
CMM-OS
Actual configuration: 2.0mm Probe
Actual stylus: Down
fwObject: Zeiss.CMMOS.OMControlBehaviourC99FW20
ID chain CS: _.63X63_91X91_27,001RHOL6,001C616J
IFCpresent: false
ncDisplayStatus: 22-----#--.-----
PICS A input: +0
SDO version: 6.6.8.1
Sensor: VASTXT
TCO pending: 0
PiWeb Reporting
PiWeb reporting version: 7.8.19.0
PDF Merger: Not installed
STATUS WINDOW
1/24/24 9:02:16 AM = = = = = = = = = = System Start up = = = = = = = = = =
1/24/24 9:02:16 AM 658: Initializing
1/24/24 9:02:37 AM 658: CAA Correction active
1/24/24 9:02:37 AM 658: Temperature correction for the X axis will be processed internally
1/24/24 9:02:37 AM 658: Temperature correction for the Y axis will be processed internally
1/24/24 9:02:37 AM 658: Temperature correction for the Z axis will be processed internally
1/24/24 9:02:37 AM 658: Temperature stylus not available or inactive
1/24/24 9:02:37 AM 658: Temperature sensor for table does not exist or is ignored
1/24/24 9:02:37 AM 658: CMM Ready
1/24/24 9:02:41 AM 658: Connect from Client.Addr: #(127 0 0 1) Port.Nr: 55012 with Zeiss KMG - Server
WHERE I AM
load startLoad N:\CMM\Calypso files\Autorun Master Program Files\6141403_RevA_Final_658


Any help would be greatly appreciated.

Cheers,
Don

NonBoolean.png

[[DW...]]

Did this happen right away after the swap, or did it occur after successfully running a program once or twice? What was the previous computer's version of Calypso?

I have limited knowledge of computer programming but do understand the boolean error is telling you that it is looking for a TRUE or FALSE return for the objects listed (change position symbols, etc). Perhaps there is too much of jump from the creation version to 2021? Shouldn't happen, but I have heard of it happening when updating from much older versions.

To test that guess, create a similar program in 2021 to the one giving you errors and see if it still does it.

[[Mi...]]

Does the new PC have the network connection configured correctly?

You need to set the CMM connection's IP manually to 192.4.1.199

[[Do...]]

Please sign in to view this quote.

The issue occurred a few weeks after the swap on a program that was written and ran multiple times in Calypso 2021. Our previous machine was running Calypso 2017 on Windows 10.

When I open a program, I can view and edit features as normal, but circular features generate the error and effectively locks up the machine. I think you're on the right track regarding object symbols. Perhaps there was a slight change in Windows that is causing Calypso to look for a certain object that has been replaced or vice versa.

I also confirmed that the IP information on the machine was correct. Initially when we set up the new machine we had an issue where Calypso was unable to write to the hosts file due to IT restrictions. Once we had cleared that up the machine was working fine for a couple of weeks before we got this NonBoolean error.

We've put in a ticket with Zeiss about the issue as well so hopefully we get this addressed soon.

[[Do...]]

Update.
The Zeiss technician was unfamiliar with this particular issue, apparently this is not common.

Left to our own devices, we began a series of tests to try to troubleshoot the problem.

1. Power cycle PC and CMM and try to open the same program. Issue persisted.
2. Open a different program that had been written in Calypso 2021 (testing if the error was program specific). Issue persisted.
3. Open a program that was written in Calypso 2017 (testing if the error was version specific). Issue was intermittent.
4. Created a new machine tab in Calypso 2021 (testing if the error was configuration specific). This seems to have resolved the issue. All programs tested functioned as normal.

Normally, we upgrade Calypso on the same PC and then remove the older version. In this case though, we installed only Calypso 2021 on the new PC and then we copied over the config file from the old PC that was running 2017. I believe that there must be a missing or corrupt file someplace in this method. I will try to track down what exactly it was, but for now things seem to be working as intended.

Cheers,
Don

[[DW...]]

Thank you for the update. It helps someone in the future searching for an answer on here.