Robobot SVN version 1179 - Revision history

Jca: /* Load test */

2025-03-15T18:48:14Z

Load test

← Older revision		Revision as of 20:48, 15 March 2025
Line 131:		Line 131:
	[[file:hbt_update_time.png \| 500px]]		[[file:hbt_update_time.png \| 500px]]

	Time between "hbt" messages received by the "teensy_interface"		Time between "hbt" messages received by the "teensy_interface". Should be every 1ms.

	A load test shows that many subscriptions every millisecond will not cause send errors. The teensy_interface has logged these incoming messages. All subscriptions were with an interval of 1ms. It can be seen that this does not hold. In this case, seven message types were subscribed to at a 1ms interval. The list below shows messages for 7ms. The initial timestamp in seconds is when received in teensy_interface.		A load test shows that many subscriptions every millisecond will not cause send errors. The teensy_interface has logged these incoming messages. All subscriptions were with an interval of 1ms. It can be seen that this does not hold. In this case, seven message types were subscribed to at a 1ms interval. The list below shows messages for 7ms. The initial timestamp in seconds is when received in teensy_interface.

Jca: /* Load test */

2025-03-15T18:47:41Z

Load test

← Older revision		Revision as of 20:47, 15 March 2025
Line 131:		Line 131:
	[[file:hbt_update_time.png \| 500px]]		[[file:hbt_update_time.png \| 500px]]

	A load test shows that many subscriptions every millisecond will not cause send errors. The teensy_interface has logged these incoming messages. All subscriptions were with an interval of 1ms. It can be seen that this does not hold ~~when there are~~ seven message types ~~all~~ subscribed ~~with~~ a 1ms interval. The initial timestamp in seconds is when received in teensy_interface.		Time between "hbt" messages received by the "teensy_interface"

			A load test shows that many subscriptions every millisecond will not cause send errors. The teensy_interface has logged these incoming messages. All subscriptions were with an interval of 1ms. It can be seen that this does not hold. In this case, seven message types were subscribed to at a 1ms interval. The list below shows messages for 7ms. The initial timestamp in seconds is when received in teensy_interface.

	1742054300.0009 Rx ;74livn 0 0 0 0 0 0 0 0 1		1742054300.0009 Rx ;74livn 0 0 0 0 0 0 0 0 1

Jca: /* teensy_firmware_8 */

2025-03-15T18:42:45Z

teensy_firmware_8

← Older revision		Revision as of 20:42, 15 March 2025
Line 126:		Line 126:

	This has now been changed so that it only happens if there are no incoming messages to Teensy.		This has now been changed so that it only happens if there are no incoming messages to Teensy.

			===Load test===

			[[file:hbt_update_time.png \| 500px]]

	A load test shows that many subscriptions every millisecond will not cause send errors. The teensy_interface has logged these incoming messages. All subscriptions were with an interval of 1ms. It can be seen that this does not hold when there are seven message types all subscribed with a 1ms interval. The initial timestamp in seconds is when received in teensy_interface.		A load test shows that many subscriptions every millisecond will not cause send errors. The teensy_interface has logged these incoming messages. All subscriptions were with an interval of 1ms. It can be seen that this does not hold when there are seven message types all subscribed with a 1ms interval. The initial timestamp in seconds is when received in teensy_interface.

Jca: /* Update note 15 Mar 2025, SVN version 1179 */

2025-03-15T18:19:13Z

Update note 15 Mar 2025, SVN version 1179

← Older revision		Revision as of 20:19, 15 March 2025
Line 10:		Line 10:
	=== What to do ===		=== What to do ===

	* Changes to the "mqtt-client" are detailed to allow for a selective merge with your version.		* Changes to the "mqtt-client" are detailed below to allow for a selective merge with your version.

	====mqtt-client====		====mqtt-client====

Jca at 18:17, 15 March 2025

2025-03-15T18:17:55Z

← Older revision		Revision as of 20:17, 15 March 2025
Line 1:		Line 1:
	Back to [[Robobot_B \| Robobot]]		Back to [[Robobot_B \| Robobot]]

	== Update note ==		== Update note 15 Mar 2025, SVN version 1179==

	* Changes to mqtt-client.py to stop using start-button and to avoid starting mqtt-client if it is already running.		* Changes to mqtt-client.py to stop using start-button and to avoid starting mqtt-client if it is already running.

Jca: /* Update note */

2025-03-15T18:17:06Z

Update note

← Older revision		Revision as of 20:17, 15 March 2025
Line 5:		Line 5:
	* Changes to mqtt-client.py to stop using start-button and to avoid starting mqtt-client if it is already running.		* Changes to mqtt-client.py to stop using start-button and to avoid starting mqtt-client if it is already running.
	* Changes to ip_disp to use start button only		* Changes to ip_disp to use start button only
	* Changes to teensy_firmware_8 in an attempt to avoid untimely ~~shutdown~~.		* Changes to teensy_firmware_8 in an attempt to avoid untimely dataflow stop.
	A load test shows that Teensy can submit at least 5000 messages per second. The teensy_interface can receive and log this load with an occasional up to 5ms delay (seen once in 20 seconds). The messages were published to MQTT typically within 0.1ms.		A load test shows that Teensy can submit at least 5000 messages per second. The teensy_interface can receive and log this load with an occasional up to 5ms delay (seen once in 20 seconds). The messages were published to MQTT typically within 0.1ms.

Jca: /* teensy_firmware_8 */

2025-03-15T18:14:35Z

teensy_firmware_8

← Older revision		Revision as of 20:14, 15 March 2025
Line 123:		Line 123:
	==teensy_firmware_8==		==teensy_firmware_8==

	Teensy would stop all data subscriptions if there were too many (10) send errors. This has now been changed so that it only happens if there are no incoming messages to Teensy.		Teensy would stop all data subscriptions if there were too many (10) send errors.

			This has now been changed so that it only happens if there are no incoming messages to Teensy.

	A load test shows that many subscriptions every millisecond will not cause send errors. The teensy_interface has logged these incoming messages. All subscriptions were with an interval of 1ms. It can be seen that this does not hold when there are seven message types all subscribed with a 1ms interval. The initial timestamp in seconds is when received in teensy_interface.		A load test shows that many subscriptions every millisecond will not cause send errors. The teensy_interface has logged these incoming messages. All subscriptions were with an interval of 1ms. It can be seen that this does not hold when there are seven message types all subscribed with a 1ms interval. The initial timestamp in seconds is when received in teensy_interface.

Jca at 18:13, 15 March 2025

2025-03-15T18:13:27Z

@@ Line 116: / Line 116: @@
 * Listening to pin 13 only
 * Turning on LED 16 as red when start is pressed
 ==teensy_firmware_8==

Jca: /* Update note */

2025-03-15T17:28:56Z

Update note

← Older revision		Revision as of 19:28, 15 March 2025
Line 2:		Line 2:

	== Update note ==		== Update note ==

			* Changes to mqtt-client.py to stop using start-button and to avoid starting mqtt-client if it is already running.
			* Changes to ip_disp to use start button only
			* Changes to teensy_firmware_8 in an attempt to avoid untimely shutdown.
			A load test shows that Teensy can submit at least 5000 messages per second. The teensy_interface can receive and log this load with an occasional up to 5ms delay (seen once in 20 seconds). The messages were published to MQTT typically within 0.1ms.

	=== What to do ===		=== What to do ===

	* Changes to the "mqtt-client" are detailed to allow for a selective merge with your version.		* Changes to the "mqtt-client" are detailed to allow for a selective merge with your version.
	~~Updated original version is available in SVN repository.~~
	====mqtt-client====		====mqtt-client====
	cd ~/svn/robobot/mqtt_python		cd ~/svn/robobot/mqtt_python
Line 18:		Line 23:
	====ip_disp====		====ip_disp====
	cd ~svn/robobot/ip_disp/build		cd ~svn/robobot/ip_disp/build
	~~svn up ..~~
	~~make -j3~~
	~~====teensy_interface====~~
	~~cd ~svn/robobot/teensy_interface/build~~
	svn up ..		svn up ..
	make -j3		make -j3

Jca: /* Changes in ip_disp */

2025-03-15T17:01:19Z

Changes in ip_disp

← Older revision		Revision as of 19:01, 15 March 2025
Line 113:		Line 113:

	==Changes in ip_disp==		==Changes in ip_disp==
	* ~~listening~~ to pin 13 only		* Listening to pin 13 only
	* ~~turning~~ on LED 16 as red when start is pressed		* Turning on LED 16 as red when start is pressed

	==teensy_firmware_8==		==teensy_firmware_8==