2 ms·
Q: What is the Beckhoff "variety of options" for communicating to the hard real-time side from (userspace?) soft-real-time side? As far as I know, all communica
by colorado-anon-6 7y ago
Q: What is the Beckhoff "variety of options" for communicating to the hard real-time side from (userspace?) soft-real-time side? As far as I know, all communication goes through ADS which is handled between cycles and isn't guaranteed to be even close to soft-real-time if the PC is busy. I'm genuinely interested if I'm missing a communication path here... I leveraged R3IO in TwinCAT2 to externally clock data into the task images from userspace for "soft-real-time" approx 10ms cycles , but TwinCAT3 droppped that option... My experiments and working with Beckhoff resources showed that ADS can't make that cyclic guarantee. (soft-real-time motion control application running in user-space)
- cashsterling 7y agoBeckhoff now also offers a direct TCP/IP socket interface (for extra money, of course) if ADS doesn't cut it for you application. You'd have to ask Beckhoff or test for yourself. Depending upon whats going on on PC level, I think sub 10ms round trip is fairly typical. I should think the TCP/IP interface will be PLC cycle-time limited (PLC cycle time of 1ms is typical) plus some fractional overhead from the TCP/IP processes themselves.