I have an Arduino nano clone and I am not able to get an driver running on Windows. So I only worked directly on the raspberrypi.
-
[Solved] Auriol temperature sensor type IAN 91838 not detected
-
I have found a solution.
You need two terminals on your linux machine.
In the first you type thiscat /dev/ttyUSB0
change ttyUSB0 to your arduino when it is different.
This terminal shows you the answers from the arduino.With the second terminal we send the commands.
echo -e "COMMAND" > /dev/ttyUSB0
Command should first be PING.
Do you got a permissions failure? Then type this insudo chmod o+rw /dev/ttyUSB0
Now we can send the Receive command
echo -e "RF raw PIN" > /dev/ttyUSB0
remember PIN must be the number of your pin with the receiver (0 or 1).
Now it is possible, that your terminal is spammed with numbers.
Press the Button the Weather sensor twice.after this send this command
echo -e "RF receive PIN" > /dev/ttyUSB0
this stops the raw routine.
Now you have only to copy the text in the first terminal.
I think you can do some pipeping to an file with the first terminal but i am not a linux guy.pimatic rocks!!!
-
I have pushed some bugfixes and updates to homeduino.
Best is, when you updates your arduino too.https://github.com/Icesory/RFControl
https://github.com/Icesory/homeduinopimatic rocks!!!
-
I tried your solution with two terminals but I get no response on ‘cat’. Maybe the serial settings are incorrect. How can I check and modify them? ‘stty -F /dev/ttyUSB0 -a’ delivers:
speed 115200 baud; rows 0; columns 0; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^H; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 100; time = 2; -parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts -ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl ixon -ixoff -iuclc -ixany -imaxbel -iutf8 -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 -isig -icanon iexten -echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke
I am not so familiar with this.
-
Ah, I got it. I set
stty -F /dev/ttyUSB0 cr1 nl1
and then it works. ‘make monitor’ set NL and NR to 0. I don’t know how to change this.
Problem now is, that I can not press a button on the sensor. It sends its data automatically about every minute or two.
-
nice.
You can use this command to store the output in an file.cat /dev/ttyACM0 > raw_data.log
To stop this process you must only press STRG+C
pimatic rocks!!!
-
Yes of course. I can run this for 5 minutes or so, but you get a huge amount of raw data and I ask how to find out which part is from the sensor and if it this file contains data of the sensor anyway?
-
I think i find the necessary data. Let us trying this.
Normally these sensors sends the data when the battery is plugged in.
pimatic rocks!!!
-
How can I post the file in this forum?
-
Use pastebin.com
-
Yes paste bin or an oneclick hoster like uploaded or dropbox.
pimatic rocks!!!
-
Looks not good.
I havent found any data in the raw data.To find the necessary parts i have created a excel sheet.
https://www.dropbox.com/s/wh15jfgkynzj47o/weather7_heinzel_01.xlsx?dl=0pimatic rocks!!!
-
@Icesory : Can you give it another try. I found an interesting pattern in the raw data stream. Maybe this helps.
http://pastebin.com/gBNjf2qw
I saw this about every 30 seconds. And the sensor has a LED which also flashes about every 30 seconds.btw. The excel sheet I can not read. Can you produce a .xls file (Excel2003) and explain what I can do with it?
-
Another observation:
When I do this:echo -e "RF receive 0" > /dev/ttyUSB0
I get about every minute this
RF receive 392 4000 2048 9364 0 0 0 0 010202020201020101020202020202020101010202020202010102020201010103
-
Hey, what’s that?
I restarted pimatic and from time to time I get this in the log:weather7: { id: 133, channel: 0, temperature: 24, lowBattery: false } received: [ 388, 2052, 4004, 9388 ] 020101010102010202010101010101010202020201010101020102010201010203
-
First.
In the excel sheet i use functions of the 2007 version. So i cant safe it as a 2003 version.Second.
You can receive the data with homeduino. That is strange. Eventually you have some power supply failures.
The patterns you have found in the raw timings are the weather data.
I have no clue what we can do at the moment. Best is to watch this for a time period.pimatic rocks!!!
-
@Icesory : Good hint! I checked the voltage on the RF receiver. The power came from arduinio nano and has 4.85 V. When I take power directly from raspberrypi it is 5.2V and all works perfect. I think that 4.85 V is too less for the receiver to receive a maybe week signal. But I am wondering about that, because the distance is about 3 meters and only one wall is between sensor and receiver. Receiver has an antenna wire and can receive other signals from a switch remote from more than 10 meters without problems.
Receiver is same as this:
http://www.amazon.com/Wireless-Receiver-Module-Arduino-Control/dp/B00PQ32FR2/ref=sr_1_1?s=electronics&ie=UTF8&qid=1427355404&sr=1-1&keywords=433Mhz+Wireless+Receiver -
Since I take the +5V for the RF receiver from raspberrypi GPIO the USB serial interface where the Arduino is connected crashes from time to time with this error:
error [pimatic]: A uncaught exception occured: AssertionError: false == true at Board._handleRFControl (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:322:5) at Board._onLine (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:142:21) at SerialPortDriver.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:83:22) at SerialPortDriver.EventEmitter.emit (events.js:95:17) at SerialPort.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/driver/serialport.js:60:24) at SerialPort.EventEmitter.emit (events.js:95:17) at /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/parsers.js:25:17 at Array.forEach (native) at Object.parser (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/parsers.js:24:13) at Object.SerialPort.options.dataCallback (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/serialport.js:168:15) at SerialPortFactory.SerialPort._emitData (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/serialport.js:350:20) at afterRead (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/serialport.js:326:20) at /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/serialport.js:342:9 at Object.wrapper [as oncomplete] (fs.js:454:17) This is most probably a bug in pimatic or in a module, please report it!
-
It is a know bug.
https://github.com/pimatic/pimatic/issues/572How works your sensor generally?
pimatic rocks!!!