Wireless Communications Research Engineer

We're accepting applications for the position of Wireless Communications Engineer, located in Leesburg, VA. Click here for details.

Tuscarora Framework is now Open Source

Tuscarora is a framework for developing highly scalable and portable Network Patterns (NP) and applications. The Framework serves as the narrow waist of the system, decoupling the Application Layer and the Network Patterns from the underlying radio and hardware platform, enabling portability, scalability and extensibility. Tuscarora was partly funded by DARPA.

The source has been released on GitHub at https://github.com/Samraksh/Tuscarora/. Learn More.

About Samraksh  


 Wireless Sensor Network Expertise We are experts in low-power, reliable wireless sensor networks (WSN) with world-class experience and deep, innovative research into the hardware, software and algorithmic issues they present. We design, manufacture and sell inexpensive high-performance, low-power, scalable and easy-to-program components and systems.

WSN-Enabling Products Besides the eMote .NOW and the BumbleBee highlighted below,  we also provide a range of other sensors and supporting items. Complete network solutions can be deployed using these components.


 The eMote .NOW comes with two serial COM ports, COM1 and COM2. COM1 is primarily used to monitor system messages and Debug.Print output via a Serial-USB interface. This is what you're using when you have MFDeploy connected.


COM2 can be used for input and output via the screw terminals on the .NOW. A typical application would be used to connect a .NOW with another device such as a terminal emulator. Or, you could use it to communicate between two .NOWs. To use COM2, first look at your board and inspect the region highlighted in the image below. Each of the solder pad pairs (such as the two for R40 towards the bottom) should not have anything connecting them. If there is, use a soldering iron to melt the pads and tweezers to remove whatever is there.



To connect a .NOW to another device via COM2, you'll use the following pins:





Connector J11

5  GPIO EmoteDotNow.Pins.GPIO_J11 PIN5
 COM2 Transmit
6  GPIO EmoteDotNow.Pins.GPIO_J11 PIN6 
 COM2 Receive

Connector J12

10  Ground   NA


Pin J11/5 doubles as a GPIO and as COM2 transmit, depending on how it's initialized in your program. When you create a SerialPort object on COM2, it becomes a COM2 pin. Similarly for J11/6, COM2 receive. Here's an example of how to connect two .NOWs. Note that J11/5 of each is connected to J11/6 of the other. Ground is wired in common between them.



When you write a program that uses COM2, you might find that nothing is happening on the serial port. The probable reason is that you are using the Visual Studio debugger or the eMote .NOW is attached via MF Deploy. In both those cases, Micro Framework (upon which eMote is built) automatically rounts ALL serial traffic to COM1. Hence when you run the program, you cannot use the debugger or MFDeploy. If you want to monitor the system and output from COM1, you can attach via a terminal emulator such as PuTTY. You'll configure the connection as Serial, provide the COM port used by Windows, and set the data rate, stop bits and protocol according to how you've defined the SerialPort in your eMote program.