發表文章

目前顯示的是 2018的文章

Orange DSM2/DSMx tx modules... how to make it work correctly?

圖片
I have been using turnigy controller for quite a long time.... The first module I used is a orange rx module: I'm not sure what is the version I have, but I guess it's v1, it communicate with controller through PPM, so it fit into my old JR 9X II as well. it does support 4 types of DSM. at binding, it will try to find out what is the dsm type of receiver, and set itself into that mode, and stay in that mode. and the LED will blink according to the mode: DSM2 1024: no LED DSM2 2048:1 blink DSMX 22ms: 2 blinks DSMX 11ms: 3 blinks If your last fly is with DSM2 2014 receiver(such as old orange 6 chs), and try to fly with receiver in another mode, you will see the light on receiver is on, but servo does move,(or some move, some does not, incorrect any way...) you can press the bind button 3 times(fast..) to switch operation mode of the module in sequence, you can see this through LED,and find the one works... Some times later, there is a internal module:

Beaglebone industrial

圖片
there are 2 versions of beaglebone industrial on the market these days(2018/4). 1. red version: element 14 2. Arrow one. it is industrial temp version of beaglebone black. but seems the page disappeared on 4/16/2018 3. beaglecore http://beaglecore.com/ shop  https://www.conrad.com/ce/en/product/1551255/BEAGLECORE-CPU-module-BCM1ETR?ref=searchDetail they do module with industrial temp, and promise support upto 2023. seems Germany made. and still open source.  https://github.com/BeagleCore/Hardware also comes with tape and reel. The best thing of beaglebone is that it has tones of uart for industrial usage. uart0 to uart 5. uart 0 is predefined as debugger port. uart 3 has pin conflict with HDMI(not a problem if u don't use HDMI), so the first used ones are: uart 1,2,4,5 as the latest debain for beaglebone, the hardware configuration is upto user. So, to enable these uarts: refer to  https://billwaa.wordpress.com/2014/10/13/beaglebone-black-enable-all-uart-ports-at-boo

How many LMIC for arduino are on the net??

I have been trying to work out the TTN in my region which is 923 AS2. spending some time to find out how to make a 1ch gateway, which take only 1ch and 1SF. Now it comes to the node side, most of examples use IBM LMIC and it's variation. IBM LMIC is based on ST MCU, so some porting to arduino IDE. They all have simillar name but with different modification.  and the function to call in arduino are the same, so be very careful to install.(I believe you better have only one on it.) 1. Matthijs Skooij https://github.com/matthijskooijman/arduino-lmic based on LMIC 1.5 providing raw example; used to send lora mac to other, for testing purpose. ttn-abp ttb-otaa No wiki page, but good explaination on readme.md 2. Thomas Telkamp https://github.com/tftelkamp He has 2 git on LMIC, 1. arduino-lmic-v1.5 noted deprecated, and refer reader to Matthijs one.US915/AU915 hybrid mode 2. LoRa-LMIC-1.51 folked from  Forked from  things4u/LoRa-LMIC-1.51  not sure what changes has bee

TTN single channel gateway with esp8266 for us frequency plan at 903.9Mhz

My region is fit for TTN 923 frequency plan, before making a 923 1ch gateway, it's good exercise to 1st make a 915 gateway. Hardware: RFM95, ESP8266 I did not find the hardware guide for V5, but there is one for V4 http://things4u.github.io/HardwareGuide/Single-Channel-Gway/ESP-gateway-v4.html short notice on hardware: The version is done with 2 kinds PCB(3 in V5, additional heltec board) which related to pin connection.There are' Comresult connections: For the bare board solutions the connections that need to be made are as follows: RFM95 pin ESP8266 pin 3.3V VCC 3.3V GND GND MISO D6 GPIO12/MISO MOSI D7 GPIO13/MOSI SCK D5 GPIO14/CLK (*) NSS D8 GPIO15/CS RESET *nc DIO0 D1, GPIO5 DIO1 D2, GPIO4 DIO2 D3, GPIO0 (**) * The reset pin does not have to be connected so it seems. It is only used at setup to read the chip identification ** This connection is not necessary for the current version of the gateway, but is more versatile for next versions or other use

Why we should not use the String object of arduino??

When using sd lib, I ran into problem of con char* and string problem in sd.println(), the compiler told me it's not right to write a string.... I have a function which assemble some strings and return back a string. let say String form-string(void); then I tried     myFile = SD.open("test.txt", FILE_WRITE);   // if the file opened okay, write to it:   if (myFile) {     Serial.print("Writing to test.txt...");    myFile.println(form_string());     // close the file:    myFile.close(); The error is that it says it need "const char *" not a "string"... I was so so confused.... I need to go deeper in the string and char array....google it.... turns out that lot of people talk about not to using arduino String objects, saying it's bad, and wast more time and space....well, today we can have powerful and big MCU then before with same cost, I don't really think this is a problem...Until I read this article.... The is the on