KepServer and AtlasCopco tags issue

[EL_13480545]

---

It is also likely to cause issues with other third party MES Software, which really does not like reading from, or writing to addresses that are "Bad (Out Of Service)" .

Is there anything I can do to remedy this situation? ie, Is there a way to make sure I can identify situations where Kepware is unable to subscribe via MID51, seperately from situations where Vehicle ID Number is simply blank? Alternatively, can I change how Kepware determines a address is "Bad"

---

I am in the same situation, looking at the same issue. We currently have to restart the KepServer regularly. Having most of the tags from the AtlasCopco default to Bad(Out of Service) Quality leads to huge issues on the OPC-Client side.
Is there a solution for this or a related Knowledge Base or Support Article?

Reference topic for the quote: https://community.ptc.com/t5/Kepware/Question-regarding-PF6000-and-how-KepwareOPC-sets-the-JOB-JOBNUM/m-p/986634#M2551 

Thanks!

[pshashipreetham]

Hi,

Unfortunately, as of mid-2025, PTC/Kepware doesn’t provide a configurable override for “Bad (Out Of Service)” status in the MID driver logic. There is no registry-level override or Quality remapping at the Kepware level either.

If the Atlas Copco PF6000 firmware allows Job Event-Based triggers instead of polling (some versions do), consider event-driven job data transfer to avoid constant polling timeouts.

Short term:

• Enable fallback values

• Add derived diagnostic flags to isolate "bad" states

• Slow down polling

Long term:

• Push Atlas Copco for event-based integration (job complete triggers)

• Monitor tag quality in MES and treat “Bad” tags as retryable, not fatal

Thanks,