Sigma Lambda Pi is the perfect thing to talk about on the 3/14 Pi day!
This crazy machine is a 16 Raspberry Pi-4 cluster in a 2U server rack, set to execute FaaS (Function as a Service) with a green-it approach. Don’t make a dream of Raspberry-Pi high performance demonstration, you will be disappointed and it’s not the purpose of this project. This is not a commercial product, the objective of the company who made it, was research, team building and team skills improvement. This has been made by friends of my, working at Be|ys, a team of 9 people, under the lead of Christophe Prugnaud. They made a demo of it during the Clermont’Tech Api Hour #46, the video will be soon accessible.
I’m actually working on a device using a NFC chip from ST. Unfortunately, this chip is not using the ISO-14443 norms but the less usual ISO-15693 one. As a consequence the NFC reader I had were not compatible with this norms. I found a solution (there are not a lot) in Amazon to covert this need. The Fongwah S9 NFC Reader. I made this post to share my test experience of this device.
Precision: this is not a post made for Fongwah, I really have to crash my head on this device and the purpose of this post is to save your time. The fondwah S9 is a nice tool with a multi-language (on top of C library) SDK but it is delivered with no easy documentations, broken links and no reference on ISO-15693 support… I was a bit disappointed once the box opened.
You may have read some of my post about RF433 and Raspberry PI. Basically with RPI 1, I was using wiringPi interrupt handler to manage the RF433 decoding. The problem is that with RPI2 and RPI B+ the delay to take an interrupt that was becomes unpredictable. And the timing constraints are not respected. As a consequence part of the messages are loss because for these delay.
One of the solution (the software one) is to be more efficient to proceed the interrupts and the way to do this is to compile a kernel driver for directly handling the interrupts. This is what this post is about. This comes to complete the RFRPI code and associated hardware. A complete source code and software for using it is on the rfrpi bitbucket repository.
Challenge of the coming days : write a kernel driver to manage interruption quicker on a raspberry pi 2. I’m happy to find a lot of example on Internet and in particular this one, that is really looking like what I’m trying to do. This post is describing all the step needed to do this.
If you want to create a company like infrastruture on Azure you could expect to create a VPN to have a secured access to it and have an internal lan to protect you servers against external access. Basically the system provides all that you need but, as usual in the closed world of MicroSoft. The VPN server based on SSTP protocol sound hard and not documented to be used with MacOsX or Linux.
I’ll describe in this post how I fixed this issue par using an OpenVpn gateway server.
These two last days, I was participating to devoxx in Paris. One of the star topic of the event this year was Docker so I attempt different talk about this container technology I already has discovered in a previous JUG session. It was not an evidence that this technology was more than something interesting for DEV needing small, fast starting, small memory footprint, environment for testing. With my OPS hat, I did not catch the interest. This was before Devoxx and the different talk. The aspects I’ll detailed in this post have not been addressed during Devoxx, as much as I have seen, as mostly the DEV aspects have been addressed, I going to synthesize my opinion.
Really interesting tweet I just saw about the Odroid-U3 platform you can find following this link. This platform with the size of a Raspberry PI board is a 4 ARM core 1.7Gb (cortex A9) with 2GB included. Video is HDMI 1080p.Storage is MicroSD slot. The price is really low : 58$
You can ran even Android & Linux on it.
Compared to a RPI, this sound good for video/media box applications, better than RPI. For hacking this is largely different, as you can see on the picture, GPIO connector are not so easy to access. But, you can also purchase an extension shield providing all what you are expected with 36 GPIO. To build your own shield it could be more complicated than RPI. This let me go to a question I have since months … Why RPI is not becoming less and less expensive or more & more powerful ? it have now about 2 year old.
Less negative point : like any new board coming after Raspberry, the ecosystem is actually really smaller and all third party components (box, shields) is really limited.
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.