Up and coming changes
23 February, 2014 - 18:42
#102
Quick question
Quick question please Brett,
I assume that if I now do a:
INSTALL_DIR=/ make install After checking out the recent portable branch, I will update my PI system with all the changes made recently. Will this overwrite the previous binaries in /usr/bin? Or do I need to delete them first. also, what about my ini files, will these get overwritten. Not sure what the install command flags do and google is confusing me. Want to be safe than sorry! if I lose the heating for more than an hour I'm in the dog house! Cheers, Garry
|
23 February, 2014 - 21:10
#103
New PCB
23 February, 2014 - 21:11
#104
New PCB
Hi Derek,i feel like I'm a bit of a lurker as I'm finding very little time to put into this great project but full of ideas.I would be very tempted to go for a 5v supply for the pcb as this is becoming the standard now with most phones using USB chargers as well as the pis and similar. Could a step up circuit be used to generated the 12v required? Even a max232 can generate a few mA at 12v from 5v but there are plenty of simple step up circuits around. I could asked my colleagues for a few pointers?
23 February, 2014 - 22:38
#105
hostname
Brett
I've run the install again using the latest update. No installation issues this time.
My only issue is that the hostname is being ignored and defaulted to arm e.g. dbzoo.arm.serial rather than dbzoo.'hostname'.serial
Mark
23 February, 2014 - 23:53
#108
hostname
Brett
So it is ignoring hostname set in gui?
Ok I'll change that, thanks
Mark
24 February, 2014 - 12:16
#110
Wallwarts.. a very approriate
Wallwarts.. a very approriate name....
It's nice that there are increasing number of POE devices appearing, and I have bought POE switches when upgrading but it is still quite costly (component wise) to include the 802.3af electronics onboard. In the meantime I mostly use those small inline POE extractors to avoid wallwart congestion.
3 March, 2014 - 23:32
#111
filters
Brett
I'm having issues with xap filters not picking anything up with 591 (it started on an earlier release but can't remember which)
I can see the serial data in xfx viewer and have edited the filters to include capitalisation where it shows in xfx but still no data
Here is an example filter
f = xap.Filter()
f:add("xap-header","source","dbzoo.beaglebone.Serial")
f:add("Serial.Received","port",port)
f:callback(update)
the line to read the data
local data = frame:getValue("Serial.Received","data")
and the data it should pick up.
xap-header
{
v=12
hop=1
uid=FF00D500
class=Serial.Comms
source=dbzoo.beaglebone.Serial
}
Serial.Received
{
port=/dev/ttyUSB0
data=CC:Tx:4073:106:END
}
I have also included the lua script in full.
It works fine on the arm port you did that runs under Angstrom.
If there is any more info you need, just let me know.
No rush, it's on the BB dev board, not my HAH
Cheers
Mark
| Attachment | Size |
|---|---|
| CCApplet.lua.txt | 2.33 KB |
4 March, 2014 - 00:21
#113
I'll make sure I give it a go
I'll make sure I give it a go tonight.
Mark
4 March, 2014 - 19:32
#114
Plugboard log
Hi Brett,
I've noticed that the Plugboard log is not getting populated on my pi? I have checked the init.d/xap script and >/var/log/xap-plugboard.log 2>&1 is present.
Is this an issue on the pi only? Does the bone report log correctly?
thanks,
Garry
4 March, 2014 - 23:31
#115
penlight
Brett
That seems to have cured it.
Cheers
Mark
4 March, 2014 - 23:38
#116
xap-plugboard.log
Garry
Do you mean there is nothing in the log or no errors?
2>&1 means send stderr to file (apparently) so the log should only be populated on errors
5 March, 2014 - 00:04
#117
Hi mark,on the livebox you
Hi mark,
on the livebox you used to get a list of applets being loaded into the log. Also if you put print command into your scripts for debugging they would be printed to the file. I get nothing on my pi. Not tried to see if errors are logged but the stdout doesn't seem to be logged?
cheers
Garry
5 March, 2014 - 12:59
#119
Cheers Brett, that explains
Cheers Brett, that explains it!
can run standalone in future, no probs
Garry
9 March, 2014 - 14:06
#120
Raspberry pi upgrade woes
Hi folks,
errors I get trying upgrade on my Pi
$ cd /home/pi/portable
$ svn update
$ make arm-deb
$ cd /home/pi/portable/build/
$ sudo dpkg -i hah_0.1_armhf.deb
(Reading database ... 86526 files and directories currently installed.)
Preparing to replace hah 0.1 (using hah_0.1_armhf.deb) ...
Unpacking replacement hah ...
dpkg: error processing hah_0.1_armhf.deb (--install):
trying to overwrite '/usr/share/lua/5.1/pl/stringx.lua', which is also in package lua-penlight 1.0.2+htmldoc-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
update-rc.d: using dependency based boot sequencing
insserv: warning: script 'mathkernel' missing LSB tags and overrides
update-rc.d: using dependency based boot sequencing
insserv: warning: script 'mathkernel' missing LSB tags and overrides
Errors were encountered while processing:
hah_0.1_armhf.deb
So this upgrade fails . . when I look at the top of Kloned web page it still shows Build: 312/?Err? so its not 313 as reported in the /home/pi/portable/build/sysroot/etc/xap.d/build, ?Err? is just caus I've no hardware on the pi yet.
What am I doing wrong?
any help appreciated
john
14 March, 2014 - 15:25
#122
Need advice (and i have suggestion)
Been "off the grid" so to speak for a while the new changes look good, now the question's.
running a hah on a livebox.
is the upgrade straightforward (yes i will back up first) on livebox?
what exeactly is needed to transfer from livebox to Pi? to keep functionality.
Love Pi and have a spare.
on HAH i have pcb + jeenode + currentcost.
sorry for asking such basic questions
Also ref Pi is a SD download avalible so i can just burn an sd and get up and running fast (rather than going through a build process-and a lot of pain) i am a hardware guy not a software developer.
14 March, 2014 - 16:04
#123
welcome back
The Pi and BB versions are still at alpha stage but Garry has managed to attach his HAH pcb to the gpio.
I'm running on livebox and BB, gradually moving stuff over. Like you I have HAH pcb, basenode (with URFRX mod) and CC attached to the livebox. The CC is almost redundant now though as I have a node running on the BB that decodes CC. I also have another node on the BB that decodes the WH1080 weather station.
To sum up my current set up. The Livebox is used for CC, RF gasnode and roomnodes. The BB is used for CC, WH1080 and presence detection using arp to ping known wifi attached phones. Both BB and livebox publish to Xively and they both access each others xap messages using plugboard scripts. I'm using an app created in Corona for control/monitoring of the overall system.
There isn't a downloadable SD version yet and no install package either so you will have to download and build. It's not too hard once you try it a few times. I can only really comment on my BB experience though. Garry has played with the Pi.
14 March, 2014 - 16:25
#124
Hi Dean, welcome back,I've
Hi Dean, welcome back,
I've got the software running on my Pi it's straight forward enough if you follow the instructions on the portable wiki. I donno if it would help but I've attached a zip version of the .deb as compiled on my Pi which you might just be able to install as a package if you are using the raspbian wheezy distro.
Allan
| Attachment | Size |
|---|---|
| hah_0.1_armhf.zip | 984.51 KB |
14 March, 2014 - 18:26
#125
Hi dean
Hi dean, maybe give Allan's zip a go, otherwise I am planning on doing a virgin pi install for my brother soon (next week) so can take an image before I customise if you want?
As for PCB, it fits on the pi gpio easily, just a breakout board of fleabay and a change in serial port.
as for recent changes, only work involved should be modding your scripts slighty for the new way to initialise endpoints and require modules. The ini file is now split but the update should take care of that.
to be honest though, if I were in your position I would leave your livebox running as is and start to transition to the pi on the new version, that way you can play without upsetting your existing setup. just move the pcb over last when everything else working.
Garry
17 March, 2014 - 09:36
#126
think i have a spare :)
in fact sure i have a spare HAH board, just need to get a micro programmed up and get this break out board you speak of. :)
13 April, 2014 - 22:19
#127
Made the leap
I made the leap to 'almost' total control from the beaglebone. The only thing left to move over is the HAH pcb (RF) and iServer. I can only presume that if iServer works on the BBB then it will be faster than the livebox.
As an aside, it's been very quiet on here recently. I know it's not winter anymore and the heating season is behind us (and the days of needing your lights on almost 24HRS) but now is the time to play and prepare for next winter ;)
14 April, 2014 - 16:46
#128
Preparing for Next Winter
Once I have moved to the Pi I was hoping to look at Node Red as a way of visualizing the plugboard but Martyn got there first.
http://blog.aceshigh.net/2014/04/the-futures-bright-the-futures-red-node-red/
I was also thinking that the Spark.IO boards looked interesting for separating the hardware from the main processor but Brett got there first.
http://www.homeautomationhub.com/content/standalone-urf-tx-unit#comment-3596
20 April, 2014 - 18:03
#129
Brett we need a trap for corrupt data
Brett we need a trap for data collisions on the BB
I have traps set up for false data on the Current Cost and WH1080 code but it seems jeenode.lua fails if unexpected data arrives.
This caused plugboard to stop
lua: /usr/share/lua/5.1/xap/init.lua:436: /usr/share/lua/5.1/xap/jeenode.lua:51: invalid value (nil) at index 2 in table for 'concat'
xAP Message being processed.
xap-header
{
uid=FF00D500
source=dbzoo.beaglebone.Serial
hop=1
class=Serial.Comms
v=12
}
serial.received
{
data=OK 2 89 0CC:Tx: 193 0
port=/dev/ttyUSB2
}
21 April, 2014 - 19:47
#131
Serial collision
Brett
The error seems to be caused by 2 serial messages colliding. Again the question is why would this happen if the data is on different serial ports. So I don't think is has anything to do with the basenode mod or any problem in jeenode.lua.
It just shouldn't happen but it is.
I've just had another, this time it was the CCApplet that stopped not jeenode.lua
There error message shows data that should be on ttyUSB0 mixed with data from a roomnode that 'should' come in on ttyUSB2
serial.received
{
data=CC:Tx:39OK 685:226 164 0 1:END
port=/dev/ttyUSB0
}
Mark
23 April, 2014 - 21:27
#133
r595
Brett
r595 under test now. No issues so far.
Mark
EDIT: Still running fine after 26hrs. Good work Brett
25 April, 2014 - 18:57
#135
Still stable
Brett
Still running fine.
Mark
10 June, 2014 - 23:21
#136
Serial ports on the BBB
I thought I'd have a look at setting up a serial port on the GPIO pins for the HAH PCB. A bit of a minefield but making a little progress. I'll post back as soon as I have made a little more progress.
17 June, 2014 - 21:22
#137
oh dear
Be careful what you do if you edit the optargs line in uEnv.txt on the BBB. Especially if part of it disables the eMMC.
I did have a backup but that didn't work :(
All back up and running now but I'm now running from the SD card (much easier to work with)
2 July, 2014 - 19:34
#138
Connect To HAH AVR from BBB
Brett
I want to connect to UART4 on the BBB so I can use the connections on P9. I have got the port working and can ' see' the HAH AVR on the port but what file do I modify (if any) to allow control of my RF devices?
Cheers
Mark
2 July, 2014 - 20:13
#139
Hi Mark, i remember Brett
Hi Mark,
i remember Brett making changes to xap-live box to allow different serial port to be used. Is it not just a case of amending the following in /etc/xap.d/xap-livebox.ini?
| [livebox] |
| enable=0 |
| #port=/dev/ttyS0 |
The pi for example uses /dev/AMA0 on the gpio pins.
Garry.
EDIT: just remembered I also had to 'hack' the etc/init.d/xap script to send a '+++' command to the board on startup. E.g.
| start_livebox() { |
| INI="/etc/xap.d/xap-livebox.ini" |
if [ `iniget $INI livebox enable 0` -eq 1 ] ; then echo +++ >/dev/ttyAMA0 |
| /usr/bin/xap-livebox $MYDEV >/var/log/xap-livebox.log 2>&1 & |
| fi |
| } |
2 July, 2014 - 22:28
#140
Hi GarryI'm using the GPIO P9
Hi Garry
I'm using the GPIO P9 11 & 13 for TX and RX using UART4 so the port would be /dev/ttyO4
root@beaglebone:~# ll /dev/ttyO*
crw-rw---- 1 root tty 248, 0 Jul 1 20:41 /dev/ttyO0
crw-rw---- 1 root dialout 248, 4 Jul 1 20:41 /dev/ttyO4
ttyO0 is used for the terminal, I Suppose I could use that
I've set up the files as required and as soon as SWMBO has done some soldering for me tomorrow, I'll let you know how it\s gone.
I know we can edit the .c files and do a build, I had to for my Xively as I had more than 32
Cheers
Mark
3 July, 2014 - 22:11
#142
Livebox redundant
All moved to the BBB now
- « first
- ‹ previous
- 1
- 2
- 3
The thing that I really like about the Livebox platform is that, unlike the Pi, when you buy a Livebox you get a PSU and an enclosure for your PCB/LCD thrown in. At £10 from eBay, this is hard to beat from a cost perspective.
However, things move on and there are a LOT of Pi units out there.
I'm working on a new PCB. As Brett says, it is ethernet connected. The annoying thing about the 'separate units' approach is power - these ethernet units need a wallwart. One way that we were able to keep costs down on the original PCB was to use parts that had been gathered in my basement over many years. There is still an opportunity for some of this in the new PCB.
Main change is the addition of the ethernet module. Also a twin RJ45 socket for the 1-wire bus. An unregulated 15V DC input (same as Livebox) is stepped down to give 12V for the RF Tx module and 5V for the micro. LCD is serial driven to save on I/O pins & wiring. Much of the rest is as before.
Of course, it's hard to know if anybody would want to buy such a device.
Derek.