Bound reconnect time for message_bridge_client
We were having pi's not connect until a 5 minute timeout. That isn't
right. Tuning --sinit_max_init_timeout to a max of 5 seconds appears to
have fixed that. We are on a local network, so if something is taking
over 100ms, something is seriously wrong...
Change-Id: Icaf5f6c90ff99c969c6b5d8a3e78bbffc7c95934
Signed-off-by: Austin Schuh <austin.linux@gmail.com>
diff --git a/y2023/y2023_imu.json b/y2023/y2023_imu.json
index 416552b..535d97f 100644
--- a/y2023/y2023_imu.json
+++ b/y2023/y2023_imu.json
@@ -452,8 +452,6 @@
"applications": [
{
"name": "message_bridge_client",
- "executable_name": "message_bridge_client",
- "user": "pi",
"nodes": [
"imu"
]
diff --git a/y2023/y2023_logger.json b/y2023/y2023_logger.json
index 55d201d..9b0ba55 100644
--- a/y2023/y2023_logger.json
+++ b/y2023/y2023_logger.json
@@ -417,8 +417,6 @@
"applications": [
{
"name": "message_bridge_client",
- "executable_name": "message_bridge_client",
- "user": "pi",
"nodes": [
"logger"
]
diff --git a/y2023/y2023_pi_template.json b/y2023/y2023_pi_template.json
index 8d9fdaa..31f4045 100644
--- a/y2023/y2023_pi_template.json
+++ b/y2023/y2023_pi_template.json
@@ -350,7 +350,11 @@
"applications": [
{
"name": "message_bridge_client",
- "args": ["--rt_priority=16"],
+ "executable_name": "message_bridge_client",
+ "args": [
+ "--rt_priority=16",
+ "--sinit_max_init_timeout=5000"
+ ],
"user": "pi",
"nodes": [
"pi{{ NUM }}"
diff --git a/y2023/y2023_roborio.json b/y2023/y2023_roborio.json
index 3114ac9..cf3a14e 100644
--- a/y2023/y2023_roborio.json
+++ b/y2023/y2023_roborio.json
@@ -530,7 +530,8 @@
"name": "roborio_message_bridge_client",
"executable_name": "message_bridge_client",
"args": [
- "--rt_priority=16"
+ "--rt_priority=16",
+ "--sinit_max_init_timeout=5000"
],
"nodes": [
"roborio"