Emergency stop state - Revision history

Blayze: /* Testing Emergency Stop State Behaviour */ Adds reference to the heartbeat timeout option that controls how long it takes for stop state behaviour to kick in.

2023-02-26T18:30:46Z

Testing Emergency Stop State Behaviour: Adds reference to the heartbeat timeout option that controls how long it takes for stop state behaviour to kick in.

← Older revision		Revision as of 18:30, 26 February 2023
Line 3:		Line 3:
	=== Testing Emergency Stop State Behaviour ===		=== Testing Emergency Stop State Behaviour ===
	If you are running an event in which RoboPads are being used, you may want to make sure that all RoboPad-based robots behave in a safe and expected manner when they enter this state. While simply getting the user to navigate to the homepage ''will'' get the RoboPad into the emergency stop state, the most sure fire way to test a RoboPad's behaviour when phone-RoboPad communication is broken is to physically break it. The recommended way to do this is to get the user to place the connected phone into a tin-foil (or other Faraday-cage equivalent that works for the 2.4Ghz radio range) lined box and close the lid, forcibly terminally disrupting the signal between the phone and the RoboPad, and then observing that the RoboPad-based robot responds in an appropriate and safe value.		If you are running an event in which RoboPads are being used, you may want to make sure that all RoboPad-based robots behave in a safe and expected manner when they enter this state. While simply getting the user to navigate to the homepage ''will'' get the RoboPad into the emergency stop state, the most sure fire way to test a RoboPad's behaviour when phone-RoboPad communication is broken is to physically break it. The recommended way to do this is to get the user to place the connected phone into a tin-foil (or other Faraday-cage equivalent that works for the 2.4Ghz radio range) lined box and close the lid, forcibly terminally disrupting the signal between the phone and the RoboPad, and then observing that the RoboPad-based robot responds in an appropriate and safe value.

			It's also worth noting that the Emergency Stop Behaviour sets in after a certain amount of time configurable under the RoboPad's [[The Management Page#General Configuration\|general configuration options]] - the ''Heartbeat Timeout''. This can be set by users up to '''seven seconds''', so if you want to be certain that safety has been considered, you may want to check that this value is set to a reasonable option (anything under 3 seconds in order to comply with [https://www.robotwars101.org/ants/rules.htm Antweight World Series Specifications]).

Blayze: Added info on disarming

2023-02-25T17:42:22Z

Added info on disarming

← Older revision		Revision as of 17:42, 25 February 2023
Line 1:		Line 1:
	Whenever the RoboPad looses signal from the phone that is connected to it, or the user is not in the "Control Robot" screen, the RoboPad will enter it's '''emergency stop state'''. In this state The RoboPad attempts to be as safe as possible by reverting all active [[IO Config Editor\|IO Units]] to their emergency stop state behaviour, which will change depending on how the user has configured each IO Unit. In particular, H-Bridge motors and Brushless motors should revert to stopped states.		Whenever the RoboPad looses signal from the phone that is connected to it, or the user is not in the "Control Robot" screen, the RoboPad will enter it's '''emergency stop state'''. In this state The RoboPad attempts to be as safe as possible by reverting all active [[IO Config Editor\|IO Units]] to their emergency stop state behaviour, which will change depending on how the user has configured each IO Unit. In particular, H-Bridge motors and Brushless motors should revert to stopped states. This will also '''disarm''' all IO Units, meaning that a control signal will have to be sent that '''passes through their safe values in order for them to move again'''.

	=== Testing Emergency Stop State Behaviour ===		=== Testing Emergency Stop State Behaviour ===
	If you are running an event in which RoboPads are being used, you may want to make sure that all RoboPad-based robots behave in a safe and expected manner when they enter this state. While simply getting the user to navigate to the homepage ''will'' get the RoboPad into the emergency stop state, the most sure fire way to test a RoboPad's behaviour when phone-RoboPad communication is broken is to physically break it. The recommended way to do this is to get the user to place the connected phone into a tin-foil (or other Faraday-cage equivalent that works for the 2.4Ghz radio range) lined box and close the lid, forcibly terminally disrupting the signal between the phone and the RoboPad, and then observing that the RoboPad-based robot responds in an appropriate and safe value.		If you are running an event in which RoboPads are being used, you may want to make sure that all RoboPad-based robots behave in a safe and expected manner when they enter this state. While simply getting the user to navigate to the homepage ''will'' get the RoboPad into the emergency stop state, the most sure fire way to test a RoboPad's behaviour when phone-RoboPad communication is broken is to physically break it. The recommended way to do this is to get the user to place the connected phone into a tin-foil (or other Faraday-cage equivalent that works for the 2.4Ghz radio range) lined box and close the lid, forcibly terminally disrupting the signal between the phone and the RoboPad, and then observing that the RoboPad-based robot responds in an appropriate and safe value.

Blayze: Added emergency stop page and simple guidance on testing emergency stop behaviour.

2023-02-22T03:15:11Z

Added emergency stop page and simple guidance on testing emergency stop behaviour.

New page

Whenever the RoboPad looses signal from the phone that is connected to it, or the user is not in the "Control Robot" screen, the RoboPad will enter it's '''emergency stop state'''. In this state The RoboPad attempts to be as safe as possible by reverting all active [[IO Config Editor|IO Units]] to their emergency stop state behaviour, which will change depending on how the user has configured each IO Unit. In particular, H-Bridge motors and Brushless motors should revert to stopped states.

=== Testing Emergency Stop State Behaviour ===
If you are running an event in which RoboPads are being used, you may want to make sure that all RoboPad-based robots behave in a safe and expected manner when they enter this state. While simply getting the user to navigate to the homepage ''will'' get the RoboPad into the emergency stop state, the most sure fire way to test a RoboPad's behaviour when phone-RoboPad communication is broken is to physically break it. The recommended way to do this is to get the user to place the connected phone into a tin-foil (or other Faraday-cage equivalent that works for the 2.4Ghz radio range) lined box and close the lid, forcibly terminally disrupting the signal between the phone and the RoboPad, and then observing that the RoboPad-based robot responds in an appropriate and safe value.