{"action":"created","issue":{"url":"https://api.github.com/repos/opendroplet/opendroplet-avr/issues/1","labels_url":"https://api.github.com/repos/opendroplet/opendroplet-avr/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/opendroplet/opendroplet-avr/issues/1/comments","events_url":"https://api.github.com/repos/opendroplet/opendroplet-avr/issues/1/events","html_url":"https://github.com/opendroplet/opendroplet-avr/issues/1","id":60489638,"number":1,"title":"Issues with Emoncms","user":{"login":"UCLteam","id":11406900,"avatar_url":"https://avatars.githubusercontent.com/u/11406900?v=3","gravatar_id":"","url":"https://api.github.com/users/UCLteam","html_url":"https://github.com/UCLteam","followers_url":"https://api.github.com/users/UCLteam/followers","following_url":"https://api.github.com/users/UCLteam/following{/other_user}","gists_url":"https://api.github.com/users/UCLteam/gists{/gist_id}","starred_url":"https://api.github.com/users/UCLteam/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/UCLteam/subscriptions","organizations_url":"https://api.github.com/users/UCLteam/orgs","repos_url":"https://api.github.com/users/UCLteam/repos","events_url":"https://api.github.com/users/UCLteam/events{/privacy}","received_events_url":"https://api.github.com/users/UCLteam/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-10T12:08:46Z","updated_at":"2015-03-10T14:15:32Z","closed_at":null,"body":"We have built the sensor as explained in https://droplet.hackpad.com/Hardware-Primer-ZlAUIxXoOr8. You can find attached photographs of what we did:\r\n![img_0630](https://cloud.githubusercontent.com/assets/11406900/6574978/38ab0b78-c722-11e4-9c3c-d71879922975.JPG)\r\n![img_0631](https://cloud.githubusercontent.com/assets/11406900/6574983/43e5b6fa-c722-11e4-9e8d-7c7a901ed813.JPG)\r\n![img_0632](https://cloud.githubusercontent.com/assets/11406900/6574984/479b0656-c722-11e4-9cf0-c2584f0ab6b0.JPG)\r\nHowever we have a  few doubts:\r\n  - the thickness of the antenna connected to the sensor (it was not precised in the protocol) \r\n  - the connection between VCC of the microphone to the Moteino: we chose finally 3V3. Is there some new code to add to the OpenDropletOEM file?\r\n\r\nWe have loaded the OpenDropletOEM file to the sensor, without doing any changes.\r\n\r\nWe have connected the rfm12pi to the rpibasestation b+ but we are not sure which pins we should use exactly. You can find attach the photograph of what we did:\r\n![img_0629](https://cloud.githubusercontent.com/assets/11406900/6574968/1e54afae-c722-11e4-95b7-08317b78d8f8.JPG)\r\n\r\nWe have loaded the ready-to-go SD card image to the SD card as explained in steps 1 and 2 of https://github.com/emoncms/emoncms/blob/bufferedwrite/docs/setup.md\r\n\r\nWe have configured the basestation to store locally the data as explained in step 3a) of https://github.com/emoncms/emoncms/blob/bufferedwrite/docs/setup.md. \r\nHere is our emonhub.conf file:\r\n![1](https://cloud.githubusercontent.com/assets/11406900/6575668/c5433f14-c728-11e4-96c8-1c4d1dcc425a.jpg)\r\n![2](https://cloud.githubusercontent.com/assets/11406900/6575678/d3603836-c728-11e4-9085-56c7a3b767f8.jpg)\r\n\r\nHowever, we are not sure of the group and the baseid of the RFM12pi module: we left the initial values: group=210, baseid=15. The frequence is 433MHz.\r\n\r\nNow, \"inputs should start appearing in the inputs section of your emoncms account\". It worked once: ![screenshot of inputs](https://cloud.githubusercontent.com/assets/11406900/6574684/0b50650e-c71f-11e4-9c98-5ca0c9b24b57.png). Is this what we are expecting? \r\nThere were 3 inputs appearing : Node 1 - key 1, Node 1 - key 2, Node 1 -key 3. \r\nHowever, these inputs just disappear and we can no longer see them. Shure proposed to:\r\n-\"checked that the rpi filesystem is read AND write enable after reboot\": however in https://github.com/emoncms/emoncms/blob/bufferedwrite/docs/setup.md they say to \"Set the raspberrypi os back into read-only mode\" at the end of the protocol, before checking the inputs\r\n-\"checked serial output from sensor\": what does this mean exactly?\r\n-\"rfm hub service on rpi running\": yes, this is the case.\r\n\r\nWhen we connect the power of the basestation, connected to a screen, there are three strange texts: \r\n![basestation shrinked](https://cloud.githubusercontent.com/assets/11406900/6575103/6efb0286-c723-11e4-95b3-5b3f41aa15fb.jpg)\r\nThe log is said to be off but in the file: boot/emonhub.conf, loglevel = WARNING\r\n\r\nWhen we write the \"sudo iostat 60\" command, kb_wrtn/s is not as it should be (around 0.5-1.5 kb_wrtn/s):\r\n![sans titre](https://cloud.githubusercontent.com/assets/11406900/6575322/aff9c3a6-c725-11e4-8063-1a276611c148.jpg)\r\n\r\n\r\nSome mistakes can come from any of the previous steps. However, as we saw the inputs once, can't we assume that no mistakes were made? Except if it is possible that the inputs seen are coming from another RFM12 device?\r\n\r\n\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/opendroplet/opendroplet-avr/issues/comments/78061298","html_url":"https://github.com/opendroplet/opendroplet-avr/issues/1#issuecomment-78061298","issue_url":"https://api.github.com/repos/opendroplet/opendroplet-avr/issues/1","id":78061298,"user":{"login":"aShure","id":4117408,"avatar_url":"https://avatars.githubusercontent.com/u/4117408?v=3","gravatar_id":"","url":"https://api.github.com/users/aShure","html_url":"https://github.com/aShure","followers_url":"https://api.github.com/users/aShure/followers","following_url":"https://api.github.com/users/aShure/following{/other_user}","gists_url":"https://api.github.com/users/aShure/gists{/gist_id}","starred_url":"https://api.github.com/users/aShure/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aShure/subscriptions","organizations_url":"https://api.github.com/users/aShure/orgs","repos_url":"https://api.github.com/users/aShure/repos","events_url":"https://api.github.com/users/aShure/events{/privacy}","received_events_url":"https://api.github.com/users/aShure/received_events","type":"User","site_admin":false},"created_at":"2015-03-10T14:15:32Z","updated_at":"2015-03-10T14:15:32Z","body":"I will try to address your questions:\r\n\r\n> However, as we saw the inputs once, can't we assume that no mistakes were made? Except if it is possible that the inputs seen are coming from another RFM12 device?\r\nThe data you saw seems to be your node, the array of three data points absolutely correlates with the data you send from the node.\r\n\r\n> When we write the \"sudo iostat 60\" command, kb_wrtn/s is not as it should be (around 0.5-1.5 kb_wrtn/s)\r\n\r\nI can't follow your problem there, the system seems to work well - it would be broken if it would show anything above 0, because you put it into read only mode immediately before. Why should the write stat be around 0.5-1.5 kb/s, when nothing is allowed to write to the sd card? \r\n\r\nI would not put the system into a read only state as you want to tweak files and log data. The error messages at bootup seem to be normal due to the read only state. It does not start in read and write state to reduce wear on the filesystem due to the nature of SD cards, they have a limited amount of writing operations, but a near unlimited amount of read operations before they will fail.\r\n\r\nThe error which says\r\n\r\n> Starting redis server: failed.\r\n\r\ncould be a problem, as redis seems essential to buffer the incoming data. However, the error could be coming up because the service is already up and running, thus can't be started a second time. If you are not familiar with the linux shell and the evaluation of running processes, I guess the following commands are an easy approach to see if the redis service has been running:\r\n```\r\nsudo service redis-server start\r\nsudo service redis-server stop\r\nsudo service redis-server restart\r\n```\r\n\r\nThe antenna length should be 165 mm for the rfm12b frequency of 433 Mhz. The wire width is unimportant.\r\n\r\nThe batteries you are using don't look healthy at all. I assume they are rechargeable batteries and have been damaged with overcharging and thus overheating. If any of the batteries touch their adjacent battery due to the broken insulation they will form a short circuit.  \r\n\r\nI suggest you connect the Moteino to your computer and look at the serial output, for example with the Arduino IDE. "}}