bernard_arinax Posted October 18, 2022 Share Posted October 18, 2022 We are unable to make a PVT move with Coord[1].SegmoveTime=0 on PowerBricks with ARM processor with firmware version 2.6.1, The result of the start of the first PVT move (even a single motor involved, whatever the speed/duration) is a direct crash of the powerBrick software: we have no time to see any error on the display: we lose communication, and subsequent pings fail. There is no whatchdog error on the controller, but only a hard restart solves the problem. The issue occurs if we start our motion program from the IDE or another application. The same program works on our PowerBricks with PowerPC processors (older firmware). If we use SegMoveTIme=1, there is no crash but our program is not working properly. Indeed, we must disable SegMoveTime because we need very accurate positioning (no interpolation beween PVT segments) with variable synchronization at some passage points. If we reduce SegMoveTime to a very small value, our program accuracy gets better, but at some point we get RunTimeError. I attached our CPU typical load, just in case it helps. Is this major issue known? Please suggest a solution. Quote Link to comment Share on other sites More sharing options...
Sangmo Posted October 25, 2022 Share Posted October 25, 2022 (edited) I think this issue has been fixed in firmware version 2.7.0.0. This problem only occurs in version 2.6.1.0, other versions have no problem. You can update your PMAC to 2.7.0.0 via the attachment. Edited November 19, 2022 by Sangmo 1 Quote Link to comment Share on other sites More sharing options...
bernard_arinax Posted November 15, 2022 Author Share Posted November 15, 2022 Thank you so much Sangmo, you saved me a lot of time ! I confirm that the 2.7.0.0 fixes the problem. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.