Difference between revisions of "User:Bertrik Sikken"

From RevSpace
Jump to navigation Jump to search
(37 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
  |Tagline=heb ik niet
 
  |Tagline=heb ik niet
 
}}
 
}}
 +
 +
You can reach me at bertrik@sikken.nl or bertrik@gmail.com
  
 
Studied Electrical Engineering at Twente University.
 
Studied Electrical Engineering at Twente University.
 +
  
 
Main interests:
 
Main interests:
 
* reverse-engineering things (USB stuff, mp3 players), working on http://rockbox.org
 
* reverse-engineering things (USB stuff, mp3 players), working on http://rockbox.org
 
* studying bats and making electronics for recording/listening to bat sounds
 
* studying bats and making electronics for recording/listening to bat sounds
* software-defined radio
+
* radio stuff, in particular software-defined radio
 +
 
 +
 
 +
Projects I work(ed) on ([https://revspace.nl/index.php?title=User:Bertrik_Sikken&action=purge refresh]):
 +
{{#ask:[[Category:Project]][[Project Contact::bertrik]]
 +
|?Project Status
 +
|headers=show
 +
|link=all
 +
|order=ASC,ASC
 +
|sort=Project Status,Project Name
 +
}}
 +
 
 +
 
 +
== Project ideas ==
 +
This is a list of ideas I'm thinking about, but have not fully developed into an actual project yet.
 +
 
 +
=== investigate STM32F103 microcontroller ===
 +
The STM32 family of microcontrollers looks quite interesting.
 +
 
 +
You can buy inexpensive [https://nl.aliexpress.com/item/STM32F103C8T6-ARM-STM32-Minimum-System-Development-Board-Module/32327927921.html STM32F103] boards with the following functionality:
 +
* Cortex M3 processor running at 72 MHz
 +
* 64 kB flash, 20 kB RAM
 +
* 2x ADC with 1 microsecond conversion time
 +
* USB interface
 +
 
 +
The plan is to get a bunch of these and play with them, for example see if it is fast enough to sample ultrasonic audio and store it on an sd card (so it can be used as a super cheap bat call recorder).
 +
 
 +
See [http://grauonline.de/wordpress/?page_id=1004 this page] for more information on using these in the Arduino environment.
 +
 
 +
=== investigate quadcopter remote control ===
 +
It turns out that the typical little cheap Chinese quadcopters use a remote-control protocol that can be easily recreated using the famous NRF24L01+ chip (< $1 and easily connected to an arduino).
 +
This gives nice opportunity to either:
 +
# transmit our own control signal, to control a quadcopter from something different than the manual remote control, e.g. automatic control
 +
# receive the control signal, so the manual remote control that comes with a quadcopter can be used to steer other things (like a model car).
 +
 
 +
I haven't found a good overview of quadcopter remote control protocol specifications yet, there seem to be plenty examples of "here-is-the-code" however.
 +
 
 +
=== TTN gateway info panel ===
 +
Problem: if you're running a gateway for the-things-network (TTN), you can see packets coming in by following the packet forwarder log file, but it gives very limited and rather cryptic information.
 +
For example, you don't see which node sent a message, so you have no idea how many unique nodes are sending data through your gateway.
 +
 
 +
This idea is about creating a simple info panel that you can run directly on the TTN gateway itself.
 +
The plan is to write this in Python.
 +
A typical gateway probably already runs some sort of Linux distribution which has the python binaries available or allows them to be installed easily.
 +
Using Python also means that you don't need a compiler/Makefile/etc.
 +
 
 +
Basic operation of this utility:
 +
* the gateway software is configured to send its data not just to TTN but also to the gateway info panel utility (running on "localhost"), using the poly packet forwarder
 +
* the utility listens on a specific UDP port, accepting data according to [https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT the Semtech v1 protocol].
 +
* it parses the plain JSON metadata (modulation parameters, like frequency, LoRa mode, SF, BW, etc.)
 +
* it also parses the payload bytes, part of the payload is not encrypted, so we can extract the message type, device address and sequence number (FCNT).
 +
* all incoming packets are shown in a table-like view in the console using the [https://en.wikipedia.org/wiki/Ncurses ncurses] library.
 +
 
 +
Initially, the utility will just keep the packets in memory, so it just shows things that happened since you last started it.
 +
Later, we can decide to store the data, for example in a database.
 +
 
 +
The information shown can be just the incoming messages in order of arrival, one line per message.
 +
Alternatively it could show a kind of node-centric view, one line per device with info only on the latest message from that node.
 +
 
 +
=== mini word clock in dutch ===
 +
Basically an monochrome 8x8 word clock, in Dutch, showing local time in the Netherlands.
 +
 
 +
[https://github.com/bertrik/miniwordclock This git repo] has the current code.
 +
 
 +
See [https://plus.google.com/103276078656203197145/posts/7ki7rpJzk3a here for a demo] running on an arduino nano.
 +
 
 +
The plan is to run this from an ESP8266 instead of an arduino nano, so it can get the time from the internet using NTP. The time offset will be fixed to Dutch local time, i.e. GMT+1 taking into account summer time. Summer time will be determined using the general rule "from 2:00 local time on the last sunday of March until 3:00 local time on the last sunday of October".
 +
 
 +
=== Inexpensive CO<sub>2</sub> sensor ===
 +
TODO: move this to its own page.
 +
 
 +
Status: works as a basic MQTT sensor, see topic "bertrik/co2" on test.mosquitto.org
 +
 
 +
See [https://github.com/bertrik/mhz19 this github repo] for code.
 +
 
 +
Use the [http://www.winsen-sensor.com/products/ndir-co2-sensor/mh-z19.html MH-Z19] sensor module (about E22,-) to measure the CO<sub>2</sub> concentration and an ESP8266 (like a WeMos D1 mini board) to push the measurement data over the internet to a MQTT server. Possibly I can use [https://www.esp8266.nu/index.php/ESPEasy ESPEasy] which makes configuration easy (through a web interface), I'd have to add support for this particular sensor -> ESPEasy seems pretty complicated to get changes accepted, has existing bugs that are not addressed, probably better to write my own custom code.
 +
 
 +
=== Understanding LoRa ===
 +
Ultimate goal is to create an SDR algorithm to decode LoRa without the need for dedicated LoRa hardware. This could be useful when tracking HABs transmitting LoRa for example. See [[DecodingLora]] and [[EncodingLora]].
 +
 
 +
In particular, I should definitely check out [https://github.com/rpp0/gr-lora this gr-lora project].
 +
Perhaps make it work for decoding balloon telemetry modes.
 +
 
 +
=== Cypress PSOC5 ===
 +
Play with the Cypress PSOC5 platform, which combines a ARM Cortex-m3 processor with configurable analog blocks. I'm thinking of combining it with a 24 GHz doppler radar sensor, to process the signal and present it as a USB audio device (stereo signal contains I and Q parts). See [[RadarOnAStick]].
  
Old project ideas:
+
=== Android HabAlert app ===
* do cool stuff with NRF24L01+ modules, e.g. connect one to the SPI bus of a Raspberry Pi
+
see [[HabAlertApp]]
* experiment with [http://mqtt.org MQTT], a light-weight publish/subscribe framework for telemetry data
 
* put the things above together in some kind of home automation project
 
* build a colinear antenna out of RG-6 coaxial cable for the 70cm band (for receiving high-altitude balloons)
 
* more radio stuff with the ham-it-up
 
* implement dominoex/thor radio mode for a balloon payload, perhaps build a light-weight reusable library
 
* come up with an algorithm to determine position/direction of bats as they pass a set of ultrasonic microphones, see [[StereoBatRecorder]]
 
** I've tried direct correlation, works but sometimes gives errors on bat calls with little frequency sweep
 
** Planning to try correlation of only the amplitude data (derived with a Hilbert transform)
 
  
New project ideas:
+
=== Inexpensive ultrasonic player ===
* Use two old satellite dishes to allow speech to be transferred over some distance
+
see [[UltrasonicPlayer]]
** Figure out focal point
 
** Create some kind of dish mount
 
* Reverse engineer the digital oscilloscope at revspace
 
** Figure out screenshot image format
 
** Try to find if there are other commands than the "send screenshot" command
 
* <strike>More LedBanner audio visualisations</strike>
 
* Create a RFM69HW TNC, based on code by flok
 
** Remove 'flok' framing, make it comply with KISS protocol
 
** Use 'infinite' package length mode to send typical TCP/IP frames (1500 bytes)
 
* Create a 'HabAlert' android app, see [[HabAlertApp]]
 
* add opus audio codec support to squeezeboxserver and/or squeezelite
 
** an opus web radio stream already seems to be redirected to the client, but squeezelite crashes on it
 
* create code for remote control of my ZwaaiLicht
 
** implement wireless protocol for the NOMZ message ("\x4NOMZ") on address 0x66996699L (no ack)
 
** possibly implement a more capable protocol on a different pipe (with ack, learn about extra pipes on NRF24L01+)
 
** possibly split control of the light and the motor
 

Revision as of 17:49, 2 October 2016

User info Bertrik Sikken
Name Bertrik Sikken
Nick bertrik
Tagline heb ik niet

You can reach me at bertrik@sikken.nl or bertrik@gmail.com

Studied Electrical Engineering at Twente University.


Main interests:

  • reverse-engineering things (USB stuff, mp3 players), working on http://rockbox.org
  • studying bats and making electronics for recording/listening to bat sounds
  • radio stuff, in particular software-defined radio


Projects I work(ed) on (refresh):

 Project Status
FrontDoorDisplayAbandoned
HabAlertAppAbandoned
ISSOAbandoned
IbmPosDisplayAbandoned
Pico TrackersAbandoned
RadarOnAStickAbandoned
WifiLampAbandoned
A4PaperDispenserCompleted
BuildStatusTrafficLightCompleted
CJMCU-811Completed
CO2MeterHackingCompleted
CrawlSpaceSensorCompleted
DecodingLoraCompleted
DustSensorCompleted
ElectronicLoadCompleted
EspNowSkipCompleted
IntakefancontrollerCompleted
LichtKrantCompleted
LoRaGatewayCompleted
LoraBatBoxCompleted
LoraWanNodeCompleted
MHZ19Completed
MainsFrequencyCompleted
MiniSTM32F103ZECompleted
PowerLightCompleted
RC522HackingCompleted
RevRadioCompleted
STM32Completed
Secure iButtonCompleted
SoilHumiditySensorCompleted
StofAnanasCompleted
StofradarCompleted
TTNHABBridgeCompleted
VINDRIKTNINGCompleted
ZigbeeCoordinatorCompleted
Sensor-data-bridgeCompleted
AntiLostIn progress
AudioMothIn progress
CubeCellIn progress
EspAudioSensorIn progress
Esp32camIn progress
FMCWRadarIn progress
LoRa-E5-miniIn progress
LoraWanDustSensorIn progress
MainsFrequency2.0In progress
Msi2500SDRIn progress
Sim7020In progress
StereoBatRecorderIn progress
UltrasonicPlayerIn progress
EspNowAudioInitializing
... further results


Project ideas

This is a list of ideas I'm thinking about, but have not fully developed into an actual project yet.

investigate STM32F103 microcontroller

The STM32 family of microcontrollers looks quite interesting.

You can buy inexpensive STM32F103 boards with the following functionality:

  • Cortex M3 processor running at 72 MHz
  • 64 kB flash, 20 kB RAM
  • 2x ADC with 1 microsecond conversion time
  • USB interface

The plan is to get a bunch of these and play with them, for example see if it is fast enough to sample ultrasonic audio and store it on an sd card (so it can be used as a super cheap bat call recorder).

See this page for more information on using these in the Arduino environment.

investigate quadcopter remote control

It turns out that the typical little cheap Chinese quadcopters use a remote-control protocol that can be easily recreated using the famous NRF24L01+ chip (< $1 and easily connected to an arduino). This gives nice opportunity to either:

  1. transmit our own control signal, to control a quadcopter from something different than the manual remote control, e.g. automatic control
  2. receive the control signal, so the manual remote control that comes with a quadcopter can be used to steer other things (like a model car).

I haven't found a good overview of quadcopter remote control protocol specifications yet, there seem to be plenty examples of "here-is-the-code" however.

TTN gateway info panel

Problem: if you're running a gateway for the-things-network (TTN), you can see packets coming in by following the packet forwarder log file, but it gives very limited and rather cryptic information. For example, you don't see which node sent a message, so you have no idea how many unique nodes are sending data through your gateway.

This idea is about creating a simple info panel that you can run directly on the TTN gateway itself. The plan is to write this in Python. A typical gateway probably already runs some sort of Linux distribution which has the python binaries available or allows them to be installed easily. Using Python also means that you don't need a compiler/Makefile/etc.

Basic operation of this utility:

  • the gateway software is configured to send its data not just to TTN but also to the gateway info panel utility (running on "localhost"), using the poly packet forwarder
  • the utility listens on a specific UDP port, accepting data according to the Semtech v1 protocol.
  • it parses the plain JSON metadata (modulation parameters, like frequency, LoRa mode, SF, BW, etc.)
  • it also parses the payload bytes, part of the payload is not encrypted, so we can extract the message type, device address and sequence number (FCNT).
  • all incoming packets are shown in a table-like view in the console using the ncurses library.

Initially, the utility will just keep the packets in memory, so it just shows things that happened since you last started it. Later, we can decide to store the data, for example in a database.

The information shown can be just the incoming messages in order of arrival, one line per message. Alternatively it could show a kind of node-centric view, one line per device with info only on the latest message from that node.

mini word clock in dutch

Basically an monochrome 8x8 word clock, in Dutch, showing local time in the Netherlands.

This git repo has the current code.

See here for a demo running on an arduino nano.

The plan is to run this from an ESP8266 instead of an arduino nano, so it can get the time from the internet using NTP. The time offset will be fixed to Dutch local time, i.e. GMT+1 taking into account summer time. Summer time will be determined using the general rule "from 2:00 local time on the last sunday of March until 3:00 local time on the last sunday of October".

Inexpensive CO2 sensor

TODO: move this to its own page.

Status: works as a basic MQTT sensor, see topic "bertrik/co2" on test.mosquitto.org

See this github repo for code.

Use the MH-Z19 sensor module (about E22,-) to measure the CO2 concentration and an ESP8266 (like a WeMos D1 mini board) to push the measurement data over the internet to a MQTT server. Possibly I can use ESPEasy which makes configuration easy (through a web interface), I'd have to add support for this particular sensor -> ESPEasy seems pretty complicated to get changes accepted, has existing bugs that are not addressed, probably better to write my own custom code.

Understanding LoRa

Ultimate goal is to create an SDR algorithm to decode LoRa without the need for dedicated LoRa hardware. This could be useful when tracking HABs transmitting LoRa for example. See DecodingLora and EncodingLora.

In particular, I should definitely check out this gr-lora project. Perhaps make it work for decoding balloon telemetry modes.

Cypress PSOC5

Play with the Cypress PSOC5 platform, which combines a ARM Cortex-m3 processor with configurable analog blocks. I'm thinking of combining it with a 24 GHz doppler radar sensor, to process the signal and present it as a USB audio device (stereo signal contains I and Q parts). See RadarOnAStick.

Android HabAlert app

see HabAlertApp

Inexpensive ultrasonic player

see UltrasonicPlayer