RemoteControl - Revision history

Elcanoadmin: /* 5- and 6-channel RC Controller */

2024-08-16T01:50:41Z

‎5- and 6-channel RC Controller

Tfolsom: /* Current System */

2019-11-10T02:07:37Z

‎Current System

Tfolsom: /* CAN Bus and SAMD21 */

2019-11-09T05:03:43Z

‎CAN Bus and SAMD21

Tfolsom: /* CAN Bus and SAMD21 */

2019-11-09T05:02:54Z

‎CAN Bus and SAMD21

Tfolsom at 22:40, 8 November 2019

2019-11-08T22:40:28Z

Tfolsom: /* CAN Bus and SAMD21 */

2019-11-08T22:35:33Z

‎CAN Bus and SAMD21

Tfolsom: /* CAN Bus and SAMD21 */

2019-11-08T22:25:10Z

‎CAN Bus and SAMD21

Tfolsom: /* Elcano Remote Control */

2019-11-08T22:23:14Z

‎Elcano Remote Control

Tfolsom: /* CAN Bus and SAMD21 */

2019-11-08T21:42:15Z

‎CAN Bus and SAMD21

JosephBreithaupt: /* CAN Bus and SAMD21 */

2019-08-14T20:01:01Z

‎CAN Bus and SAMD21

← Older revision		Revision as of 01:50, 16 August 2024
Line 76:		Line 76:
	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.		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.

		+	= Summer 2024 RC controllers =
		+	DumboRC X6FG 6 channel RC controller2.4 GHz 4.8-10V
		+
		+	Pulse width 1000-2000 milliseconds
		+
		+	* CH1 Steering
		+	* CH2 Throttle
		+	* CH3 2 way switch
		+	* CH4 3 way slider switch
		+	* CH5 Rotary switch
		+	* CH6 Rotary switch
		+
		+	[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]
		+
		+	[[File:DUMBORC.jpg\|300px\|]]

	== RFM69HCW and SAMD21 ==		== RFM69HCW and SAMD21 ==

@@ Line 39: / Line 39: @@
 Reset requires two quick taps of the reset button. After a reset, the blue LED on the board will pulse slowly for a few seconds. If the board is unresponsive, try resetting this way first.'''
 == 5- and 6-channel RC Controller ==
 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.

← Older revision		Revision as of 05:03, 9 November 2019
Line 33:		Line 33:
	CAN is documented on [[Communication]]		CAN is documented on [[Communication]]

−	As a transmitter, it is packaged in a remote box with joysticks and switches. Functions and pins are explained in TranceiverPins_1_6.docx on https://github.com/elcano/Transceiver/tree/master/Transceiver ~~Documents~~.	+	As a transmitter, it is packaged in a remote box with joysticks and switches. Functions and pins are explained in TranceiverPins_1_6.docx on https://github.com/elcano/Transceiver/tree/master/Transceiver%20Documents.

@@ Line 31: / Line 31: @@
 When configured as a receiver it is mounted on the vehicle and communicates drive commands over CAN bus.
-CAN is documented on . [[Communication]]
+CAN is documented on [[Communication]]
-As a transmitter, it is packaged in a remote box with joysticks and switches. Functions and pins are explained in TranceiverPins.
+As a transmitter, it is packaged in a remote box with joysticks and switches. Functions and pins are explained in TranceiverPins_1_6.docx on https://github.com/elcano/Transceiver/tree/master/Transceiver Documents.

@@ Line 29: / Line 29: @@
 * Receiver using 5 or 6 channel radio control (RC)
-When configured as a receiver it is mounted on the vehicle and communicates drive commands over CAN bus. [[Elcano CAN Commands]]
+When configured as a receiver it is mounted on the vehicle and communicates drive commands over CAN bus.
 As a transmitter, it is packaged in a remote box with joysticks and switches. Functions and pins are explained in TranceiverPins.

@@ Line 23: / Line 23: @@
 * Receiver using Bluetooth
-* Transmitter using radio
+* Transmitter using radio (RFM69HCW)
-* Receiver using radio
+* Receiver using radio (RFM69HCW)
-* Receiver using radio control (RC)
+* Receiver using 5 or 6 channel radio control (RC)
 When configured as a receiver it is mounted on the vehicle and communicates drive commands over CAN bus.

@@ Line 1: / Line 1: @@
-= Elcano Remote Control =
+= Historic Systems =
 The Elcano system can run autonomously or by remote control. There have been four systems built for manual or remote control.
@@ Line 8: / Line 8: @@
 == Bluetooth ==
 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 ==
 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.
 == RFM69HCW and SAMD21 ==
@@ Line 36: / Line 62: @@
 * signed RSSI of last received packet (from remote)
 NEXT . [[SensorsPage]]

@@ Line 38: / Line 38: @@
 == CAN Bus and SAMD21 ==
-The RC transceiver board mounted on the vehicle communicates drive commands over CAN bus. This software is in development.
+The RC transceiver board can be built five different ways:
-'''NOTE: Resetting the SAMD21 mini dev board requires two quick taps of the reset button. After a reset, the blue LED on the board will pulse slowly for a few seconds. If the board is unresponsive, try resetting this way first.'''
+* Transmitter using Bluetooth
 NEXT . [[SensorsPage]]

← Older revision		Revision as of 20:01, 14 August 2019
Line 42:		Line 42:
	'''NOTE: Resetting the SAMD21 mini dev board requires two quick taps of the reset button. After a reset, the blue LED on the board will pulse slowly for a few seconds. If the board is unresponsive, try resetting this way first.'''		'''NOTE: Resetting the SAMD21 mini dev board requires two quick taps of the reset button. After a reset, the blue LED on the board will pulse slowly for a few seconds. If the board is unresponsive, try resetting this way first.'''

−
−
−	~~-- Main.JosephBreithaupt - 2017-10-11~~

	NEXT . [[SensorsPage]]		NEXT . [[SensorsPage]]