Netduino
Quoting the words of Greg Duncan, I’m a "friend of the blog"!
The weekly Friday post on Coding4Fun blog on Channel9 refers to my article on the SPI bus and its use with the .NET Micro Framework (on Netduino board).
It 'a pleasure to be there !
After the previous two articles describing the SPI and I2C buses and their use with the .Net Micro Framework, it is now finally time to see a practical application with my latest project available on CodePlex : uNFC – NFC library for .Net platforms ! Introduction : software and hardware support This library allows to use NFC integrated circuit connected to your PC (via serial) or to embedded system based on Windows Embedded Compact or .Net Micro Framework. It supports all three types of .Net Framework : .Net Framework 4.0 for PC based on Windows 7 / 8 or embedded systems based on Windows Embedded Standard 7 and Windows Embedded 8 Standard; .Net Compact Framework 3.5 / 3.9 for embedded systems based on Windows Embedded Compact 7 and Windows Embedded Compact 2013; .Net Micro Framework 4.2 and 4.3 for embedded systems like Netduino boards and .Net Gadgeteed boards; The library supports NXP PN532 chip but it also defines a little framework so that y ...
Read the rest of entry »
At the same as SPI, analyzed in a previous article, the I2C (Inter-Integrated Circuit) is a synchronous communication bus used to connect and exchange data between a microprocessor and external devices; it was developed by Philips, now NXP, today it is "de facto" standard. Bus description The I2C bus is also known as two-wire as it is characterized in all the effects of only two "wires": SDA (Serial Data Line) : line for the data transfer; SCL (Serial CLock) : clock for data exchange; The lines abovelines are always characterized by a pull-up resistor that has the task of maintaining the signal "high" (logic 1) in conditions of idle while the interconnected components (master and slave) have the task of lowering the level to transfer a logic 0 and release it to bring it back to idle and transfer a logic 1, this behavior is typical of the open-drain lines. Similarly to SPI, you can have multiple slaves connected to the bus and a single master to communicate wit ...
Again, one of my posts on .NET Micro Framework is leading to Coding4Fun on Channel9 in the periodic Friday post on the projects based on the hardware.
This time it refers to experimental SDKs released by Secret Labs for support .Net Micro Framework, the Netduino board and the AGENT smartwatch in Visual Studio 2013.
As always it makes me happy!
The SPI (Serial Peripheral Interface) bus is a synchronous communication bus typically used to transfer data between a microcontroller and an external device (eg sensor, actuator, memory, SD card, ...). Being synchronous, unlike the typical asynchronous serial communication (UART), it uses a clock signal to ensure the perfect synchronism in the transmission and reception between the two counterparts known as master and slave. Bus description Overall, the SPI bus is characterized by the following signals : SCLK (Serial CLocK) : clock for synchronization in the data exchange; SS (Slave Select) : signal for enabling the slave (receiver); MOSI (MasterOut / SlaveIn) : data line used for the transmission from master to slave; MISO (MasterIn / SlaveOut) : data line used for the transmission from slave to master; Excluding the SS signal, which can be handled separately, the bus should be considered a 3-wires bus. The master is responsible f ...
Having already written something similar on the official forum of the Netduino, Chris Walker (Secret Labs) has written a comment to a post on the official blog of the .Net Micro Framework team after meet them at MVP Summit of thi year.
He emphasizes that Microsoft seems to be getting more interested in pursuing .NET Micro Framework development (it is now part of the Windows Embedded team), whereas the processors for embedded systems are becoming increasingly powerful and less expensive (eg, the Cortex -Mx) and the C # and VB.Net with Microsoft development tools can start to make difference, especially by leveraging all the developers who have knowledge of. Net Framework.
In short, it seems that 2014 will be a fantastic year for the framework and for the community !
Before the end of this year, I wanted to enrich my uPLibrary a new managed driver for the dual motor driver TB6612FNG that I used earlier this year in a demo at the Microsoft Embedded Conference 2013 on a robot equipped with a Netduino Plus and piloted through the Kinect (thanks to Clement Giorio). The dual motor driver This Toshiba motor driver allows to drive two DC motors (Direct Current) with a maximum power of 15 V and with four operating modes: CW (ClockWise), CCW (CounterClockWise), short brake and stop. Also, the speed of each motor can be varied through a PWM (Pulse Width Modulation) by changing the duty cycle. On the Sparkfun website a useful breakout board that mounts the motor control and makes it easily accessible pins is available. The managed driver The managed driver that allows the use of dual motor driver is represented by the TB6612FNG class that provides two contructors through which you can decide whether to use just one or both engines. For each engine is called a channel (A and B ...
The Secret Labs, makers of the famous series of Netduino boards and AGENT smartwatch based on .Net Micro Framework, could not wait for an official release by Microsoft and has decided to make available an experimental SDK for Visual Studio 2013 ! Chris Walker has disclosed the news on the official forum and explained that he had used the open source code of .NET Micro Framework to generate this SDK that will no longer be supported by the Secret Labs when Microsoft will release the official one. Obviously, I have not been able to wait and after installing Visual Studio 2013 I downloaded the SDK to be able to try a simple application on my Netduino Plus board. In addition to the .NET Micro Framework SDK, it is also needed to download and install the Secret Labs SDK, also experimental for Visual Studio 2013. SDK .Net Micro Framework 4.3 (RTM) and SDK Netduino boards The SDK installer is related to the .NET Micro Framework 4.3 (RTM) version and it is perfectly identical to the official as well as throughout t ...
New release for my M2Mqtt library, MQTT client available for any platform based on .Net Framework (from the desktop to the micro via the compact), now at version 2.4.0.0 and as always is available on CodePlex and Nuget. Bug Fix : message identifier no longer cross-broker This time the update contains, among other things, an important bug fixes on the message identifier generation for PUBLISH, SUBSCRIBE and UNSUBSCRIBE messages provided by the MQTT protocol. In previous versions, the generation of this identifier was encapsulated in the base class of the hierarchy of messages, the MqttMsgBase, highlighting the anomaly of a message identifier increasing cross-broker, which was used the same variable (static) for the generation also if the client was instantiated multiple times in our application to connect to multiple different brokers. Obviously, the protocol provides that the identifier is bound to the client-broker pair, namely that it is unique for each connection to the broker. .Net Compact Framework 3 ...
This time again with great pleasure, my M2Mqtt library (MQTT client for all versions of the. Net Framework) is mentioned in the "fardware friday post" on the blog Coding4Fun on Channel9 at the following link !
The post highlights the main latest features, support for security through SSL / TLS protocol and event management asynchronously. It is also highlighted my demo on the use of the MQTT client with 2lemetry platform.
The satisfaction is double in knowing that my work is attracting a lot of interest and that the library is increasingly being used. Obviously, this leads me to improve it and in fact approaching many surprises and improvements!
View this page in another language:
