Left ArrowBack to discussions page
MarioMario Posts: 3 Apprentice
Has anyone ever had some teach screen freeze problems ?
This append some times (not everytime) when operator needs to access to the robot teach pendant.
Then we have to shut down the controller in order to have access to the teach.

The robots communicate with Siemens PLC by Profinet.



  • matthewd92matthewd92 Posts: 889Founding Pro, Tactile Sensor Beta Testers Handy
    We are having that issue with E-Series robots, we have never had it with any of the CB3 robots running polyscope 3.9 or older, haven't upgraded any production robots to 3.10 yet.  We will be installing 5.4 shortly on the robots that have the issue to see if that helps
  • Kaleb_RodesKaleb_Rodes Posts: 59Founding Pro, Partner, Beta Tester VIsion 1.1 Program, Tactile Sensor Beta Testers, Beta Tester Camera URCap 1.2.0-beta Handy
    We've also seen it in the e-Series only. Our e-Series teach pendant acquired a pink tint that overlayed on the screen in addition to the screen freezing for a short time. We replaced it and haven't had any issues since.
    Kaleb Rodes
    Applications Engineer
  • MarioMario Posts: 3 Apprentice
    Thank you for your answers.  The controllers are CB3 Series and we use Polyscope 3.9.1.  The problem is probably caused by the
    complex programming (many scripts) and the exchanges with the PLC which probably cause an overload of the system. The problem occurs on differents robots, not only one...

  • matthewd92matthewd92 Posts: 889Founding Pro, Tactile Sensor Beta Testers Handy
    That's definitely possible but I would be surprised if that is the issue on a CB3, try downgrading to 3.8 software and see if the issue goes away.  We operate very complex programs on 95% of our robots with up to 30 background threads running, with not only a Profinet connection to the PLC but multiple XMLRPC connections to servers both on and off the robot, modbus connections and have all of that going all at once.  We have never really experienced much performance issues on the CB series but we can bring an e-series to a standstill.  We can run identical programs on side-by-side robots, one a CB and one an e-series, the CB will plug right along, no issues, the e-series will either freeze up or throw a hard fault that the process got too far behind real-time.

    We have definitely had to learn to be much more efficient with the code running on the e-series robots and that is without a ton of external fieldbus protocols, simple modbus connection and 1 xmlrpc server that is hosted off the robot.
  • MarioMario Posts: 3 Apprentice
    Thank you @matthewd92 !!!
    The first time we had this problem  POLYSCOPE 3.5 was installed.  We upgraded version per version to see if the freezes disappeared. It's very easy to create a screen freeze on a CBSeries. I have experimented this by sending messages on the event log screen and then play to enable and desable the key that display user messages. When the program sends too many messages to the log, this action causes a freeze of the screen when the windows is activated and it takes a few minutes to have access. But our problem comes from something else...
  • matthewd92matthewd92 Posts: 889Founding Pro, Tactile Sensor Beta Testers Handy
    If you can get the CB to freeze on log messages then you’d just “kill” an e-series. We stream a lot of log messages as our programs are script based and funny enough we have issues in the e-series when we start streaming low level trace events but the cb series just hums along with the same level of messages. 
Sign In or Register to comment.
Left ArrowBack to discussions page