Skip to main content
Skip table of contents

pmc 2025.02v7.17.35 (117.17.35)

Feature Summary

  • Support more than 2 PMCs in emulation mode

  • Support RFID scan for M3-25

  • Add group motion command

  • Add reboot option to TCP/IP command

  • Stop both inject noise and force mode after Stop XBots

  • Improve RFID reading performance

Bug Fixes

  • Fixed issue that absolute ID scan with mixed XBot types will fail

  • Fixed issue that XBot may collide with other XBots during border crossing

  • Fixed issue that phantom obstacle XBot is present from neighbor

  • Fixed issue that real time ID mode with logging will cause border crossing XBot disappear

  • Fixed issue that XBot will disappear from both PMCs during the transfer

  • Fixed issue that accident XBot may get stuck at detection

  • Fixed issue that XBot may not be received from border in large system

  • Fixed issue that intersection zone doesn't block groups sometimes

  • Fixed issue that group XBots don't take up a free spot in intersection zone when unbonded

  • Fixed issue that XBots lose their stereotype when switching to absolute ID

  • Fixed issue that XBot will disappear after collision in force mode

  • Fixed issue that system doesn't distinguish between different XBot types for stereotype 255

  • Fixed issue that XBot doesn't assign default stereotype 255 to auto-loading XBot

  • Fixed issue that zone activation will get aborted if it's already activated

  • Fixed issue that motion command returns aborted signal after crossing border

  • Fixed issue that system boundary stops working after auto-loading

  • Fixed issue that accident info is not transmitted across borders

  • Fixed issue that dynamic fence of detection remains after accident recovering

  • Fixed issue that stereotype is swapped after auto-loading

  • Fixed issue that sending invalid XBot ID to move when spacing XBot

  • Fixed issue that XBot may get stuck in rotation sometimes

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.