3/6/2015 8:31 AM | |
Joined: 9/8/2009 Last visit: 7/17/2023 Posts: 1410 Rating: (150) |
Your monitoring doesn't track those signals in the program, therefore no conclusions from that point can be made. |
3/6/2015 12:23 PM | |
Joined: 8/31/2013 Last visit: 5/26/2024 Posts: 607 Rating: (41) |
check the CPU setting of process image partition of the normal and safety inputs. |
Warm Regards |
|
3/9/2015 10:05 AM | |
Joined: 3/24/2009 Last visit: 6/20/2023 Posts: 535 Rating: (112) |
Dear eizdenczy, is this the only write-access to M440.0 (check the cross-references)?
|
3/18/2015 1:13 PM | |
Joined: 4/11/2012 Last visit: 12/4/2023 Posts: 176 Rating: (34) |
Also check MW440 and remember that indirect addressing of the memory bit won't appear in the cross-referece list. Consider the enviroment, is it possible that 3:rd party is writing to the memory bit? (UI or computer program communicating with the PLC) As the M4445.0 state is changed in a similar manner to the M440.0, I would guess that there is additional source that's writing to the memory bits 440+ |
3/18/2015 4:25 PM | |
Posts: 5 Rating: (0) |
No other place in the program to write to the memory bit. |
3/21/2015 10:34 AM | |
Joined: 9/8/2009 Last visit: 7/17/2023 Posts: 1410 Rating: (150) |
Why don't you change M bits to DB bits and make sure nowhere else is accesing those bits. |
Follow us on