The PTC Community is on temporary read only status in preparation for moving our community to a new platform. Learn more here
Solved! Go to Solution.
Thanks for the help and comments. This problem solved itself. The output started showing up in the logs as expected. Maybe the system needed a reboot to flush whatever was causing the block. I do use this output for debugging only so any Java errors are matched to what values variables have and what robots I am in. Thanks again.
Robert.
Hi @rsutherland,
I have tested the same, and the sysout statements are not being printed in the BGMS logs.
There could be multiple reasons for this, and PTC would be able to provide clarification.
However, using System.out.println is not recommended. It is always advisable to use proper logging mechanisms such as Log4j.
FYI, I tested System.out.println("****** testing 1 2 3 ..."); in an expression robot in Windchill 13.1.2.0 and it does write to BGMS log.
I know you're on 13.0 but I thought knowing how it behaves in 13.1 would be worth knowing.
Hi @rsutherland,
I wanted to see if you got the help you needed.
If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation.
Thanks,
Anurag
Thanks for the help and comments. This problem solved itself. The output started showing up in the logs as expected. Maybe the system needed a reboot to flush whatever was causing the block. I do use this output for debugging only so any Java errors are matched to what values variables have and what robots I am in. Thanks again.
Robert.
