TD LAN range test

Posted on by
4

Telecom Design LAN capability is a 9600bps rf 868 transmission you can use with the sigfox modem to communicate between multiple TD120x devices. One of the main use is to have multiple sensors communicating to a sigfox gateway. The communication get benefit of the nice ultra narrow band RF transceiver included in the chip.

TD LAN is based on GFSK modulation on 25kHz channels working at 9600bps.

I did really remember where but I read it could reach long distance in the best conditions, so as it could open many opportunities, I wanted to test it in real conditions to see what we could get from it.

Continue reading →

Get start with the SigRPI Shield

Posted on by
3
Raspberry PI Shiel Hat standard

Raspberry PI Shiel Hat standard

The SigRPI shield is a HAT standard board providing SigFox connectivity to your Raspberry PI. As it is not certified for this network it can’t be used in production for this usage, but you can use it as a long range RF that does not need certification. I will later details this with a project related to this function.

By-the-way, the purpose of this board is to let you play easily with sigfox. The raspberry-pi offering a really efficient way to code and to make prototypes.

The shield comes with TD1204 (including accelerometer & GPS) of TD1208 (sigfox modem). You can use it with the standard firmware or upload your own one.

The shield can be ordered in the shop section : here

This posts details how to setup it and use it.

Continue reading →

Use cflash tool to upgrade Telecom Design Firmware

Posted on by
Reply

In the Telecom Design SDK, you have a cflash tool you can use to reflash your firmware from a serial port. This can be usefull to reflash a TD chip from another chip of from an embedded platform like a RaspberryPI.

This peace of code is not really nicely documented, so to avoid spending to many tries, here is the result of my investigations

Continue reading →

Backed Domino IO project !

Posted on by
1
Domino IO - IoT enabler

Domino IO – IoT enabler

I do not usually post more than a tweet when backing on a KickStarter project but as for this time there is a French guy included  in the project, it is a good opportunity to do it !

The Domino IO project is an interesting platform to connect one of your home stuff ! It contains a powerful CPU, the network connectivity and all what you need to quickly make your own design.

This platform is really looking like the SparkCore under steroïd having eaten a Carambola engine. The chip is provided for $10 on Kickstarter ; this is 2.5 time less than carambola and 2 times less than Sparkcore. Sound like the missing element between RaspberryPi and Arduino.

Continue reading →

IoT disruption, why it is the appropriate time ?

Posted on by
2

In a previous post I explained why the IoT is appearing in this period thanks to the network technology evolution. It would not be a complete analysis if I would not care about the social evolution. In parallel of IoT and technologies there are other rising trends : Makers, Fablabs, embedded systems, 3d printing and crowd-founding.

Take a look at personal computing some decades ago when guys like Jobs or Gates make the first line of code and solder the first micro-processors in their garage ; they just used the technological elements available that time and were able to make them doing much more than what they have been made for. They did it because they were able to do it. The same story appends in the late 90’s with Internet : anyone was able to code some PHP stuff and create a service in his garage thanks to this students have created Facebook and many more.

At the opposite, when smart phone appeared in the middle of the 90’s it was a technology that requires strong industrial assets and this technology has been limited to major companies. The smart-phone revolution had been the same opening door to programmer to an new area with applications (apps). In fact all previous hardware evolutions since the Personal Computer beginning was requiring huge technological assets to be part of it.

IoT disruption is breaking these last 40 years where only software were hackable by getting hardware accessible.

Let see why

Continue reading →

IoT, M2M, quick panorama on main technologies

Posted on by
1

rfrpi_3This year M2M and IoT are two of the most heard keywords in our technological domain. One of these is fresh new, I mean a couple of year old, when the other one is pretty much older. M2M, standing for Machine to Machine is a capability for two machines (or more) to discuss together and take actions. Like a temperature sensor allowing your boiler to decide when to start or stop. In the industry where automatism are in place since many year, M2M is something in place, running, not new. IoT, standing for Internet of Things is part of the M2M technology but actually raising. In IoT the main word is Internet and it stands for the capability of an object to talk over Internet on its own. Why only now ? mostly because now it starts to be possible.

Continue reading →

Design a raspberry Pi HAT shield

Posted on by
10
Raspberry PI Shiel Hat standard

Raspberry PI Shiel Hat standard

When you want to design a shield for Raspberry Pi, you have to follow the HAT standard. This standards describes the form factor of the shield to ensure future compatibility. It also describes the configuration solution for the board based on a flash containing necessary information. The Hat standard link gives all the detailed specification to design a such shield. In this post I’ll describe my experience of designing such shield and you will find the basic elements I build and now sharing with you.

Continue reading →

I2C activation on raspberry PI B+ and 2

Posted on by
Reply

The new version of kernel now activate the device-tree standard, it means that instead of having all module activated by default with some stopped by a blacklist system, now, all are disable and activated only when described in a device tree.

Device tree details the system architecture and dependencies following configuration files. The device tree can be owned by the shield itself in an attached eprom.

As a consequence, now, i2c / spi are not activated by default. So if you need to activate it on startup. For this, edit /boot/config.txt and add line at the end like :

dtparam=i2c_arm=on   # for i2c 1
dtparam=i2c_vc=on    # for i2c 0
dtparam=spi=on
dtparam=i2s=on

dtparam=i2c_arm=on,i2c_vc=on

Then reboot