Comment by Martin Peres on December 21, 2010 at 12:46pm

Oh, kuddos to Microchip!

 

Not sure I understand this paragraph, but I don't know this device so I guess it is normal.

 

When on the field, I guess no-one will ever have a public IP or be able to do source-nat (port fowarding). That's why I was proposing the use of a third-party server.

Comment by Russkel on December 21, 2010 at 4:55pm

How is it difficult to talk to the USB module with a microcontroller? I thought you would communicate with it using serial.

Either using a USB host shield or (forgive me I am not very well versed in the detail of microcontrollers etc) from my research there is a Serial-to-USB chip on the board.. could the serial just be tapped into before it reaches the chip and bypass the USB all together?

Comment by Tom Pittenger on December 21, 2010 at 9:44pm

@Martin - Good call about the third-party server solution. Do you recommend any?

Comment by Paul Mather on December 22, 2010 at 7:39am

Nice work! You need to get more footage of that good lookin' GCS software! j/k :)

Comment by Tom Pittenger on December 22, 2010 at 11:22am

@Happy - By new years I'll have a new video which will be much better and will include more GCS because GCS is what makes this awesome! Great job on the software. btw, Next week I'm planning on hacking at your code to add in a threaded TCP/UDP server directly into GCS. That FTDI loop-through thing I did is ghetto!

Comment by Paul Mather on December 22, 2010 at 12:28pm

Let me know what you find out and I'll add it to the release version too!

Comment by Paul Mather on January 2, 2011 at 12:43am

Version 1.1.27 now *supports* TCP and UDP. It's my first attempt. What I'm not sure about is if the GCS is supposed to be the Server or the Client... and with UDP I guess I would need to specify a server to listen to. Right now, there's no error trapping, there's no feedback on connect success or failure and you can only specify a port on the local server to listen to for TCP or a local port for UDP... In the case of TCP, my GCS is the server waiting for a connection, but this might be backwards.

Comment by Tom Pittenger on January 2, 2011 at 6:41pm

Happy,
I'm terribly sorry - I've slacked in this department. I've been out of town and when I got back I had all kinds of silly things I had to do. I haven't even had a chance to make another video :(

I see the TCP/UDP option in GCS 1.1.29, nice job! When I put in a DNS name it crashes. It was connecting to an embedded TCP telnet server that wasn't sending anything useful, not sure if that matters. Anyhow, I plan to look into this tomorrow and give you some more constructive input about TCP/UDP. Maybe download the source and just make it work and send you a video!

Comment by Paul Mather on January 2, 2011 at 7:24pm

Let me know about the TCP server/client issue. I just tried to do some testing across the network and nothing seems to work. On my local PC everything works fine with both TCP and UDP. I've noticed that with TCP it handles everything quite well....even at 50Hz. With UDP there's major lag once you crank it up above about 10Hz....

 

I'll do some more testing with the DNS

Comment by Tom Pittenger on January 2, 2011 at 7:46pm

In my application the GCS must be the server although it would be nice if it could do both, you know, just for fun. It must be the server because cell phone IPs are behind a NAT firewall which is not user configurable. That means all communication must originate from the cell phone/aircraft so the NAT tunnels a port.

Comment

• ‹ Previous
• 1
• 2
• 3
• Next ›
• Page