I suggest we consolidate the CLI functions and GCS into a new Comms.pde and obsolete the CLI and GCS. This will allow us to do all configuration and managing from a single application at any time we want or need to. We need to possibly incoorporate some security to prevent users to change vital settings while in flight. I know there have been issues with CLI over XBees, not sure whether this can be tackled or it is as simple as setting the XBees baudrate to 111000 instead of 115200.
Hope to get your feedback quickly; I'm halfway through combining the two :)
Comment #1
Posted on Feb 11, 2011 by Happy HorseI strongly support whatever you suggest, Kim! ;) Getting rid of the CLI is a great idea and comes very handy for beginners. Also it's reported that 111000 simply works.
Comment #2
Posted on Feb 11, 2011 by Grumpy ElephantI hope that user with no xBee, will still be able to config the Quad ;-)
Comment #3
Posted on Feb 11, 2011 by Quick BirdWithout Xbee is no problem; as soon as #define SerXbee is uncommented, all this works over the USB FTDI connection. The advantage I see is that we can add loads of help lines describing what a function does. With help from the menu, we can organize functions into categories, which aids with understanding whether a function is something a newbie should try and use, or not ;)
Comment #4
Posted on Feb 11, 2011 by Quick BirdOh ! I've been using this with my 900Mhz Xbee, and it works just fine on 115200 baud.
Needs some tweaking, this consolidation, but it's already in Dev_trunk in case you guys want to give it a whirl ;)
Comment #5
Posted on Mar 1, 2011 by Swift RhinoComment deleted
Comment #6
Posted on Mar 1, 2011 by Swift RhinoHi Kim,
None of the Configurators is working. I can not see any PID values in the latest Configurator and in the Old Configurator I can not adjusted any PID values.
Greetings, Hein
Comment #7
Posted on Mar 1, 2011 by Quick BirdHmmm, that's weird. Pretty sure I tested this. Could you guys assist, cause I'm not going to be able to sit down and code until at least somewhere next week :(
Comment #8
Posted on Mar 1, 2011 by Quick BirdWhat should be tested is if the serial commands work via Serial Monitor. If not, is SendSerialTelemetry actually fired ? Sorry I can't actively contribute right now guys, I'm away from home till at least tuesday next week.
Comment #9
Posted on Mar 4, 2011 by Swift RhinoComment deleted
Comment #10
Posted on Mar 4, 2011 by Swift RhinoHi Kim,
I have Windows Prof XP (service pack 3). Do you think that could be a reason for my problem.
I am currently running the exe.file under debug or release then I get a error "system could not find the following file "touchless.Vision"? I just normally press continue..... Which exe file should I run under debug or release? I did install Microsoft.net framework 4. Am I suppose to run some installer for this configurator?
Please help. I have no experience in Visual Basic.
Last question. I downloaded Visual Basic Express. Will I be able to use this to compile and make changes to your configurator?....I would like to play with it..
Thanx, Hein
Comment #11
Posted on Mar 4, 2011 by Quick BirdHey Hein ! The latest version of the APMC was that of Krokodil. I added him to CC. I had these same issues with the Touchless.Vision thingy until Krokodil sent me an update; not sure whether he had updated SVN by then, so I'm not sure what we should and shouldn't be able to do with that version right now. Visual Basic Express 2010 is exactly what you need to open the project and play with it ;) I'll be back sometime next week and hope to find some time to tackle some issues, but sure hope you guys can have a look at COMMs.pde in Dev_trunk as well.
Status: Started
Labels:
Type-Defect
Priority-Critical
Usability