Ground Support Terminal next steps

[Dan Bowen]

Hi Pat,

Nice work thus far on the ground terminal, that was very helpful this week.  The next thing that would be extremely helpful ASAP is getting the commands up top to work - particularly the following ones, as we finish comm controller programming:

Display all variables: 0x05 0xFF

Set Data Sample Rate: 0x05 0x06 0x## 0x##

Set Data Transmit Rate: 0x05 0x07 0x## 0x##

Also the units used (s for seconds in this case) tooltip popups or something indicating the valid ranges that can be entered would be nice.

Thanks,

Dan

[Pat McCarthy]

Tooltips implemented

(OK, they are there, but the ranges are not accurate….. Working on it J )

 

Patrick McCarthy

 

T 502.476.9878

C 502.939.1756

pmcc...@humana.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

[Everseeker]

Ummm, the elements you asked for are not among the implemented ones. But I think that the generic "send" field is implemented....

[Dan Bowen]

They need to be implemented please. send field is not appropriate, these are most highly adjusted of all the values.

[Everseeker]

Try the other data points. See if they work.
I didn't design the hex encode/transmit routine so...
I will work on reworking the interface to add the functionality you need

[Everseeker]

Look at the interface.
In addition to the 3 new fields, are there any others that you will be wanting? It's easy to design the interface, but a ROYAL pain in the ass to change one :-)

[Everseeker]

So, if you can send me complete requirements, I will design version 2.0 of the interface

On Mar 14, 2012 12:56 PM, "Dan Bowen" <stea...@gmail.com> wrote:

[Pat McCarthy]

If you can ge the new requirements this morning, I may have it ready for the meeting this evening

 

 

Patrick McCarthy

 

T 502.476.9878

C 502.939.1756

pmcc...@humana.com

 

[Dan Bowen]

Will try!

Sent from my iPad

[Jonathan Clark]

Hey guys,
all the commands are implemented in the sense that the buttons that send the commands are already active and there are functions already built for each button and command. There is a variable for each command that you just need to set as the hex string that you want to send and it will start working.  There is a seperate function that validates values to be entered and merges them with the command string. Thats all setup and active. 

I left the hex codes blank because we couldn't verify the ones on the wiki were correct, but everything should alread be setup.

Jonathan Clark
jdc...@gmail.com

On Mar 15, 2012 12:33 AM, "Dan Bowen" <stea...@gmail.com> wrote:

[Everseeker]

Look at the code... (well, at 11am)  it's not quite as you had it.
I didn't see what you described.
By the way, if the wiki hex codes are wrong.... Dude.....

[Dan Bowen]

What do you mean by try the other data points?

The presence of tooltips is nice,  but the actual valid ranges are needed, if you couldn't find them, they're on the same page as the commands:

http://wiki.whitestarballoon.com/doku.php?id=software:speedball1:uplink:commands

Please add units to tooltips, as in (s) or (m/min) etc, also on that page.

Sent from my iPad

[Dan Bowen]

The wiki is fine, what are you talking about?  See my examples in the first email for an example of the proper address, command, and data to send

Sent from my iPad

[Everseeker]

Question: the send routine takes the data and type and sends it to the validation routine. If the data is the wrong type or is missing, it's failed. Cool
But
The only way I can see to send "dataless" commands is to send a 0x00 along, and that may cause a problem. Did you have a different workaround that I am missing?

[Dan Bowen]

Seems to be ok with the extra 0x00 when I just manually used send for the 0x05 0xFF anyway, likely that will work.  

Sent from my iPad

[Jonathan Clark]

Not sure what codes they were, but I just remember the first two I had entered when we were first testing had a problem with what was actually documented in the wiki, but that was months ago so it may be fine now. 

I have valid ranges on all  the boxes already.  If you hover the mouse over each box or title there should be tooltip window that pops up and tells you what ranges and values can be entered.

There main send function has a number of arguments.  One is the command hex and I believe the last was a value to send.  You can use the function and not enter the value and it will just send the command.  I think this is what you were asking about.

I do remember one thing that is slightly different then what I described in the previous message.  You should see a function for each button in the code.  Each function is called when the corresponding button is pressed.  Inside each function is the send function which should be have it's command arguments set as the corresponding variable that hold the hex string.  I may have actually just put in the hex string during testing instead of using variables but the variable are there in the wsfunctions file.   

[Jonathan Clark]

Pat,

Just to clarify, if you don't enter a value, the function does take care of skipping data validation and just continues on to properly formatting the string and sending it out.

[Dan Bowen]

Addresses for all modules are here: http://wiki.whitestarballoon.com/doku.php?id=protocolguide#white_star_i2c_addresses

Use Hex Address not Arduino Hex Address

Sent from my iPad

On Mar 15, 2012, at 9:49, Everseeker <evers...@gmail.com> wrote:

[Pat McCarthy]

If $send = "" And $hex = "" Then ;check for no data or hex

                                _wsdbug("_VerifyData: No Data and No Hex, Should exit now", 1)

                                $dataerr = 9

Send = the data value

Waaaait…

;datavalue to send, data type(si9n or unsi9n), number of bytes, command to send, hex optional send specific hex instead of data value

Oh, I think I get it…. Fixing send strings now…

 

 

Patrick McCarthy

 

T 502.476.9878

C 502.939.1756

pmcc...@humana.com

 

From: white-sta...@googlegroups.com [mailto:white-sta...@googlegroups.com] On Behalf Of Jonathan Clark

Sent: Thursday, March 15, 2012 10:15 AM
To: white-sta...@googlegroups.com

[Jonathan Clark]

P.S. feel free to change and odd placed "9"s to "g"s.  I had no "g" key on my laptop at the time I was writing the code. :)

[Jonathan Clark]

Also, I don't know if you already realized this or not but...

I have loaded the code with "wsdebug" commands and there should be a wsdebug window variable.  If the variable is set to a box number within the gui it will then start sending out debug messages to that window.  I originally was going to add a debug toggle button on the gui that would pop open a seperate window but just didn't get to that point, but it was still helpful for me to be able to turn it on and send it to one of the main windows so I could see what was happening.

[Pat McCarthy]

HAHAHA… I was wondering about that J

I changed em in lots of places… missed that line

 

I changed the wsdebug to send to the console. Too confusing to send it all to the output windows since they are all “in use” now

It LOOKS like all is working, but I would feel better if someone was able to say, Yup, the board IS seeing the data you send, and is reacting correctly

[Everseeker]

Last was for Jon...
Dan, I will prettify the tooltips in a few minutes

[Everseeker]

Ok, the actual send line was commented out...  D'oh!
Fixed.
Tool tips, fixed
Send was sending some number before the actual hex...  Suppressed unless I need to put it back
Jon -look at the code, see if I am missing something massive

[Everseeker]

Dump x grams ballast is broken... Debugging after the game O:-)

[Jonathan Clark]

WOAH!!!! Hold on Pat.

There are a few types of send functions.  Originally the software was wrote to talk to the bus pirate which needed to be sent asci characters, after the bus pirate was removed I had to rewrite a lot of code to make it send actual HEX which the ground controller then just repeats over i2c.  Make sure the send command you are uncommenting is not an old one.  The one you want to use should make use of the SENDHEX function I put in there. 

[Jonathan Clark]

Pat,

the last check I performed with the software was working and sending and receiving correct data from the ground control board.  If you look at the method used to send data from the first button that has a value box (top left of gui) you will see the correct method used for sending.  I did not realize we were still trying to speak to the ground controller, I just thought you were trying to optimize and understand some of the code. 

[Dan Bowen]

The send manually field was working, but I've never seen any of the fields or presets working yet, have only tried a few though

[Pat McCarthy]

So…. Jon, You will be there tonight, right?

 

Patrick McCarthy

 

T 502.476.9878

C 502.939.1756

pmcc...@humana.com

 

From: white-sta...@googlegroups.com [mailto:white-sta...@googlegroups.com] On Behalf Of Jonathan Clark
Sent: Thursday, March 15, 2012 3:48 PM
To: white-sta...@googlegroups.com
Subject: Re: {WhiteStar} Ground Support Terminal next steps

 

Pat,

[Jonathan Clark]

As of the last time I checked with the software plugged into the ground controller, the send field and the first value send box was working.  I used that box to figure out how to correctly send to the values to the ground controller.  From that point the only thing left to do was just enter the hex command strings for each button.  I had tested the command only buttons using the flight phase 1 and 2 buttons which we set to the "return all sensor vaules" command, which did work when tested.   

[Jonathan Clark]

Hey Pat,

No I can't be there at all during the week right now and rarely on some weekend days.  I hate that I can't be there, but it's just not possible right now. I will keep my email open and if you wan't to start a google hangout I may be able to jump in there as well.  I tried teamviewing into the pc this weekend to work on it but there were 4 other people trying to get other things working as well.  I could try teamviewing in again this evening if no one else is on there.

[Pat McCarthy]

Johnathon Clark:

OK, We need to talk… and work together, ESPECIALLY before I attempt V 2.0 I will bring my laptop…

First, the code I saw when I got the key to the directory did not even compile (End Function was missing in 1 spot, and a next was commented out in another spot, so I did not have a stellar start point.

I pushed all I found down 1 level & pulled working copies up… (you can see the pushdown folder in the drop box)

 

Next, working with no knowledge of future implementation “plans”, I may have reinvented the wheel a wee bit J

OK, it sounds like I may have reinvented quite a bit… including the Hex assignments. I created an entire raft of cmd_ codes that are phrase type, for readability….

Task 1 was to config all the output windows to display (done) and to do so legibly (Also done)

Task 2 was to config all the data transmit windows… I followed the lead of the 1 that was done, and did all the rest

Since task 2 began, I’ve been asking… need to confirm data is actually getting sent, and is “correct”

 

I worked with the code that was not commented out, figuring that it was “correct”

PLEASE, look at what I have, to see where we need to make changes:

1.       How do I configure  imperitive commands, with no data

2.       IS the thing sending

3.       Is it sending to the right place

4.       Is the data “correct” (Correct hex codes)

5.       What in the world is wrong with the @!*$&)%#&)! Dump x grams of Ballast button…

6.       Thoughts on my plan to tabularize 2.0 (Raises the Koda complexity, but I’ve done it before)

 

 

 

I will be at the space as soon as I can, to work on the Makerbot… ~8, I’ll get with you to work on the above

[stea...@gmail.com]

Pat, to see if your data is getting to the gsp you should check for the SACK I think, or again- the flight computer will acknowledge all the command to send to it with English, and the hacks that you sent. Just try that and if it works code is working.

Thanks,

Dan

Sent from my iPhone

[Everseeker]

Found the problem. Will fix tonight
Brad,can you do something to reduce the amount of heartbeat text streaming into the ground support board.?  It's hard to work with the text streaming faster than I can read...

[Brad Luyster]

Unless it's broken, the flight computer should be sending only a couple dozen lines of text per minute.

[stea...@gmail.com]

He reduced it a lot last night, see how it is now

Thanks,

Dan

Sent from my iPhone

[Pat McCarthy]

1.       I think I found the problem… will fix it tonight

2.       I loaded 3.8.1 Autoit3 and SciTE on the computer, you can now drive the thing thru team viewer while watching the console (yea)

3.       A google hangout…. Oh lord, ANOTHER connection tool?  I want my ICQ back J