The present invention relates to model vehicle transmit controllers and, more particularly, to user interfaces for model vehicle transmit controllers.
A radio control model vehicle, such as a radio control automobile, boat, or airplane, may be controlled remotely by a transmit controller. A transmit controller is often an exclusively hardware device with an exclusively hardware built-in user interface. In a transmit controller, all user input may be received through mechanical hardware components such as knobs, dials, wheels, and switches. Output to the user might be provided solely through labeled positions of the hardware components and a few LED's.
The built-in user interface of a transmit controller may be separated into two parts: a control user interface and a parameter user interface. The control user interface directly controls the movement of the model vehicle. For example, in a typical model automobile, the control user interface includes a steering wheel and a throttle trigger. When the user turns the steering wheel, the wheels of the vehicle may move accordingly. When the user displaces the trigger toward the grip, the vehicle may accelerate, and when the user displaces the trigger away from the grip, the vehicle may brake.
The parameter user interface allows a user to set operational parameters which indirectly control the operation of the vehicle. These parameters may be stored a memory of the transmit controller. The parameters may affect how the transmit controller translates input from the control user interface into output to the model vehicle. The transmit controller can be said to “determine” an output signal to the model vehicle based on the parameters and the input to the control user interface. In other words, the parameters may determine whether or not the transmit controller modifies a control instruction from the control user interface and, if the control instruction is modified, the parameters may determine how the control instruction is modified.
For example, some model vehicles have reversed steering servos, meaning the vehicle will turn left when the transmit controller directs it to turn right, and turn right when the transmit controller directs it to turn left. Accordingly, a user intending to turn the vehicle to the right will observe the vehicle turn to the left, and vice versa. To address this issue, a transmit controller may have a servo reversing parameter stored in memory. If the servo reversing parameter is set to off, the transmit controller may transmit signals normally. If the servo reversing parameter is set to on, the transmit controller may reverse the left/right instructions transmitted to the vehicle, compensating for the vehicle's the reversed steering servo. Accordingly, a user instruction to turn the vehicle to the left will cause the transmit controller to instruct the vehicle to turn to the right, which because of the reversed steering servo will cause the vehicle to turn to the left. Likewise, a user instruction to turn the vehicle to the right will cause the transmit controller to instruct the vehicle to turn to the left, which because of the reversed steering servo will cause the vehicle to turn to the right.
For binary parameters such as servo reversing, a built-in switch in the transmit controller may be acceptable. However, with more complex parameters, typical hardware user interface components may be unwieldy. For instance, an acceleration curve parameter may determine how much the transmit controller will instruct the model vehicle to accelerate in response to varying amounts of movement of the throttle trigger. To specify an acceleration curve, with only dials, switches, and so on can be difficult for most users. In addition, if the user cannot graphically view the acceleration curve the user may have no way to determine if the user has set the acceleration curve correctly.
Typical hardware user interface components may also have limited capability to provide feedback to the user. Informing a user of vehicle speed, battery voltage, engine RPM, and so on with only labels and a few LED's can be difficult. A transmit controller with a built-in graphical user interface could provide a user with a more advanced user interface. However, producing such a transmit controller may be cost-prohibitive. The addition of a graphical display and versatile user controls would require additional components that would add significantly to the cost of the transmit controller. In addition, powering these components would significantly reduce the transmit controller's battery life.
Thus, a need exists for the addition of a better user interface to a transmit controller without the extensive addition of components to the transmit controller.
In an embodiment, a transmit controller compatible with an auxiliary user interface device is provided. The transmit controller has a memory with operational parameters, a control user interface, an auxiliary user interface connector, and a transmit controller processor. The transmit controller processor is configured to transmit the operational parameters to the auxiliary user interface device and modify the operational parameters in accordance with a parameter instruction from the auxiliary user interface device. The transmit controller processor is further configured to receive a control instruction from the control user interface, determine an output signal based on the control instruction and the one or more operational parameters, and transmit the output signal to the model vehicle.
For a more complete understanding of the present invention and the advantages thereof, reference is now made to the following Detailed Description taken in conjunction with the accompanying drawings, in which:
In the following discussion, numerous specific details are set forth to provide a thorough understanding of the present invention. However, those skilled in the art will appreciate that the present invention may be practiced without such specific details. In other instances, well-known elements have been illustrated in schematic or block diagram form in order not to obscure the present invention in unnecessary detail. Additionally, for the most part, specific details, and the like have been omitted inasmuch as such details are not considered necessary to obtain a complete understanding of the present invention, and are considered to be within the understanding of persons of ordinary skill in the relevant art.
In accordance with the present invention, a transmit controller may have the capability to communicate with a portable electronic device. The transmit controller may function alone, without the portable electronic device, and provide a basic, built-in non-graphical parameter user interface. To provide an expanded parameter user interface, a portable electronic device may be connected to the transmit controller and serve as an auxiliary user interface. The portable electronic device may be attached to the transmit controller where the user may interact with the portable electronic device while using the transmit controller.
Portable electronic devices may be devices such as mobile smart phones, personal digital assistants, and digital music players. These devices are commonly available and commonly programmable. By using a portable electronic device, the transmit controller may present a graphical user interface with only the hardware necessary to communicate with the portable electronic device, rather than a built-in LCD display, touch screen, audio output, and so on. A user who owns a transmit controller and a portable electronic device may save the expense of additional hardware components in the transmit controller by utilizing the hardware components available in the portable electronic device.
Many portable electronic devices are capable of providing rich graphical user interfaces comparable to the graphical user interfaces of personal computers. For input, these devices may have a touch screen or keyboard. These devices may have high-resolution displays with the same range of colors as a personal computer monitor. These devices are often usable as music players and consequently may be capable of producing high-quality audio output. Some devices may have vibration capabilities.
Many portable electronic devices also have an external interface for communication with an external device. The external device is often a personal computer. Through the external interface, the portable electronic device may communicate with the personal computer and vice versa. In an exemplary embodiment of the present invention, a portable electronic device communicates with a model vehicle transmit controller using the external interface, allowing the portable electronic device to function as an auxiliary user interface for a transmit controller.
With reference to
The portable electronic device 102 may be a smart phone or digital music player. Exemplary portable electronic devices are the iPhone and iPod Touch produced by Apple Inc. Both of these exemplary portable electronic devices may accept user input via a touch screen. Portable electronic device 102 may be connected to transmit controller 104 through external interface 102A of portable electronic device 102. External interface 102A may be a conventional hardware interface of portable electronic device 102, such as the connection used by portable electronic device 102 to communicate with a personal computer.
Transmit controller 104 may have a dock for storing portable electronic device 102, so that the user may more easily concurrently operate both devices. A typical portable electronic device 102 may be physically smaller in volume, or at least not substantially larger in volume, than a typical transmit controller 104. The reason is that a user may be expected to operate portable electronic device 102 while simultaneously controlling a vehicle with transmit controller 104. If transmit controller 104 is designed to be held with both hands, a substantially larger portable electronic device 102 may be difficult for the user to work with.
Portable electronic device 102 may execute a software application for communication with transmit controller 104. The software application may be provided to portable electronic device 102 through an Internet download. Internet download is a common software application delivery method for many portable electronic devices.
Transmit controller 104 may have processor 104A. Processor 104A may determine what output signal is transmitted to receiver 106 over radio link 108. The output signal may be determined from user input from control user interface 104B and one or more parameters stored in memory 104C. Control user interface 104B may be components of transmit controller 104 which permit a user to directly control the operations of a model vehicle. These components may include a steering wheel and throttle trigger. Once processor 104A determines the output signal that should be transmitted, it may send the signal through a radio frequency module.
Transmit controller 104 may connect to external interface 102A of portable electronic device 102 through auxiliary user interface connector 104E. The connection between external interface 102A and auxiliary user interface connector 104E may be wired or wireless, and a wired connection may be through direct contact or through a cable between the two devices. In some embodiments, auxiliary user interface connector 104E may include a cable, with one end of the cable permanently attached to transmit controller 104.
A wireless connection between external interface 102A and auxiliary user interface connector 104E may be a Bluetooth connection. The wireless connection between external interface 102A and auxiliary user interface connector 104E may also be a wireless local area network connection using a standard such as IEEE 802.11, also known as Wi-Fi. External interface 102A and auxiliary user interface connector 104E may include Bluetooth or 802.11 transceivers. Portable electronic device 102 may be a mobile smart phone, and many mobile smart phones include Bluetooth and 802.11 transmitters. Auxiliary user interface 104E may utilize a Bluetooth or 802.11 transceiver built into transmit controller 104 or an external dongle with a Bluetooth or 802.11 transceiver.
One advantage of using a wireless connection between external interface 102A and auxiliary user interface connector 104E is that a single transmit controller 104 may easily support different types of portable electronic devices 102. Different portable electronic device manufacturers may use different physical connections for their portable electronic devices. Accordingly, transmit controller 104 may be require a separate external interface 102A for each type of portable electronic device. In contrast, a wireless standard such as Bluetooth or 802.11 may typically be supported by a variety of devices.
Another advantage of using a wireless connection between external interface 102A and auxiliary user interface connector 104E is that the wireless connection permits portable electronic device 102 to be separated from transmit controller 104. A user's pit man, for example, could use portable electronic device 102 while the user continues to operate the vehicle with transmit controller 104. Further, if a wireless local area network connection such as IEEE 802.11 is used, multiple portable electronic devices 102 may be in communication with a single transmit controller 104 at the same time. Therefore, a user and the user's pit man may each have a functioning portable electronic device 102 while the user is controlling the vehicle with transmit controller 104.
When portable electronic device 102 is not connected, the user may modify the parameters in memory 104C through parameter user interface 104D. Parameter interface 104D may allow the user to modify basic parameters such as servo reversing, steering sensitivity, and throttle sensitivity. These basic parameters may be sufficient for the user to operate the model vehicle, but may be limited by the input and output capabilities of parameter interface 104D.
When the user connects portable electronic device 102 to auxiliary user interface connector 104E, portable electronic device 102 may provide the user with a graphical user interface permitting the user to gain access to additional parameters and additional feedback. The graphical user interface may also provide the user with access to the same parameters and feedback available through transmit controller 104 alone. Parameter user interface 104D may become inoperable when portable electronic device 102 is connected.
To display a parameter, auxiliary user interface device 102 may request the parameter from processor 104A. In response to the request, processor 104A may transmit the parameter from memory 104C to portable electronic device 102.
When the user chooses to modify a parameter using portable electronic device 102, portable electronic device 102 transmits a parameter instruction to transmit controller 104. The parameter instruction instructs processor 104A to modify the parameter in memory 104C according to the user's input.
Portable electronic device 102 may transmit signals to and receive signals from the vehicle through transmit controller 104. Through the graphical user interface provided by portable electronic device 102, the user may set the various parameters stored in memory 104C. The user may set be able to set the parameters in memory 104C while operating a model vehicle, while not operating a model vehicle, or both.
Telemetry sensors 112 may be mounted on the model vehicle. Telemetry data captured by telemetry sensors 112 may be provided to receiver 106, which may transmit the data to transmit controller 104 over radio link 108. The telemetry data may include data such as motor temperature, motor RPM, speed, battery voltage, and fuel level. Transmit controller 104 may then provide the data to portable electronic device 102, if it is attached. Telemetry data may be provided to the user through built-in components of transmit controller 104, but the inclusion of portable electronic device 102 can greatly improve the presentation of the telemetry data to the user. For example, in addition to using its graphical display, portable electronic device 102 may provide feedback to the user through its audio and vibration capabilities.
An exemplary parameter which takes advantage of the output capabilities of the auxiliary user interface is an accelerometer sensor in the model vehicle. The accelerometer sensor can be used to detect bumps, collisions, jumps, and landings of the model vehicle. The accelerometer sensor can provide the acceleration data to portable electronic device 102 through receiver 106, radio link 108, and transmit controller 104. Portable electronic device 102 may vibrate during periods of sudden changes in acceleration of the model vehicle, providing additional feedback to the user. Because the feedback is tactile, the user may receive the feedback even when the user is not looking at transmit controller 104 or portable electronic device 102.
Portable electronic device 102 may communicate with processor 104A of transmit controller 104. Portable electronic device 102 may transmit write commands to processor 104A, instructing processor 104A to modify the value of a particular parameter in the memory of transmit controller 104. Portable electronic device 102 may transmit read commands to processor 104A, instructing processor 104A to provide portable electronic device 102 with the value of a particular parameter in memory 104C or a particular telemetry value recorded by telemetry sensors 110. Portable electronic device 102 may also periodically transmit values to portable electronic device 102, eliminating the need for read commands.
With reference to
Transmit controller 200 has a base which supports steering wheel 204 and throttle trigger 206. As shown in
When connected, portable electronic device 202 may provide an auxiliary user interface for transmit controller 200. The auxiliary user interface may utilize a touch screen of portable electronic device 202 and provide additional input and output capabilities not available in the basic user interface of transmit controller 200. Dock 208 and auxiliary user interface connector 210 may be located where a user may easily see the screen of portable electronic device 202 while operating a model vehicle with steering wheel 204 and throttle control 206. The user may also operate the touch screen of portable electronic device 202 by moving the user's right hand from steering wheel 204 while continuing to grasp transmit controller 200 with the user's left hand.
With reference to
In user interface 300, panel 302 displays a lap timer, panel 304 displays a lap counter, panel 306 displays battery voltage, and panel 308 displays engine RPM. The size, number, arrangement, and content of the panels displayed by the user interface may be modified by the user. For instance, instead of the engine RPM shown in panel 308, the user might choose to display a second row of three panels to the right of the column having panels 302, 304, and 306. Some additional choices for content which may be displayed in a panel include motor temperature, vehicle speed, remaining laps, total elapsed time, and vehicle fuel level.
Notably, panel 308 includes a graphical display of an RPM dial. These graphical displays may be readily shown on the LCD display of a portable electronic device. However, showing such graphical displays on a transmit controller, which normally does not have a LCD display or equivalent, could require the inclusion of additional components, increasing the cost and complexity of the transmit controller.
With reference to
The parameters which may be set through a portable electronic device may be in addition to, or may overlap, the parameters which may be set through the parameter user interface of the associated transmit controller. In an exemplary embodiment, the mechanism on the built-in parameter user interface of transmit controller 104 for setting various parameters may be a dial called the MF (MultiFunction) Dial. Through the MF Dial and associated hardware, the user may select and modify a parameter.
In portable electronic device interface 400, only one of the MF Dial and portable electronic device interface 400 may control a given parameter at a particular time. Slider 402, the slider for steering sensitivity, is shown as disabled because it is being controlled by the MF Dial. The user may be required to use the MF Dial, rather than slider 402, to modify the steering sensitivity.
The user may press MF Dial Enabled Button 412 to disable MF Dial control of any parameter. Upon the user pressing MF Dial Enabled Button 412, slider 402 may become enabled, because the steering sensitivity is no longer being controlled by the MF Dial. All sliders 402, 404, 406, and 408 may then be usable.
The user may cycle through which parameter is controlled by the MF Dial by pressing Select Function Button 414. If the user were to press Select Function Button 414, the parameter controlled by the MF Dial may change from steering sensitivity to ABS*. Accordingly, slider 402 may become enabled and slider 404 may become disabled.
MF Dial Icon 416 may serve as a visual reminder that buttons 412 and 414 are associated with the MF Dial. Graph 418 provides the user with a graphical display of the parameter controlled by the MF Dial.
Because a typical portable electronic device 102 may offer richer input and output functionality than a typical transmit controller 104, portable electronic device 102 may offer the user controls and feedback that would be impractical for transmit controller 104 alone to provide. With reference to
The present invention may provide improved input and output capabilities for a model vehicle transmit controller without significantly increasing the cost and complexity of the transmit controller. Instead, the transmit controller may have an auxiliary user interface connector, permitting a portable electronic device to serve as a detachable, auxiliary user interface for the model vehicle.
With reference to
With reference to
Although the invention has been described with reference to a specific embodiment, these descriptions are not meant to be construed in a limiting sense. Various modifications of the disclosed embodiments, as well as alternative embodiments of the invention will become apparent to persons skilled in the art upon reference to the description of the invention. It is therefore contemplated that the claims will cover any such modifications or embodiments that fall within the true scope and spirit of the invention.
This application relates to, and claims the benefit of the filing date of, co-pending U.S. provisional patent application Ser. No. 61/331,745 entitled AUXILIARY USER INTERFACE FOR A MODEL VEHICLE, filed May 5, 2010. The entire contents of application Ser. No. 61/331,745 are incorporated herein by reference for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
5121863 | Kotitalo et al. | Jun 1992 | A |
5252965 | Gidwani et al. | Oct 1993 | A |
5438936 | Wang | Aug 1995 | A |
5457745 | Wang | Oct 1995 | A |
5555302 | Wang | Sep 1996 | A |
5787168 | Lien | Jul 1998 | A |
5788202 | Richter | Aug 1998 | A |
5836563 | Hsin-Yung | Nov 1998 | A |
5903645 | Tsay | May 1999 | A |
5937065 | Simon et al. | Aug 1999 | A |
6127941 | Van Ryzin | Oct 2000 | A |
6229891 | Chen | May 2001 | B1 |
6293798 | Boyle et al. | Sep 2001 | B1 |
6658328 | Alrabady et al. | Dec 2003 | B1 |
6741684 | Kaars | May 2004 | B2 |
6785567 | Kato | Aug 2004 | B2 |
6944294 | Tsay | Sep 2005 | B2 |
6959899 | Yeh | Nov 2005 | B2 |
7080812 | Wadsworth et al. | Jul 2006 | B2 |
7158092 | Shen | Jan 2007 | B2 |
7174518 | Kim | Feb 2007 | B2 |
7224262 | Simon et al. | May 2007 | B2 |
7231294 | Bodin et al. | Jun 2007 | B2 |
7233844 | Peltz et al. | Jun 2007 | B2 |
7268664 | Tanaka et al. | Sep 2007 | B2 |
7307573 | Choi | Dec 2007 | B2 |
7391320 | Beard et al. | Jun 2008 | B1 |
7407143 | Chen | Aug 2008 | B1 |
7418097 | Chang | Aug 2008 | B2 |
7486193 | Elwell | Feb 2009 | B2 |
7537190 | Fan | May 2009 | B2 |
7614595 | Richter | Nov 2009 | B2 |
7681194 | Van Ee et al. | Mar 2010 | B2 |
7828259 | Wang et al. | Nov 2010 | B2 |
7967262 | O'Brien et al. | Jun 2011 | B2 |
8138894 | Kato et al. | Mar 2012 | B2 |
8240628 | Huang | Aug 2012 | B2 |
8262070 | Liu | Sep 2012 | B2 |
8282063 | Ou et al. | Oct 2012 | B2 |
8376301 | Fan | Feb 2013 | B2 |
8405974 | Sayavong | Mar 2013 | B2 |
8500080 | Hu | Aug 2013 | B2 |
20010042631 | Carrier | Nov 2001 | A1 |
20020187726 | Yamaguchi | Dec 2002 | A1 |
20030148703 | Scott et al. | Aug 2003 | A1 |
20040018800 | Caiozza | Jan 2004 | A1 |
20040077284 | Bonilla et al. | Apr 2004 | A1 |
20040091102 | Tsay | May 2004 | A1 |
20040179469 | Attar et al. | Sep 2004 | A1 |
20040179678 | Hsu Li | Sep 2004 | A1 |
20050048918 | Frost et al. | Mar 2005 | A1 |
20050088275 | Valoteau et al. | Apr 2005 | A1 |
20050168373 | Mukaida | Aug 2005 | A1 |
20050236536 | Fan | Oct 2005 | A1 |
20060113428 | Choi | Jun 2006 | A1 |
20060145039 | Shawver | Jul 2006 | A1 |
20060183405 | Mathews | Aug 2006 | A1 |
20060293102 | Kelsey | Dec 2006 | A1 |
20070001805 | Utter et al. | Jan 2007 | A1 |
20070035412 | Dvorak et al. | Feb 2007 | A1 |
20070262223 | Wang et al. | Nov 2007 | A1 |
20070284500 | Fan | Dec 2007 | A1 |
20070293124 | Smith et al. | Dec 2007 | A1 |
20080285628 | Gizis et al. | Nov 2008 | A1 |
20090195407 | Nakano et al. | Aug 2009 | A1 |
20090262002 | Alexander et al. | Oct 2009 | A1 |
20090294617 | Stacey et al. | Dec 2009 | A1 |
20110288696 | Lefebure | Nov 2011 | A1 |
20120015686 | Krupnik | Jan 2012 | A1 |
Number | Date | Country |
---|---|---|
101505380 | Aug 2009 | CN |
10 2007 038 666 | Feb 2009 | DE |
1736948 | Dec 2006 | EP |
1973313 | Sep 2008 | EP |
2296122 | Mar 2011 | EP |
2384796 | Nov 2011 | EP |
2416049 | Feb 2012 | EP |
5086759 | Apr 1993 | JP |
5106376 | Apr 1995 | JP |
2002-345050 | Nov 2002 | JP |
2004-64418 | Feb 2004 | JP |
2004-064418 | Feb 2004 | JP |
2009-177767 | Aug 2009 | JP |
M395337 | Dec 2010 | TW |
WO 2004052484 | Jun 2004 | WO |
WO 2010042219 | May 2010 | WO |
Entry |
---|
Booker, Jim; “The JR Data Transfer Program Makes Model Setup Easy”; Horizon Hobby; Aug. 29, 2008; http://www.horizonhobby.com/Articles/Article.aspx?ArticleID=1827. |
Booker, Jim; “The JR Data Transfer Program Makes Model Setup Easy”; Horizon Hobby; Aug. 29, 2008; http://www.jrradios.com/Articles/Article.aspx?ArticleID=1827. |
“JR Data Transfer How to: . . . Set Up Dual Aileron and Elevator”; Transcript of video presented by Horizon Hobby Aug. 29, 2008 at http://www.horizonhobby.com/Articles/Article.aspx?ArticleID=1827. |
Parry, Bill; “Clip-on Wireless Telemetry from Eagle Tree Systems!”, message posted Apr. 27, 2004 by ‘billpa’, “Bill From Eagle Tree Systems here, . . . ”; http://forums.radiocontrolzone.com/showthread.php?t=165955. |
European Search Report; EP Appl'n No. 11164210.4; Sep. 19, 2011. |
Horizon Hobby; “PC Data Transfer by JR”; Aug. 2008; http://www.horizonhobby.com/Products/Default.aspx?ProdID=JRPA310#quickOverview. |
Horizon Hobby; “JR PC Data Transfer Instruction Manual”; Horizon Hobby Inc., Champaign IL; Aug. 2008. |
Eagle Tree Systems; “Preliminary Information for the Seagull Wireless Telemetry System”; Eagle Tree Systems, Bellevue WA; Aug. 12, 2004; http://web.archive.org/web/20040812123921/http://eagletreesystems.com/News/news.html. |
Eagle Tree Systems; “Wireless Telemetry and Advanced Data Recording for Model Cars/Trucks”; Eagle Tree Systems, Bellevue WA; Jul. 10, 2004; http://www.eagletreesystems.com/Car/car.html. |
Eagle Tree Systems; “Instruction Manual for the USB Flight Data Recorder, ver. 1.01”; Eagle Tree Systems, Bellevue WA; Jun. 21, 2003. |
Eagle Tree Systems; “Instruction Manual for the USB Flight Data Recorder, ver. 3.9”; Eagle Tree Systems, Bellevue WA; Jan. 15, 2010. |
Spektrum RC; “ModelMatch”; Horizon Hobby Inc., Champaign IL; Oct. 2009; http://www.spektrumrc.com/DSM/Technology/modelmatch.aspx. |
Spektrum; “3-Channel, 4-Model Memory DSM Racing System” instruction manual; Horizon Hobby Inc., Champaign lL; Oct. 2009. |
Futaba; “FASST 2.4GHz Module & R603FS Receiver” brochure; Great Planes Model Distr. Co., Champaign IL, May 2006. |
Futaba; “Futaba 2.4GHz FASST System Features”; May 2007 Hobbico Inc.; http://2.4gigahertz.com/features/features.html. |
Futaba; “3GR-2.4GHz System” manual; Futaba Corp., Japan, May 2007. |
Futaba; “3PM w/2.4GHz FASST System” brochure; Great Planes Model Distr. Co., Champaign IL, May 2007; www.2.4gigahertz.com. |
Futaba; “3PM-2.4GHz System” manual; Futaba Corp., Japan, May 2007. |
Futaba; “4PK 4-Channel Computer Systems” brochure; Great Planes Model Distr. Co., Champaign IL, May 2007. |
Futaba; “6EX w/2.4GHz FASST System” brochure; Great Planes Model Distr. Co., Champaign IL, May 2007. |
Futaba; “6EX-2.4GHz Instruction Manual”; Futaba Corp., Japan, May 2007. |
Futaba; “Futaba Model Data Converter” manual; Futaba Corp., Japan, May 2008. |
Futaba; “7C 7-Channel FASST Computer System” brochure; Great Planes Model Distr. Co., Champaign IL, May 2007. |
Futaba; “7C-2.4GHz Instruction Manual”; Futaba Corp., Japan, May 2007. |
Futaba; “12FG 12-Channel Computer Systems” brochure; Great Planes Model Distr. Co., Champaign IL, May 2007. |
Futaba; “FASST Air System TM-7 RF Module and R607FS Receiver Instruction Manual”; Futaba Corp., Japan, May 2007. |
Futaba; “FASST Air System TM-14 RF Module and R6014FS Receiver Instruction Manual”; Futaba Corp., Japan, May 2007. |
Futaba; “FASST Air System TM-8 RF Module and R608FS Receiver Instruction Manual”; Futaba Corp., Japan, May 2008. |
Futaba; “14MZ 14-Channel Computer Systems” brochure; Great Planes Model Distr. Co., Champaign IL, May 2008. |
Futaba; “4PK-2.4GHz System” manual; Futaba Corp., Japan, May 2008. |
Futaba; “Manual Changes—Instruction Manual—Throttle-cut function”; Futaba Corp., Japan, May 2008. |
Futaba; “R6004FF” receiver manual; Futaba Corp., Japan, May 2008. |
Futaba; 10CAP/10CHP/10CP 10-Channel Radio Control System Instruction Manual; Futaba Corp., Japan, May 2008. |
Futaba; “3PM-X 3-Channel 2.4GHz FASST Computer System” brochure; Great Planes Model Distr. Co., Champaign IL, Hobbico Inc. May 2009. |
Number | Date | Country | |
---|---|---|---|
20110275274 A1 | Nov 2011 | US |
Number | Date | Country | |
---|---|---|---|
61331745 | May 2010 | US |