-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: minimum requirements #345
Comments
No, the minimum requirements have not been determined as far as I know. It's also going to depend quite a bit on system utilisation: an RPi with no other tasks than the driver can run it quite successfully, but an i7 with 32GB of ram running 30+ nodes and Gazebo may have trouble sustaining the required rates. And that is disregarding factors like network bandwidth, contention on the segment, etc. Note: I'm not claiming this would not be good information to have. Just noting that it's not a trivial thing to do/measure. |
#321 could help, but for that to really work, users would have to install an RT kernel, which will probably not help make things "easier" for the average user. |
I'm closing this as we've officially deprecated this package. Refer to the announcement on ROS Discourse. |
By closing this, I'm not dismissing it, but I feel it would make sense to try and derive some system requirements for If you'd agree, please open an issue on the |
Considering the
ur_modern_driver
is so demanding on the computer and network to work reliably, has anyone determined & documented its minimum requirements already? (When not using the low bandwidth trajectory follower).Alternatively -or perhaps even better than a static requirements list-, a start-up test that verifies that the system can sustain latency and bandwidth required might go a really long way at reducing (new) user's frustration.
The text was updated successfully, but these errors were encountered: