Raspberry und SD0

[netsrac]

Habe mal wieder bei Busware nachgefragt...leider immer noch keine Unterstützung der D0 Schnittstelle.

Hat sich da schonmal jemand rangemacht?! Will doppelte Arbeit vermeiden...

Gruß, Netsrac

[jakdaniel]

My SD0 don't tick any measurement

Hello to all,
I bought a few days ago the counter SD0. I followed the installation instructions on the site busware.de : SD0_Installation. Installing okay.

I have connected an electricity meter Electrex CD1 (http://www.electrex.it/download/cate...tallazione-cd1)

I see the pulse of the LED on the unit. I tested it with a tester and cd1 closes the circuit every 10 beats.

But using vzfeeder.pl do not see any "tick". Counters that you use? A voltage that send the pulse 27Vdc or something? How can I test if the card is broken or there are malfunctions in the counter? Batteries and manual contact?

In attachment the installation process.

Thanks to all

Bye

Eugenio
----- Deutsch Übersetzung google -----
Hallo an alle,
Ich kaufte mir vor ein paar Tagen den Zähler SD0. Ich folgte den Installationsanleitungen auf der Website busware.de : SD0_Installation. Installieren Ordnung.

Ich habe einen Stromzähler Electrex CD1 verbunden (http://www.electrex.it/download/cate...tallazione-cd1)

Ich sehe den Puls der LED am Gerät. Getestet habe ich es mit einem Tester und cd1 schließt den Stromkreis alle 10 Schläge.

Aber mit vzfeeder.pl sehe keinen "Tick". Zähler, die Sie verwenden? Eine Spannung, die den Puls 27 V DC oder etwas schicken? Wie kann ich testen, ob die Karte defekt ist oder gibt es Störungen in der Theke? Batterien und Bedienungsanleitung Kontakt?

In Anhang den Installationsvorgang.

Vielen Dank an alle

Bye

Eugenio
------------------

------Install Log -----
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.11.11 23:08:15 =~=~=~=~=~=~=~=~=~=~=~=
pi@raspberrypi ~ $ passwd
pi@raspberrypi ~ $ sudo su -
(resize disk with rasp-config and reboot)
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.11.11 23:09:46 =~=~=~=~=~=~=~=~=~=~=~=
pi@raspberrypi ~ $ sudo su -
root@raspberrypi:~# passwd
root@raspberrypi:~# aptitude update
root@raspberrypi:~# aptitude upgrade
root@raspberrypi:~# grep -i -n -C5 ttyAMA0 /etc/inittab
67-#
68-#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
69-
70-
71-#Spawn a getty on Raspberry Pi serial line
72:T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
root@raspberrypi:~# vi /etc/iniittab
root@raspberrypi:~# vi /etc/inittab grep -i -n -C6 ttyAMA0 /etc/inittab
67-#
68-#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
69-
70-
71-#Spawn a getty on Raspberry Pi serial line
72:######### FREE ttyAMA0 FOR SMART METER SD0 BUSWARE #######
73:#T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
root@raspberrypi:~# grep -i -n -C5 ttyAMA0 /etc/boot/cmdline.txt
1:dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
root@raspberrypi:~# cat /boot/cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
root@raspberrypi:~# reboot
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.11.11 23:38:00 =~=~=~=~=~=~=~=~=~=~=~=
root@raspberrypi:~# mkdir /opt/SD0-kernel-busware
root@raspberrypi:~# cd /opt/SD0-kernel-busware
root@raspberrypi:/opt/SD0-kernel-busware# wget http://files.busware.de/RPi/kernel+b...busware.tar.gz
root@raspberrypi:/opt/SD0-kernel-busware# mkdir kernel
root@raspberrypi:/opt/SD0-kernel-busware# cd kernel/
root@raspberrypi:/opt/SD0-kernel-busware/kernel# tar xvfz ../kernel+boot+modules-3.6.11-busware.tar.gz
root@raspberrypi:/opt/SD0-kernel-busware/kernel# cp -av /boot /var/backups/boot.original
root@raspberrypi:/opt/SD0-kernel-busware/kernel# cp -av /lib /var/backups/lib.original
root@raspberrypi:/opt/SD0-kernel-busware/kernel# cp -av boot/* /boot
root@raspberrypi:/opt/SD0-kernel-busware/kernel# reboot
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.11.11 23:45:51 =~=~=~=~=~=~=~=~=~=~=~=
root@raspberrypi:~# which hwclock hwclockh hwclock
root@raspberrypi:~# ls /dev/rtc0
root@raspberrypi:~# if test -e /dev/rtc0; then hwclock -w; fi
root@raspberrypi:~# mkdir /opt/SD0-firmware-busware
root@raspberrypi:~# cd /opt/SD0-firmware-busware
root@raspberrypi:/opt/SD0-firmware-busware# aptitude install subversion
root@raspberrypi:/opt/SD0-firmware-busware# svn checkout busware - Revision 88: /trunk/SD0 SD0
root@raspberrypi:/opt/SD0-firmware-busware# cd /opt/SD0-firmware-busware/SD0/Bootloader
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# more readme.txt
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# grep MCU makefile
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# grep BOOTSIZE makefile
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# grep F_CPU makefile main.c
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# grep START_ main.c
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# aptitude install gcc-avr avr-libc locate
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# updatedb
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# locate avr5.x
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# ln -s /usr/lib/ldscripts/avr5.x ldscripts_no_vector/
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# make
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Bootloader# cd ../Firmware_common/
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_common# make
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_common# cd ../Firmware_VZ/
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_VZ# make
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_VZ# aptitude install avrdude avrdude-doc
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_VZ# grep -make hexdump hexdump -C /sys/bus/i2c/devices/0-0050/eeprom

00000000 53 44 30 20 56 31 2e 31 20 53 54 41 4e 44 41 52 |SD0 V1.1 STANDAR|
00000010 44 20 32 30 31 33 2d 31 31 2d 31 31 0a ff ff ff |D 2013-11-11....|
00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00000100
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_VZ# make program


calling co-processor bootloader ...

if test ! -d /sys/class/gpio/gpio17; then echo 17 > /sys/class/gpio/export; fi
echo out > /sys/class/gpio/gpio17/direction
echo 0 > /sys/class/gpio/gpio17/value
if test ! -d /sys/class/gpio/gpio27; then echo 27 > /sys/class/gpio/export; fi
echo out > /sys/class/gpio/gpio27/direction
echo 0 > /sys/class/gpio/gpio27/value
echo 1 > /sys/class/gpio/gpio17/value
sleep 1
echo 1 > /sys/class/gpio/gpio27/value
avrdude -p atmega1284p -P /dev/ttyAMA0 -b 38400 -c avr109 -U flash:w:main.hex

Connecting to programmer: .
Found programmer: Id = "AVRBOOT"; type = S
Software Version = 0.8; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=128 bytes.

Programmer supports the following devices:
Device code: 0x46

avrdude: AVR device initialized and ready to accept instructions

Reading | | 0% 0.00s
Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9705
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "main.hex"
avrdude: input file main.hex auto detected as Intel Hex
avrdude: writing flash (4516 bytes):


Writing | ################################################## | 100% 1.43s

avrdude: 4516 bytes of flash written
avrdude: verifying flash memory against main.hex:
avrdude: load data flash data from input file main.hex:
avrdude: input file main.hex auto detected as Intel Hex
avrdude: input file main.hex contains 4516 bytes
avrdude: reading on-chip flash data:

eading | ################################################## | 100% 1.25s

avrdude: verifying ...
avrdude: 4516 bytes of flash verified

avrdude done. Thank you.

if test -e /sys/bus/i2c/devices/0-0050/eeprom; then echo SD0 V1.1 STANDARD `date +%F` > /sys/bus/i2c/devices/0-0050/eeprom; fi
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_VZ# make programhexdump -C /sys/bus/i2c/devices/0-0050/eepromdate +%Fhexdump -C /sys/bus/i2c/devices/0-0050/eeprom

00000000 53 44 30 20 56 31 2e 31 20 53 54 41 4e 44 41 52 |SD0 V1.1 STANDAR|
00000010 44 20 32 30 31 33 2d 31 31 2d 31 32 0a ff ff ff |D 2013-11-12....|
00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
00000100
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_VZ# aptitude install libpoe-perl libterm-readkey-perl libpoe-component-client-http-perl libpoe-component-dbiagent-perl libdevice-serialport-perl libdatetime-perl liblog-log4perl-perl
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_VZ# cd vzfeeder/
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_VZ/vzfeeder# ./vzfeeder.pl

[2013/11/12 00:11:30] INFO main - starting logger process
[2013/11/12 00:11:30] INFO main - opening database link
=== 9062 === 1 -> open_serial (from ./vzfeeder.pl at 75)
[2013/11/12 00:11:30] INFO main - opening serial port
=== 9062 === 1 -> queue_cmd (from /usr/share/perl5/POE/Kernel.pm at 1871)
=== 9062 === 1 -> POE::Wheel::ReadWrite(4) -> select write (from /usr/share/perl5/POE/Resource/FileHandles.pm at 240)
=== 9062 === 1 -> POE::Wheel::ReadWrite(4) -> select read (from /usr/share/perl5/POE/Resource/FileHandles.pm at 240)
=== 9062 === 1 -> got_serial (from /usr/share/perl5/POE/Wheel/ReadWrite.pm at 283)
[2013/11/12 00:11:32] INFO main - got_serial: V 1.0
=== 9062 === 1 -> cmd_V (from ./vzfeeder.pl at 169)
[2013/11/12 00:11:32] INFO main - VERSION: 1.0
^C
root@raspberrypi:/opt/SD0-firmware-busware/SD0/Firmware_VZ/vzfeeder#
------------------------------

[chrisi]

Kann es sein, dass es das SD0 von Busware nicht mehr zu kaufen gibt?
Gibt es da ein Nachfolgerprodukt?