2 more notes: 1. The message reported appears on UC 18 (despite it saying UC 16) 2. The issue is still present in UC 22, but it doesn't hammer the CPU as much as it does on UC18
2 more notes:
1. The message reported appears on UC 18 (despite it saying UC 16)
2. The issue is still present in UC 22, but it doesn't hammer the CPU as much as it does on UC18