DotNetSiemensPLCToolBoxLibrary
DotNetSiemensPLCToolBoxLibrary copied to clipboard
dotnetprojects
NC Var for Sinumerik One
For Sinumerik One the PLC associated is a S7-1200 comparing with the S7-300 that Sinumerik 840D has. NC Tag read works sometimes for One but suddenly throws an exception if the polling is faster than 3 seconds approx. Maybe, this problem is connected with the issue regarding to PUT/GET operations and DB optimized memory.
The same thing happens to me but I don't know where the problem lies, any solution?
@diegoErol The SINUMERIK ONE use a S7-1500. The NCK is almost the same so far. (4.9x <-> 6.xx)
You write that you have problems with NC-VAR. This has nothing to do with the PLC. Communication continues to work normally for me.
What error are you getting exactly? Which NCK Version?
TheNCK is a 6FC5317. What I'm experiencing is that one of each two reads is returning a null value. For example if I define a poll time of 10 seconds:
Pos:3,02785 at time: 00:00:00.0274315
Pos:null at time: 00:00:05.0086867
Pos:3,02784 at time: 00:00:00.0132940
Pos:null at time: 00:00:05.0075245
The response is the same as if define 1 second of pooling time:
Pos:3,02785 at time: 00:00:00.0294128
Pos:null at time: 00:00:05.0086773
Pos:3,02785 at time: 00:00:00.0171700
Pos:null at time: 00:00:05.0075623
If I let run it sequenced:
Pos:3,02785 at time: 00:00:00.0289626
Pos:null at time: 00:00:05.0034212
Pos:3,02785 at time: 00:00:00.0157251
Pos:null at time: 00:00:05.0002274
It seems like the second read is lasting always the same time and return a null value.
I also have this problem with the current NCK version. I will do some tests to see if the problem is on our side or again in the Siemens firmware.
@diegoErol Which NCK Version are you using?
I have contacted Siemens and they have confirmed that this is a fault. I was offered a workaround which I would like to test. At the same time, Siemens wants to investigate the problem further and release a fix in a future version.
I tried the new firmware CNC Version 6.22 HF3 and can confirm that the bug is fixed.
