Ok, new direction. It just isn’t worth the trouble it would surely cause returning these modules so they are yours to keep. I am still interested in making a carrier for the module so go ahead with the design. You can also put the holes for the xport connector. Holes are cheap. 
lol
The board size is 3" x 2.3" with 4 x 0.125" holes spaced in 0.150" from each edge.
Thanks Jim,
It will be interesting to see what cost estimate will come out for this setup. That is:
$53 - for Matchport B/G (Order 100 at a time from Gridconnect)
$46 - XPort …
??? board plus the Ethernet connector plus magnetics…
I will also continue along with some other ideas as well…
Simply use the Matchport for the RS232 communications. Use wireless camera (+$25 for trendnet TV-IP110) Probably cheaper than using XPort and camera runs at full speed.
WiFly - Not sure this is any better priced than matchport. Example sparkfun.com/commerce/produc … ts_id=9333 Max speed is 1mb for serial or 5mb SPI…
The router… Yes I know it may be too DIY, big…
Also been looking around at different wireless IP cameras, to try to find one that might allow other things to plug into them. I have found a couple like (brickhousesecurity.com/ipcam … ubid=27492) but nothing so far that I have found any good information on. It would be great if all we had to do was to mount the camera, and plug in some form of connection from the camera to the robot… I suppose one could try to hack up one of the cameras that have pan/tilt in them and try to intercept that as controls to the robot, but again DIY and not sure how fast those signals can change…
XBee/Wireless camera… Mentioned before. Likewise Bluetooth…
But Regardless I think you could start setting up the software for the control panel and probably make it reasonably independent of the underlying communication method. That is you can have a configure camera dialog that the user probably needs to specify the IP address and port number. This will probably be true for all of the different methods mentioned above…
Likewise will need some form of communication setup for serial link. For many of the different options, you will probably again need to specify a comm port and a baud rate. For some versions may want to specify a few other options, For example xbee may want to do a query to find out which modules are out there and choose. For Some of the Ethernet based solutions, not sure if you will be able to choose the IP address/port or will assume that has been mapped for you externally. Also not sure if you will have some form of configuration with it. Each of these input methods could define some form of IO function to call to send a packet and to receive packets…
The rest of the stuff could be reasonably independent of the underlying link…
Hopefully
OK, Will do.
Thanks for the hardware!
I’ll start working on the board schematic and layout. I’ll make “paper parts” until we can all sign off on the design.
Not sure of the space yet; Lantonix + XPort connector.
You want traces with those holes? ;>)
Yes, those are the dimensions I’m working from.
Power input connector you use? and footprint? Sparkfun preferred?
Alan KM6VV
You’re welcome. 
The module is 1.75" x 1.75", so there should be ample room for the xport. What do you mean footprint and sparkfun format?
Footprint is the pattern that goes on the PCB for a part. Sparkfun has a selected list of parts and schematic symbols/footprints to go with them. Saves having to “create” the schematic symbol and footprint if an Eagle user hasn’t done it already for you.
Yeah, sounds like it should fit…
Alan KM6VV
Ah, I only used “footprint” in the context of the boards overall size. lol
I got it…
Yeah, I suppose the word could have several meanings, even in PCB work!
What hole size do you specify? Plated, as I recall? I will examine the BBII board for reference.
Sorry guys, we had high winds up here last week and we lost 3 LARGE willow trees(one was over 5ft in diameter!), one of them went through our barn so i’ve been a little DiStRaCtEd cleaning up the mess(willow trees may look nice, but they are filthy trees to cleanup…). I’m ordering an Xport and it should be here by the end of the week or next Monday anyways. Just have to come up with a board to interface this with the Matchport b/g and start testing. Jim it is really nice of you to let us keep these eval boards and modules, thank you…
You are are welcome for the parts.
Well this project was intended to be a vehicle for demonstrating the video capability of the new Flowstone programming environment. I have decided to replicate one or two of the more popular modified router methods to get this going. We will start a new thread for the project when we get further along.
Although it’s not what we had in mind originally, we should go ahead with the carrier board. I think I will scale back the number of boards though.
The MatchPort Demo board schematic shows an integrated 140-306-R (?) RJ-45 connector; although I haven’t found a BOM. I need to know the manufacturer and the correct part number. It appears to be the shielded part.
I’ve used the Halo part before, but I need to know the specifics of the turns ratio, and
inductance of the recommended part.
Jim, do you have a contact, or could you contact them?
Thanks!
Alan KM6VV
Edit:
Actually, if you want to use the XPort, I guess that would be the XPort footprint. THAT, I’ve found, looking for the MatchPort.
Maybe worth taking a look on this sites.google.com/site/bifferboard/Home/howto/using-a-bifferboard-as-a-webcam? Small linux system, very low power consumption, can get one UART and 1 SPI (or I2c or SD) plus can do video streaming over wireless pretty well…
I’ll be starting a new thread for this tomorrow, but here’s a sneak peek… 8)
Here’s a simple, working solution for connecting an SSC-32 to your network! (picture is a link to the product)
images17.newegg.com/is/image/newegg/12-270-327-Z01
I’ve got this connected to a rover with a wireless router and IP cam… and it works! 
More words on this tomorrow, but this project is looking up!
Here sharing best information for you. To design a prototype PC board to carry the Lantronix WiFi Module for controlling an SSC-32, and other options yet to be defined. The end result is a remote piloted rover controlled from a laptop computer. We will provide the front end, using FlowStone graphical programming environment.
The Lantronix modules were a dead end. No support, extremely high cost with no reasonable discount structure for making it part of a product. No thanks!
