Difference between revisions of "RemoteControl"

From Elcano Project Wiki
Jump to navigation Jump to search
(RFM68HCW and SAMD21)
(Events)
 
(40 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Elcano Remote Control =
+
= RC controller =
 +
DumboRC X6FG 6 channel Radio Control Unit 2.4 GHz 4.8-10V. Installed summer 2024
  
The Elcano system can run autonomously or by remote control. There have been four systems built for manual or remote control.
+
Pulse width 1000-2000 milliseconds
  
== Joystick ==
+
* CH1 Steering
The first system used an APEM 9000 joystick. The part has five wires: 5V power, ground, and three analog lines. The joystick has two axes. The vertical axis is used for throttle (up) and brakes (down). The third analog signal is the voltage of the joystick when centered. The joystick was used in 2014 and is described in http://www.elcanoproject.org/tutorial/lab2.php.  The Low-level code may still contain inputs and processing for an analog joystick.
+
* CH2 Throttle / Brake
 +
* CH3 2 way switch: Forward or reverse
 +
* CH4 3 way slider switch: Manual or Automatic or Operator mode
 +
* CH5 Rotary switch: Request to raise gate to undock.
 +
* CH6 Rotary switch: Reserved
  
== Bluetooth ==
+
The system comes up in Manual (Controlled from RC) mode. The RC can switch the mode to Automatic or Operator. If no data comes from the RC, mode will transition to Operator.
In 2015 students built a control system using a Bluetooth receiver to the Arduino. The transmitter was a TI Sitara running Android.  
 
  
== 5- and 6-channel RC Controller ==
+
[https://www.amazon.com/dp/B09MS4HBC8/ref=sspa_dk_detail_2?psc=1&pd_rd_i=B09MS4HBC8&pd_rd_w=LeIXy&content-id=amzn1.sym.36d4fe03-2814-4a0b-86e2-d1e3d3071509&pf_rd_p=36d4fe03-2814-4a0b-86e2-d1e3d3071509&pf_rd_r=SF0RW81Y2X0PB3BGXJZP&pd_rd_wg=fWdsi&pd_rd_r=6c04f252-61f9-40a5-ac07-847c559b0e41&s=toys-and-games&sp_csd=d2lkZ2V0TmFtZT1zcF9kZXRhaWxfdGhlbWF0aWM Amazon]
The system has been run from either a Hitec Optics 5 2.4 five channel unit or a Spektrum DX6i six channel controller. The Low level circuit board has a3x7 pin socket in the corner to accommodate the receiver. Each channel needs to be on its own interrupt. Since the Arduino Mega has only 6 interrupts and the Arduino Micro has 5, this can be a problem, especially since we want another one or two interrupts to handle the speed. Low level code may still have software to handle these interrupts. The RC controllers send a 1.0 to 2.0 ms pulse on each channel at 30 Hz. Some controllers send these signals in turn. We have built a six-input OR circuit to combine all signals, which would allow processing with just one interrupt. Unfortunately, there is no good way to predict whether the RC unit will send pulses in turn or all at once. In fact, the behavior seems to be determined by the receive unit, not the transmitter. Thus a separate interrupt is required for each channel used. Interrupt processing consists of interrupting on a rising edge, then switching to a falling edge interrupt and logging the pulse width. A width of 1.0 ms typically means one extreme, 1.5 ms is centered, and 2.0 ms is the other extreme., This system can get confusing about which channel is assigned which behavior, and the two controllers assign their channels differently. To go beyond the Arduino interrupt limit, the V2 Low Level board has all RC inputs assigned to Analog Input 8 to 13 of the Arduino. These pins are used digitally. Pins A8-A15 on Arduino Mega, all go to the same port. Thus we can use the pin change interrupt, which is activated whenever any bit of the 8-bit port changes.
 
  
== Amplitude Shift Keying (ASK) RC Controller ==
+
[[File:DUMBORC.jpg|300px|]]
  
Elcano project used a custom-built radio control system with two arduinos, one in the remote control that collects manual inputs and transmits them with a 433MHz ASK radio transmitter, and one on the Elcano vehicle which receives the information sent over radio and converts it into an ElcanoSerial drive packet which is transmitted to C2 over ElcanoSerial. This information is used to manually drive the trike, begin an autonomous routine, or activate the emergency brake and stop the trike. The RH_ASK system was limited to 40 feet (12 meters) in practice and was never use to drive the vehicle.
+
=  Operator Control  =
  
== RFM69HCW and SAMD21 ==
+
If a person is riding the vehicle, they can use a joystick and switches for the same functionality as the RC controller
  
The RFM69HCW (915MHz) transceiver offers several benefits over the 433MHz ASK radios:
+
* Joystick Left-Right: Steering
* greater range with higher transmit power
+
* Joystick up/down: Throttle / Brake
* much higher raw bitrate
+
* Switch: Forward or reverse
* half-duplex communication and received signal strength indicator (RSSI)
+
* Switch: Manual or Automatic mode
* compatibility with higher-performance 3.3V ARM boards like SAMD21
+
* Switch: Request to raise gate to undock.
 +
^ There is an Emergency Stop button on the vehicle.
  
Using the RF69 RadioHead library, the RC system has expanded capabilities from the RH ASK implementation. Data is stored on both ends as a C struct, which is broken down and transmitted as bytes by the RF69 library. After successful transmission, the data is accessible directly from the struct and variables larger than one byte need no additional processing before use. After successfully receiving a packet from the remote control, the receiver sends a packet back with an RSSI value. The remote control uses this reply message to indicate radio communication is active.
+
=  Automatic Control  =
  
=== Transmitted data to vehicle ===
+
In Automatic mode, the Nav computer sends driving commands over CAN. Automatic mode is selected by the RC or Operator switch. There are separate Auto modes, depending on whether Auto was selected from the RC or Operator, since the response to E-stop differs.
* unsigned 12-bit throttle (0-4095)
 
* unsigned 12-bit turn
 
* boolean emergency stop
 
* boolean autonomous mode
 
* signed RSSI of last received packet (from vehicle)
 
  
=== Received data from vehicle ===
+
The system can go into Emergency Stop from various situations.
* signed RSSI of last received packet (from remote)
+
* If Auto Mode was initiated from RC, the RC switch will be in Auto mode. Estop is cleared by returning the RC switch to Manual Mode.
 +
* If Auto Mode was initiated by the operator, the Operator switch will be in Auto mode. Estop is cleared by setting the Operator switch to Manual Mode.
 +
* If the operator pushes the E-Stop button, E-stop is cleared by the button being reset.
  
 +
=  Modes  =
  
-- Main.JosephBreithaupt - 2017-10-11
+
Trike behavior depends on the mode. In RC control, pulling the trigger in puts on the brakes. In Operator or Automatic mode, the RC unit is disabled, except that pulling the trigger in is an E-Stop. State transitions are shown in the diagram. An LED on the vehicle is set to a color in the diagram to indicate the mode.
  
NEXT . [[SensorsPage]]
+
[[File:State transitions2A.png]]
 +
 
 +
== Events ==
 +
 
 +
* RC_DATA: Valid data from RC
 +
* NO_RC: No data from RC
 +
* RC_MAN: RC mode switch set to manual
 +
* RC_OP: RC mode switch set to operator
 +
* RC_AUTO: RC mode switch set to auto
 +
* RC_BRAKE: RC applies brake
 +
* NO_CAN: No recent data from CAN
 +
* NO_OP: No operator action for too long
 +
* OP_AUTO: Operator switch set for auto
 +
* OP_MAN: Operator switch set for manual
 +
* OP_BRAKE: Operator applies brake
 +
* OP_ESTP: Operator pushes E-stop button
 +
* OP_RTN: Operator resets E-stop button
 +
* CAN_MAN: Auto mode requests manual takeover
 +
* AUTO_ESTP: Auto mode requests E-stop

Latest revision as of 18:41, 19 June 2026

RC controller

DumboRC X6FG 6 channel Radio Control Unit 2.4 GHz 4.8-10V. Installed summer 2024

Pulse width 1000-2000 milliseconds

  • CH1 Steering
  • CH2 Throttle / Brake
  • CH3 2 way switch: Forward or reverse
  • CH4 3 way slider switch: Manual or Automatic or Operator mode
  • CH5 Rotary switch: Request to raise gate to undock.
  • CH6 Rotary switch: Reserved

The system comes up in Manual (Controlled from RC) mode. The RC can switch the mode to Automatic or Operator. If no data comes from the RC, mode will transition to Operator.

Amazon

DUMBORC.jpg

Operator Control

If a person is riding the vehicle, they can use a joystick and switches for the same functionality as the RC controller

  • Joystick Left-Right: Steering
  • Joystick up/down: Throttle / Brake
  • Switch: Forward or reverse
  • Switch: Manual or Automatic mode
  • Switch: Request to raise gate to undock.

^ There is an Emergency Stop button on the vehicle.

Automatic Control

In Automatic mode, the Nav computer sends driving commands over CAN. Automatic mode is selected by the RC or Operator switch. There are separate Auto modes, depending on whether Auto was selected from the RC or Operator, since the response to E-stop differs.

The system can go into Emergency Stop from various situations.

  • If Auto Mode was initiated from RC, the RC switch will be in Auto mode. Estop is cleared by returning the RC switch to Manual Mode.
  • If Auto Mode was initiated by the operator, the Operator switch will be in Auto mode. Estop is cleared by setting the Operator switch to Manual Mode.
  • If the operator pushes the E-Stop button, E-stop is cleared by the button being reset.

Modes

Trike behavior depends on the mode. In RC control, pulling the trigger in puts on the brakes. In Operator or Automatic mode, the RC unit is disabled, except that pulling the trigger in is an E-Stop. State transitions are shown in the diagram. An LED on the vehicle is set to a color in the diagram to indicate the mode.

State transitions2A.png

Events

  • RC_DATA: Valid data from RC
  • NO_RC: No data from RC
  • RC_MAN: RC mode switch set to manual
  • RC_OP: RC mode switch set to operator
  • RC_AUTO: RC mode switch set to auto
  • RC_BRAKE: RC applies brake
  • NO_CAN: No recent data from CAN
  • NO_OP: No operator action for too long
  • OP_AUTO: Operator switch set for auto
  • OP_MAN: Operator switch set for manual
  • OP_BRAKE: Operator applies brake
  • OP_ESTP: Operator pushes E-stop button
  • OP_RTN: Operator resets E-stop button
  • CAN_MAN: Auto mode requests manual takeover
  • AUTO_ESTP: Auto mode requests E-stop