Wow! Thanks for the quick response! I have a follow-up question. Are you able to maintain a stable connection to the robot? I was working with a testbench that has a roboRIO, radio, PDP, the basic brain, and was unable to get a reliable connection. It would fail, fail, connect!, then work.
On an actual robot I wasn’t able to connect at all. Have you had any problems like that?
I don’t recall it causing connectivity issues.
It would sometimes complain that the 1099 port is taken so I disabled it whenever I wasn’t using it.
Do you want to send the DS logs for us too look over?
thanks, I will do that. I am not at the lab right now, but I will generate and capture the logs. Perhaps your method of passing the parameters in will work better than me editing the startup script in /home/lvuser.
Enables the JMX remote agent and local monitoring via a JMX connector published on a private interface used by JConsole and any other local JMX clients that use the Attach API. JConsole can use this connector if it is started by the same user as the user that started the agent. No password or access files are checked for requests coming via this connector.
true / false. Default is true.
I interpret your statement to be disabling jmxremote. I am focusing on this statement because I don’t have this argument in my setup.
Yeah you’re totally right, I accidentally left it in when trying to disable it without commenting out the whole thing, it should be set to true.
The original code is not by me actually, this is the source: