Re: Blue screen sandbagging, was [RCSE] GUI programming for TX's
On Thu, 2 Jan 2003 [EMAIL PROTECTED] wrote: Why would you even want to use a PC for programming? Just imagine firing up your laptop while waiting in the winch line to fix some centering... We could add the blue screen of death as the latest sandbagging excuse... I don't think we're talking about completely replacing the normal programming of the Tx with an offboard GUI. The issue is more that, for first setting up a plane, it would be much easier to have a GUI flowchart (for instance). Mostly, though, I think that something like this: http://www.futaba-rc.com/radios/futj9000.html should be the standard in computer-driven Tx hardware interface (not all 9 channels of it, though; I usually need 2 and sometimes 3). I was just talking to a guy yesterday, though, who was completely stumped by his, which indicates a failure in interface design. He was new to the hobby and was getting pretty discouraged about the whole thing just because he couldn't figure out his radio. So the software interface, I think, has to change. For instance, imaging setting your centers by positioning with the stick and then pressing the Center here button. Then setting the endpoints the same way. To get a Launch Mode, align all your surfaces the way you like them, then press Enter and it moves the centers for the program to the appropriate spot. You can then tweak expo or whatever for Launch Mode in the same way. -J d. o. darnell wrote: The concept of graphical user interfaces (GUI) for programming TX's might at first seem like a good idea. However, attempts to do so have not been successful for several reasons, not the least of which is the market. There are four major manufacturers each having a different hardware setup and programming metaphor. It's possible to write a PC/PDA program to hook up to a TX , display a model with controls and to provide save/restore functions to the TX EPROM, although it is not likely that enough people would be interested in using such software. This functionality already exists internally to some degree in current TXs. Additionally there is no standard or programming model for all existing TX's narrowing the market even further. RCSE-List facilities provided by Model Airplane News. Send subscribe and unsubscribe requests to [EMAIL PROTECTED] Please note that subscribe and unsubscribe messages must be sent in text only format with MIME turned off. RCSE-List facilities provided by Model Airplane News. Send subscribe and unsubscribe requests to [EMAIL PROTECTED] Please note that subscribe and unsubscribe messages must be sent in text only format with MIME turned off.
Re: Blue screen sandbagging, was [RCSE] GUI programming for TX's
On Thu, 2 Jan 2003, Jason Werner wrote: Now that would be funny! Personally though...I don't quite see the need for an external programming type interface unless it added to the functionality of the programming. For example... - A graphical and simple mixing setup. You drag and drop controls in a bin and EASIALLY control wh is master, slave, and the ratios. I think that's exactly what we're talking about here. - Or even better, increased functionality within the programming. Why have a system that simply lets you enter end points? Perhaps the program could increase the mixing, etc. Imagine having a lower tech radio having increased programming functions? It is possible...but unlikely! Oy, now you're talking about actually *controlling* with the computer? I mean, that would be fun, and it's definitely possible, but that's some wicked klunky. In that case, I think you'd want to start with a Palm and write a custom app to talk to a custom-built Tx module with sticks for input. All possible, interesting, difficult, and expensive. -J Jason - Original Message - From: [EMAIL PROTECTED] To: d. o. darnell [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, January 02, 2003 9:34 PM Subject: Blue screen sandbagging, was [RCSE] GUI programming for TX's Why would you even want to use a PC for programming? Just imagine firing up your laptop while waiting in the winch line to fix some centering... We could add the blue screen of death as the latest sandbagging excuse... d. o. darnell wrote: The concept of graphical user interfaces (GUI) for programming TX's might at first seem like a good idea. However, attempts to do so have not been successful for several reasons, not the least of which is the market. There are four major manufacturers each having a different hardware setup and programming metaphor. It's possible to write a PC/PDA program to hook up to a TX , display a model with controls and to provide save/restore functions to the TX EPROM, although it is not likely that enough people would be interested in using such software. This functionality already exists internally to some degree in current TXs. Additionally there is no standard or programming model for all existing TX's narrowing the market even further. RCSE-List facilities provided by Model Airplane News. Send subscribe and unsubscribe requests to [EMAIL PROTECTED] Please note that subscribe and unsubscribe messages must be sent in text only format with MIME turned off. RCSE-List facilities provided by Model Airplane News. Send subscribe and unsubscribe requests to [EMAIL PROTECTED] Please note that subscribe and unsubscribe messages must be sent in text only format with MIME turned off. RCSE-List facilities provided by Model Airplane News. Send subscribe and unsubscribe requests to [EMAIL PROTECTED] Please note that subscribe and unsubscribe messages must be sent in text only format with MIME turned off.
RE: Blue screen sandbagging, was [RCSE] GUI programming for TX's
On Thu, 2 Jan 2003, Tripp Meister wrote: This wasn't about programing from your computer at the field. This is about having the flexability to do your core programing and initial testing on the PC then pushing the program to the TX. It would make the programing of the MPX3030 faster and easier because you would be able to see more of entire program in one screen than on the TX. You could also just have a far better, more intuitive interface. -J -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 02, 2003 6:34 PM To: d. o. darnell Cc: [EMAIL PROTECTED] Why would you even want to use a PC for programming? Just imagine firing up your laptop while waiting in the winch line to fix some centering... We could add the blue screen of death as the latest sandbagging excuse... d. o. darnell wrote: The concept of graphical user interfaces (GUI) for programming TX's might at first seem like a good idea. However, attempts to do so have not been successful for several reasons, not the least of which is the market. There are four major manufacturers each having a different hardware setup and programming metaphor. It's possible to write a PC/PDA program to hook up to a TX , display a model with controls and to provide save/restore functions to the TX EPROM, although it is not likely that enough people would be interested in using such software. This functionality already exists internally to some degree in current TXs. Additionally there is no standard or programming model for all existing TX's narrowing the market even further. RCSE-List facilities provided by Model Airplane News. Send subscribe and unsubscribe requests to [EMAIL PROTECTED] Please note that subscribe and unsubscribe messages must be sent in text only format with MIME turned off. RCSE-List facilities provided by Model Airplane News. Send subscribe and unsubscribe requests to [EMAIL PROTECTED] Please note that subscribe and unsubscribe messages must be sent in text only format with MIME turned off. RCSE-List facilities provided by Model Airplane News. Send subscribe and unsubscribe requests to [EMAIL PROTECTED] Please note that subscribe and unsubscribe messages must be sent in text only format with MIME turned off.
Re: Blue screen sandbagging, was [RCSE] GUI programming for TX's
Oy, now you're talking about actually *controlling* with the computer? I mean, that would be fun, and it's definitely possible, but that's some wicked klunky. In that case, I think you'd want to start with a Palm and write a custom app to talk to a custom-built Tx module with sticks for input. All possible, interesting, difficult, and expensive. i added a mixer to my hitec focus 4am transmitter. the mixer is an analog computer. when i built it i looked at the possibility to build a PIC based digital computer instead. the problem was a DA converter. AD converter for sampling the stick positions is very simple. microcontrollers with sufficient number of analog inputs are available and cheap. at that time i found only one microcontroller that had a built in DA converter. it's certainly possible to create small addon board for simple non-computer radios that would sample the stick positions, send the data to PDA using RS-232, receive the processed data and send it to transmitter circuit. imagine: you can record your manouvres to PDA and replay them later :) only one thing bothers me little bit: reliability of the software. some kind of emergency cutoff switch for fully manual control is probably required to save your plane when PDA crashes. arne RCSE-List facilities provided by Model Airplane News. Send subscribe and unsubscribe requests to [EMAIL PROTECTED] Please note that subscribe and unsubscribe messages must be sent in text only format with MIME turned off.
