Version 8.1 - Released 14th October 2019

What’s new

  • ‘Cross Belt Sorter’ performance improvement: the way events ‘OnBeltBlocking’ and ‘OnBeltUnblocking’ are fired by the simulation engine has been improved. This modification highly decreases the number of events in the queue. [ref 16631]

  • FINS driver: previously, the driver was writing only when something had to be written. We introduced two new parameters: [JIRA Sym3-260] [ref 16015]

  • TCP server. For machine with multiple IP addresses, it is now possible to specify which IP to use. See documentation for more information. [JIRA Sym3-274] [ref 16016]

Bugs fixed

  • Operator: The ‘Speed tuning dialog’ was not working, the dialog didn’t list any conveyors. This has been fixed. [SUPPORT 1561] [ref 17123]

  • Operator Client: The event grid was not refreshed with latest events. This occured when the number of events in database > MaxEvents set on client side [ref 17091]:

  • Encoder: for the cross belt sorter: the encoder value didn’t match. [JIRA Sym3-326] [ref 16623]

  • Encoder: When accelerating at the start of the first simulation, the encoder was looping back at half the MAX value setting. [JIRA Sym3-327] [ref 16622]

  • Mitsubishi driver: the option ‘Enable Profiling’ in the properties of the datasource was not saved in project. [JIRA Sym3-328] [ref 16591]

  • Mitsubishi driver: The driver was not reconnecting after the PLC was disconnected. [JIRA Sym3-330] [ref 16620]

  • Conveyor: An issue with blockage has been fixed. [JIRA Sym3-295] [ref 16018]

  • Sym3 Integrator was crashing when starting simulation and record at the same time. [SUPPORT 1547] [ref 16715]

  • A crash has been fixed when using the function ‘SetDestination’ in simulation script. Previously passing an empty string to this function was crashing Sym3. [ref 16866]

  • OPC-UA: A bug has been fixed: sym3 was using wrong path for a tag. [JIRA WEB-5] [ref 16623]