FAQ1008: How to enable VT-x support only (without enabling VT-d)
Enabling VT-x without enabling VT-d is only useful for test purposes as no physical devices which need DMA support will work then. This may be usedful for example to determine if SMIs can be suppressed.
VT-x only can be enabled using the following config file entry:
[Vmf]
"VtAllowed"=dword:5
Last update on 2021-03-15 by Realtime Support Team.
FAQ1007: How to get an update for the RTOS32Win, RT-Win and EC-Win(RTOS-32) products?
Request an update from acontis through the following site: https://developer.acontis.com/ethercat-latest-versions.html
You will get the latest version then from acontis.
Check the On Time RTOS-32 version which is required for the update.
If necessary, update your On Time RTOS-32 version to this version. Do not use a different version, this is not supported by acontis.
Last update on 2020-12-17 by Realtime Support Team.
FAQ1006: How can I create my own setup?
Please checkout chapter 15 Appendix C - "Installation" of RtosVM-UserManual.pdf.
Last update on 2020-12-17 by Realtime Support Team.
FAQ1004: How can I generate an Error Report using the System Manager?
The following steps have to be executed to generate the error report:
- Start System Manager
- Load the Virtual Machine
- Ignore the error message (e.g. cancel), do not stop the System Manager or shutdown Windows
- Generate the error report
Last update on 2020-12-17 by Realtime Support Team.
FAQ1003: How can I get a virtual dongle to unlock my target?
Please checkout the following document RtosVM-UserManual-Licensing.pdf.
Last update on 2020-12-17 by Realtime Support Team.
FAQ1002: Can I use hyperthreading?
It can be enabled, but it is not recommended as the jitter will be significant higher and real-time behavior in most cases is not acceptable.
Last update on 2020-12-17 by Realtime Support Team.
FAQ1001: How can I determine, if my hardware is capable to run Real-time applications?
Please checkout our PC-Hardware and Real-time Optimization section.
Last update on 2020-12-17 by Realtime Support Team.
FAQ1000: Error 0x0022270B - Timer frequency measurement delay limit reached
The measuring periods to determine the timer input frequency varied above a minimum.
In case of problems regarding timer period (e.g. clock drift between master and slaves) this message indicates a possible reason. It can be ignored in other cases.
The message can be disabled using the following config file entry:
[Vmf]
"TimerMeasureDelayLimit"=dword:0
Disabling the message as no negative side effects.
Last update on 2021-03-15 by Realtime Support Team.