nanoCUL funktioniert nicht (richtig)

[Fillip]

Guten Abend, Gute Nacht, Guten morgen  zusammen,
da mein FHEM nun wieder läuft wie es soll, nach der neu Installation, wollte ich mich mal einen weiteren Schritt wagen. Dem eigenbau eines NanoCULs. Ich bin nach folgender Anleitung vor gegangen fürs Flashen:
https://techblog.one/funksteckdosen-mit-fhem-schalten/#Firmware_aufspielen
Habe aktuell einen 868 Sender, somit auch in der board.h angepasst (der 2. nano mit 433 Sender ist untwergs)
Beim Flashen hat alles Problemlos geklappt,

Code Auswählen Erweitern

sudo make program
#@if test ! -d /sys/class/gpio/gpio17; then echo 17 > /sys/class/gpio/export; fi
#@if test ! -d /sys/class/gpio/gpio18; then echo 18 > /sys/class/gpio/export; fi
#echo out > /sys/class/gpio/gpio17/direction
#echo out > /sys/class/gpio/gpio18/direction
#echo 0 > /sys/class/gpio/gpio17/value
#echo 0 > /sys/class/gpio/gpio18/value
#sleep 1
#echo 1 > /sys/class/gpio/gpio17/value
#sleep 1
#echo 1 > /sys/class/gpio/gpio18/value
avrdude -D -p atmega328p -P /dev/ttyUSB0 -b 57600 -c arduino    -U flash:w:nanoCUL.hex

avrdude: AVR device initialized and ready to accept instructions

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

avrdude: Device signature = 0x1e950f
avrdude: reading input file "nanoCUL.hex"
avrdude: input file nanoCUL.hex auto detected as Intel Hex
avrdude: writing flash (24700 bytes):

Writing | ################################################## | 100% 12.21s

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

Reading | ################################################## | 100% 10.51s

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

avrdude: safemode: Fuses OK (E:00, H:00, L:00)

avrdude done.  Thank you.

Möchte ich diesen in FHEM einbinden mittels

Code Auswählen Erweitern

define CUL868 CUL /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AH05MZMB-if00-port0@38400 1234
klappt dies auch, für eine kurze Zeit zeigt er mir Initialized an, nach einer kurzen Zeit steht aber nur noch opend da, und die Verbindung scheint nicht merh zu existieren. Der nano blinkt weiß auch recht schnell. Die blaue LED leuchtet dauerhaft...

Jemand eine Idee woran das ligen könnte? 

[RaspiLED]

Hi,
Da müsstest Du uns mal Deine FHEM Logs (am besten mit verbose 5 am CUL Device) und den Output von
dmesg | tail -100
zeigen.

Könnte entweder merkwürdiger Reboot des CULs sein wenn FHEM einen Befehl sendet oder Hardware...
Gruß Arnd


Raspi2 mit FHEM, CUL, Signalduino, MySensors, HomeBridge, Presence, Bravia, ...

[Fillip]

Sorry, den wollte ich gerstern noch anhängen, hab ich dann aber vergessen. Im Log steht folgendes

Code Auswählen Erweitern

2017.07.27 00:37:50 1: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AH05MZMB-if00-port0 disconnected, waiting to reappear (CUL868)
2017.07.27 00:37:50 3: Setting CUL868 serial parameters to 38400,8,N,1
2017.07.27 00:37:59 1: Cannot init /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AH05MZMB-if00-port0, ignoring it (CUL868)

Die Ausgabe von dmesg l tail -100 wirft folgendes raus

Code Auswählen Erweitern

pi@FHEM2:~ $ dmesg | tail -100
[    1.067186] hub 1-0:1.0: 1 port detected
[    1.076666] dwc_otg: FIQ enabled
[    1.076677] dwc_otg: NAK holdoff enabled
[    1.076685] dwc_otg: FIQ split-transaction FSM enabled
[    1.076708] Module dwc_common_port init
[    1.077328] usbcore: registered new interface driver usb-storage
[    1.086645] mousedev: PS/2 mouse device common for all mice
[    1.097047] bcm2835-wdt 20100000.watchdog: Broadcom BCM2835 watchdog timer
[    1.106091] bcm2835-cpufreq: min=700000 max=700000
[    1.115528] sdhci: Secure Digital Host Controller Interface driver
[    1.123972] sdhci: Copyright(c) Pierre Ossman
[    1.133116] sdhost-bcm2835 20202000.sdhost: could not get clk, deferring prob                                                                                        e
[    1.142089] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.151798] ledtrig-cpu: registered to indicate activity on CPUs
[    1.160552] hidraw: raw HID events driver (C) Jiri Kosina
[    1.169573] usbcore: registered new interface driver usbhid
[    1.178037] usbhid: USB HID core driver
[    1.188129] vchiq: vchiq_init_state: slot_zero = 0xdb580000, is_master = 0
[    1.200076] Initializing XFRM netlink socket
[    1.209837] NET: Registered protocol family 17
[    1.219324] Key type dns_resolver registered
[    1.230135] registered taskstats version 1
[    1.239336] vc-sm: Videocore shared memory driver
[    1.248168] [vc_sm_connected_init]: start
[    1.257942] [vc_sm_connected_init]: end - returning 0
[    1.274731] 20201000.serial: ttyAMA0 at MMIO 0x20201000 (irq = 81, base_baud                                                                                         = 0) is a PL011 rev2
[    2.117153] console [ttyAMA0] enabled
[    2.132273] sdhost: log_buf @ db513000 (5b513000)
[    2.167251] Indeed it is in host mode hprt0 = 00021501
[    2.243605] random: fast init done
[    2.269361] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    2.283967] of_cfs_init
[    2.316042] of_cfs_init: OK
[    2.329681] Waiting for root device PARTUUID=45611a0f-02...
[    2.379374] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.395656] Indeed it is in host mode hprt0 = 00001101
[    2.477002] mmc0: host does not support reading read-only switch, assuming wr                                                                                        ite-enable
[    2.496620] mmc0: new high speed SDHC card at address 59b4
[    2.512822] mmcblk0: mmc0:59b4       29.8 GiB
[    2.529044]  mmcblk0: p1 p2
[    2.623409] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. O                                                                                        pts: (null)
[    2.641713] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    2.657827] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.674449] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    2.692342] hub 1-1:1.0: USB hub found
[    2.706424] hub 1-1:1.0: 5 ports detected
[    2.728173] devtmpfs: mounted
[    2.741908] Freeing unused kernel memory: 400K (c0840000 - c08a4000)
[    2.757688] This architecture does not have kernel memory protection.
[    3.039391] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    3.180130] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    3.196326] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber                                                                                        =0
[    3.224830] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SEL                                                                                        INUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    3.248395] smsc95xx v1.0.5
[    3.262532] systemd[1]: Detected architecture 'arm'.
[    3.356992] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-20980000.usb-                                                                                        1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:c7:1d:4d
[    3.474028] NET: Registered protocol family 10
[    3.489031] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[    3.508559] systemd[1]: Inserted module 'ipv6'
[    3.527359] systemd[1]: Set hostname to <FHEM2>.
[    3.542784] systemd[1]: Initializing machine ID from random generator.
[    3.560914] systemd[1]: Installed transient /etc/machine-id file.
[    3.687265] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
[    3.704472] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber                                                                                        =3
[    3.722031] usb 1-1.2: Product: FT232R USB UART
[    3.736717] usb 1-1.2: Manufacturer: FTDI
[    3.750537] usb 1-1.2: SerialNumber: AH05MZMB
[    3.903188] uart-pl011 20201000.serial: no DMA platform data
[    4.591908] systemd[1]: Cannot add dependency job for unit regenerate_ssh_hos                                                                                        t_keys.service, ignoring: Unit regenerate_ssh_host_keys.service failed to load:                                                                                         No such file or directory.
[    4.620059] systemd[1]: Cannot add dependency job for unit display-manager.se                                                                                        rvice, ignoring: Unit display-manager.service failed to load: No such file or di                                                                                        rectory.
[    4.646836] systemd[1]: Found ordering cycle on basic.target/start
[    4.663599] systemd[1]: Found dependency on sysinit.target/start
[    6.954644] systemd-udevd[116]: starting version 215
[    8.469399] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x202                                                                                        00000
[    9.585075] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   12.255250] usbcore: registered new interface driver usbserial
[   12.258407] usbcore: registered new interface driver usbserial_generic
[   12.263046] usbserial: USB Serial support registered for generic
[   12.289753] usbcore: registered new interface driver ftdi_sio
[   12.293008] usbserial: USB Serial support registered for FTDI USB Serial Devi                                                                                        ce
[   12.296536] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[   12.297609] usb 1-1.2: Detected FT232RL
[   12.299022] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUS                                                                                        B0
[   14.393443] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   15.871363] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E                                                                                        1
[   19.911208] systemd-journald[115]: Received request to flush runtime journal                                                                                         from PID 1
[   21.248693] Adding 102396k swap on /var/swap.  Priority:-1 extents:4 across:2                                                                                        41660k SSFS
[   28.747302] random: crng init done
[ 1021.056255] usb 1-1.2: USB disconnect, device number 4
[ 1021.057095] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnect                                                                                        ed from ttyUSB0
[ 1021.057208] ftdi_sio 1-1.2:1.0: device disconnected
[ 1023.652603] usb 1-1.4: new full-speed USB device number 5 using dwc_otg
[ 1023.808813] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001
[ 1023.808837] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber                                                                                        =3
[ 1023.808848] usb 1-1.4: Product: FT232R USB UART
[ 1023.808858] usb 1-1.4: Manufacturer: FTDI
[ 1023.808867] usb 1-1.4: SerialNumber: AH05MZMB
[ 1023.830409] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
[ 1023.830715] usb 1-1.4: Detected FT232RL
[ 1023.832000] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUS                                                                                        B0


Habe den nanoCUL auch nochmals neu geflasht, keine änderung...

[Fillip]

Also ich habe gerade festgestellt, wenn ich das attr CUL868 rfmode HomeMatic setze, hängt sich der CUL auf bzw ist nicht merh erreichbar und die weiße LED blinkt schnell

Habe heute auch noch einen zweiten Nano bekommen, der soll dann für 433 senden sein. Habe den auch geflasht, die Datei angepasst für die 433 mhz und in FHEM eingebunden, dort steht, wie nun auch bei dem 868 CUL opend, ich muss aber sagen, bei dem 433 CUL ist noch kein Sender angeschlossen, wollte erst nur mal schauen ob der funktioniert, aber merkt der Nano bzw FHEM denn das noch mein sendemodul (CC1101) angeschlossen ist?

[Fillip]

Wollte nur kurz mitteilen, das das Problem am Pegelwanderer lag. Habe diesen nun erst einmal ausgelötet, nun läuft es mit der a-culfw Software 

[PeMue]

Wollte nur kurz mitteilen, das das Problem am Pegelwanderer lag. Habe diesen nun erst einmal ausgelötet, nun läuft es mit der a-culfw Software 

Welche Werte hast Du denn für die Pegelwandler eingebaut?

Gruß PeMue