Problem with set group of outputs in KukaSIM

Hello,
I have a strange problem with using SIGNAL declaration in Kuka SIM. In the $config.dat file I create my internal signals to use them in the program by their proper name.

$config.dat

SIGNAL OutSig_bBurnerSpraying $OUT[33]
SIGNAL OutSig_bWireCutting $OUT[34]
SIGNAL OutSig_bBurnerCleaning $OUT[35]
SIGNAL OutSig_bAirBlow $OUT[36]
SIGNAL OutSig_bExeVision $OUT[65]
SIGNAL OutSig_bExeRange $OUT[66]
SIGNAL OutSig_bPermissionCell $OUT[97]
SIGNAL OutSig_bDone $OUT[113]
SIGNAL OutSig_bBusy $OUT[114]
SIGNAL OutSig_bWeldingInProcess $OUT[115]
SIGNAL OutSig_bAckReadParam $OUT[121]
SIGNAL OutSig_nActionNumber $OUT[129] TO $OUT[160]
SIGNAL OutSig_nErrorID $OUT[161] TO $OUT[192]
SIGNAL OutSig_nCurrentStep $OUT[193] TO $OUT[224]
SIGNAL OutSig_nCurrentSpeed $OUT[225] TO $OUT[256]
SIGNAL OutSig_nActPosAxis1 $OUT[257] TO $OUT[288]
SIGNAL OutSig_nActPosAxis2 $OUT[289] TO $OUT[320]
SIGNAL OutSig_nActPosAxis3 $OUT[321] TO $OUT[352]
SIGNAL OutSig_nActPosAxis4 $OUT[353] TO $OUT[384]
SIGNAL OutSig_nActPosAxis5 $OUT[385] TO $OUT[416]
SIGNAL OutSig_nActPosAxis6 $OUT[417] TO $OUT[447]
SIGNAL OutSig_nActPosAxis7 $OUT[448] TO $OUT[480]
SIGNAL OutSig_nRowNumber $OUT[481] TO $OUT[512]
SIGNAL OutSig_nColNumber $OUT[513] TO $OUT[544]
SIGNAL OutSig_nBaseCheckingNum $OUT[545] TO $OUT[576]
SIGNAL OutSig_nCurrentWeldJoint $OUT[577] TO $OUT[608]

The problem is in one of the variables OutSig_nActionNumber. When I try to set its value I get an error like:

KR 150 R2700-2 (integrated) Simulation was paused due to an interpreter stop.
KR 150 R2700-2 (integrated): The variable OutSig_nActionNumber is readonly. 

Here is a fragment of the program where I set the variable:

   OutSig_bDone = FALSE
   OutSig_bBusy = FALSE
   OutSig_nErrorID = 2
   OutSig_nActionNumber = 7

But when I want to set SIGNAL on the next variable OutSig_nErrorID everything is fine. Why is this happening?

Best Regards

Kamil

I disabled the signals where the addressing matched mine. But the error still occurs.
Which addresses should be chosen for mapping so that they do not conflict with system signals?

I did everything you wrote after the previous answer of the colleague above. I talked to Kuka support, it turns out that the problem is that KukaSIM, despite the change in the $machine.dat file, still generates robot data and this is protected from writing. You can disable the RobotDataGeneration option and indicate the path to the folder where this file will be and check, but unfortunately this did not work either. It is most likely KukaSIM's fault, it would work in combination with OfficeLite.