Domotica UDOiT problemi

Informazioni riguardo il mondo della Linux: Raspberry Pi, Cubieboard, PCduino, MK802...
Rispondi
fpardberry
Messaggi: 1
Iscritto il: 30/11/2015, 19:50
Cod. abbonamento Elettronica In: 10015B
Occupazione: Operaio Inst mat elettronico
Home_Page: http://www.flaviopalermo.com
Commento: 1982 IPSIA diploma montatore e riparatore di apparecchiature radiofoniche televisive
1984 IPSIA diploma tecnico industrie elettriche ed elettroniche
1986 - 2005 artigiano :assistenza hitachi mitsubishi panasonic technics aiwa toshiba roadstart synudine computer assemblaggio
2006 ad oggi operio: elettricista bassa tensione 12V
Compleanno: 07 ago 1965
Città: Ventimiglia
Prov.: IM
Via: Vico Sant' Agostino 2

Domotica UDOiT problemi

Messaggio da fpardberry »

Salve, ho acquistato i prodotti UDOiT e non riesco a fare il "Learninig" per associare i vari moduli alla rete.
Apro la pagina web all' indirizzo 10.0.1.10 vado su settings inserisco user e pass . Su device trovo il Dongle USB già installato Type 00 Addr 00 Order 90 . Aggiungo un device Pir1 Type 01 Addr 01 Order 1 , clicco sull' icona "foglio matita" (Lear device) confermo cliccando su OK. Tengo premuto il pulsante config sul radar per 5 secondi, lascio, si accende il led rosso ( dietro il modulo rf ) . A questo punto sul browser (fire fox) dovrebbe apparire una finestra pop-up per confermare, cliccando su ok , l'associazione. ( elettronica in 198 pag 94)
La finestra pop-up non appare, ho installato anche firefox , come consigliato sulla rivista, ma non succede nulla. Ho eseguito la stessa operazione aggiungendo il device contatto magnetico......idem. Nella fase di acquisizione , quando il led rosso del radar /contatto magnetico rimane acceso, Il led sul dongle rimane sempre blu fisso!!! strano dovrebbe lampeggiare rosso.

Ho ricreato la sd card parecchie volte .....la cosa strana che ho notato e che se avvio raspberry senza il dongle usb , sulla pagina web dei device lo trovo sempre: Dongle usb Type 00 Addr 00 Order 90.
altra cosa strana è che è impossibile aggiornare rasbian

apt-get update
apt-get upgrade
apt-get dist-upgrade

non hanno alcun effetto.
Buone feste a tutti
Flavio
fla65ros66@gmail.com
Messaggi: 8
Iscritto il: 10/02/2015, 18:08
Cod. abbonamento Elettronica In: 10015B
Occupazione: Installatore app. elettroniche
Home_Page: http://

Re: Domotica UDOiT problemi

Messaggio da fla65ros66@gmail.com »

Salve, di seguito riporto output del terminale per capirci qualche cosa in più

login as: root
root@10.0.1.10's password:
Linux raspberrypi 4.1.7-v7+ #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Oct 24 16:55:37 2015 from 10.0.1.107
root@raspberrypi:~# lsusb

io penso che rb non vede il dongleusb

ecco la videata del comando

lsusb

Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 005: ID 04f3:0103 Elan Microelectronics Corp.
Bus 001 Device 006: ID 04f3:0230 Elan Microelectronics Corp. 3D Optical Mouse

non capisco quale sia il dongleusb forse il device 004?

ecco la videata del comando
root@raspberrypi:~# dmesg
[ 0.000000] Booting Linux on physical CPU 0xf00
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.1.7-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #817 SMP PREEMPT Sat Sep 19 15:32:00 BST 2015
[ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Raspberry Pi 2 Model B Rev 1.1
[ 0.000000] cma: Reserved 8 MiB at 0x3d800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 253952
[ 0.000000] free_area_init_node: node 0, pgdat 8085af80, node_mem_map bcf3a000
[ 0.000000] Normal zone: 2232 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 253952 pages, LIFO batch:31
[ 0.000000] [bcm2709_smp_init_cpus] enter (9420->f3003010)
[ 0.000000] [bcm2709_smp_init_cpus] ncores=4
[ 0.000000] PERCPU: Embedded 13 pages/cpu @bcef8000 s20608 r8192 d24448 u53248
[ 0.000000] pcpu-alloc: s20608 r8192 d24448 u53248 alloc=13*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 251720
[ 0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2709.boardrev=0xa01041 bcm2709.serial=0x80706d40 smsc95xx.macaddr=B8:27:EB:70:6D:40 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3ea00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 988232K/1015808K available (5958K kernel code, 534K rwdata, 1648K rodata, 416K init, 757K bss, 19384K reserved, 8192K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xbe800000 - 0xff000000 (1032 MB)
[ 0.000000] lowmem : 0x80000000 - 0xbe000000 ( 992 MB)
[ 0.000000] modules : 0x7f000000 - 0x80000000 ( 16 MB)
[ 0.000000] .text : 0x80008000 - 0x80775cd0 (7608 kB)
[ 0.000000] .init : 0x80776000 - 0x807de000 ( 416 kB)
[ 0.000000] .data : 0x807de000 - 0x80863af4 ( 535 kB)
[ 0.000000] .bss : 0x80866000 - 0x8092378c ( 758 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Additional per-CPU info printed with stalls.
[ 0.000000] NR_IRQS:608
[ 0.000000] Architected cp15 timer(s) running at 19.20MHz (virt).
[ 0.000000] clocksource arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[ 0.000010] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[ 0.000032] Switching to timer-based delay loop, resolution 52ns
[ 0.000318] Console: colour dummy device 80x30
[ 0.002076] console [tty1] enabled
[ 0.002138] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[ 0.002240] pid_max: default: 32768 minimum: 301
[ 0.002608] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.002676] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.003989] Initializing cgroup subsys blkio
[ 0.004076] Initializing cgroup subsys memory
[ 0.004145] Initializing cgroup subsys devices
[ 0.004206] Initializing cgroup subsys freezer
[ 0.004282] Initializing cgroup subsys net_cls
[ 0.004387] CPU: Testing write buffer coherency: ok
[ 0.004507] ftrace: allocating 20207 entries in 60 pages
[ 0.054123] CPU0: update cpu_capacity 1024
[ 0.054207] CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00
[ 0.054257] [bcm2709_smp_prepare_cpus] enter
[ 0.054420] Setting up static identity map for 0x8240 - 0x8274
[ 0.113979] [bcm2709_boot_secondary] cpu:1 started (0) 18
[ 0.114419] [bcm2709_secondary_init] enter cpu:1
[ 0.114469] CPU1: update cpu_capacity 1024
[ 0.114478] CPU1: thread -1, cpu 1, socket 15, mpidr 80000f01
[ 0.133966] [bcm2709_boot_secondary] cpu:2 started (0) 17
[ 0.134322] [bcm2709_secondary_init] enter cpu:2
[ 0.134354] CPU2: update cpu_capacity 1024
[ 0.134362] CPU2: thread -1, cpu 2, socket 15, mpidr 80000f02
[ 0.154006] [bcm2709_boot_secondary] cpu:3 started (0) 18
[ 0.154263] [bcm2709_secondary_init] enter cpu:3
[ 0.154289] CPU3: update cpu_capacity 1024
[ 0.154298] CPU3: thread -1, cpu 3, socket 15, mpidr 80000f03
[ 0.154393] Brought up 4 CPUs
[ 0.154527] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[ 0.154569] CPU: All CPU(s) started in SVC mode.
[ 0.155574] devtmpfs: initialized
[ 0.180375] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[ 0.180769] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.181936] pinctrl core: initialized pinctrl subsystem
[ 0.182779] NET: Registered protocol family 16
[ 0.188561] DMA: preallocated 4096 KiB pool for atomic coherent allocations
[ 0.189783] bcm2709.uart_clock = 3000000
[ 0.195116] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.195188] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.195414] Serial: AMBA PL011 UART driver
[ 0.195630] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 83, base_baud = 0) is a PL011 rev2
[ 0.695765] console [ttyAMA0] enabled
[ 0.700017] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[ 0.776541] bcm2708-dmaengine 3f007000.dma: DMA legacy API manager at f3007000, dmachans=0xf35
[ 0.785300] bcm2708-dmaengine 3f007000.dma: Initialized 7 DMA channels (+ 1 legacy)
[ 0.793708] bcm2708-dmaengine 3f007000.dma: Load BCM2835 DMA engine driver
[ 0.800635] bcm2708-dmaengine 3f007000.dma: dma_debug:0
[ 0.806616] SCSI subsystem initialized
[ 0.810653] usbcore: registered new interface driver usbfs
[ 0.816266] usbcore: registered new interface driver hub
[ 0.821755] usbcore: registered new device driver usb
[ 0.827532] raspberrypi-firmware soc:firmware: Attached to firmware from 2015-09-23 12:13
[ 0.863049] Switched to clocksource arch_sys_counter
[ 0.917125] FS-Cache: Loaded
[ 0.920397] CacheFiles: Loaded
[ 0.935232] NET: Registered protocol family 2
[ 0.940925] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.948194] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.954908] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.961403] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.967435] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.974192] NET: Registered protocol family 1
[ 0.979013] RPC: Registered named UNIX socket transport module.
[ 0.985038] RPC: Registered udp transport module.
[ 0.989768] RPC: Registered tcp transport module.
[ 0.994529] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.002206] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available
[ 1.011815] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 1.033929] VFS: Disk quotas dquot_6.6.0
[ 1.038273] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.047855] FS-Cache: Netfs 'nfs' registered for caching
[ 1.054402] NFS: Registering the id_resolver key type
[ 1.059564] Key type id_resolver registered
[ 1.063805] Key type id_legacy registered
[ 1.070666] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 1.078364] io scheduler noop registered
[ 1.082327] io scheduler deadline registered (default)
[ 1.087838] io scheduler cfq registered
[ 1.094332] BCM2708FB: allocated DMA memory fdc00000
[ 1.099361] BCM2708FB: allocated DMA channel 0 @ f3007000
[ 1.110861] Console: switching to colour frame buffer device 80x30
[ 1.123002] Serial: 8250/16550 driver, 0 ports, IRQ sharing disabled
[ 1.132615] vc-cma: Videocore CMA driver
[ 1.138481] vc-cma: vc_cma_base = 0x00000000
[ 1.145079] vc-cma: vc_cma_size = 0x00000000 (0 MiB)
[ 1.152322] vc-cma: vc_cma_initial = 0x00000000 (0 MiB)
[ 1.159797] vc-mem: phys_addr:0x00000000 mem_base=0x3ea00000 mem_size:0x3f000000(1008 MiB)
[ 1.187603] brd: module loaded
[ 1.201548] loop: module loaded
[ 1.207619] vchiq: vchiq_init_state: slot_zero = 0xbdc80000, is_master = 0
[ 1.218218] Loading iSCSI transport class v2.0-870.
[ 1.225951] usbcore: registered new interface driver smsc95xx
[ 1.233641] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 1.441540] Core Release: 2.80a
[ 1.446494] Setting default values for core params
[ 1.453126] Finished setting default values for core params
[ 1.660917] Using Buffer DMA mode
[ 1.666031] Periodic Transfer Interrupt Enhancement - disabled
[ 1.673661] Multiprocessor Interrupt Enhancement - disabled
[ 1.681016] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 1.687186] Dedicated Tx FIFOs mode
[ 1.692779] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xbdc14000 dma = 0xfdc14000 len=9024
[ 1.706451] FIQ FSM acceleration enabled for :
[ 1.706451] Non-periodic Split Transactions
[ 1.706451] Periodic Split Transactions
[ 1.706451] High-Speed Isochronous Endpoints
[ 1.730451] dwc_otg: Microframe scheduler enabled
[ 1.730531] WARN::hcd_init_fiq:412: FIQ on core 1 at 0x80401108
[ 1.738340] WARN::hcd_init_fiq:413: FIQ ASM at 0x80401464 length 36
[ 1.746519] WARN::hcd_init_fiq:438: MPHI regs_base at 0xbe89a000
[ 1.754429] dwc_otg 3f980000.usb: DWC OTG Controller
[ 1.761261] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 1.772341] dwc_otg 3f980000.usb: irq 32, io mem 0x00000000
[ 1.779901] Init: Port Power? op_state=1
[ 1.785720] Init: Power Port (0)
[ 1.791071] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.799792] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.810731] usb usb1: Product: DWC OTG Controller
[ 1.817352] usb usb1: Manufacturer: Linux 4.1.7-v7+ dwc_otg_hcd
[ 1.825195] usb usb1: SerialNumber: 3f980000.usb
[ 1.832582] hub 1-0:1.0: USB hub found
[ 1.838328] hub 1-0:1.0: 1 port detected
[ 1.844614] dwc_otg: FIQ enabled
[ 1.844627] dwc_otg: NAK holdoff enabled
[ 1.844638] dwc_otg: FIQ split-transaction FSM enabled
[ 1.844676] Module dwc_common_port init
[ 1.845086] usbcore: registered new interface driver usb-storage
[ 1.853295] mousedev: PS/2 mouse device common for all mice
[ 1.861598] bcm2835-cpufreq: min=600000 max=700000
[ 1.868601] sdhci: Secure Digital Host Controller Interface driver
[ 1.876629] sdhci: Copyright(c) Pierre Ossman
[ 1.883284] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[ 1.890995] mmc-bcm2835 3f300000.mmc: DMA channels allocated
[ 1.933405] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.943550] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.951689] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.959280] usbcore: registered new interface driver usbhid
[ 1.966788] usbhid: USB HID core driver
[ 1.972822] Initializing XFRM netlink socket
[ 1.978982] NET: Registered protocol family 17
[ 1.982300] mmc0: host does not support reading read-only switch, assuming write-enable
[ 1.986438] mmc0: new high speed SDHC card at address aaaa
[ 1.987057] mmcblk0: mmc0:aaaa SL08G 7.40 GiB
[ 1.998394] mmcblk0: p1 p2
[ 2.015572] Key type dns_resolver registered
[ 2.022132] Registering SWP/SWPB emulation handler
[ 2.029780] registered taskstats version 1
[ 2.036027] vc-sm: Videocore shared memory driver
[ 2.042576] [vc_sm_connected_init]: start
[ 2.048612] Indeed it is in host mode hprt0 = 00021501
[ 2.056000] vc_vchi_sm_init: failed to open VCHI service (-1)
[ 2.061685] [vc_sm_connected_init]: failed to initialize shared memory service
[ 2.074606] [vc_sm_connected_init]: end - returning -1
[ 2.097631] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 2.109749] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 2.128226] devtmpfs: mounted
[ 2.134033] Freeing unused kernel memory: 416K (80776000 - 807de000)
[ 2.233148] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 2.241960] Indeed it is in host mode hprt0 = 00001101
[ 2.443515] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[ 2.452461] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.463707] hub 1-1:1.0: USB hub found
[ 2.469743] hub 1-1:1.0: 5 ports detected
[ 2.753141] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 2.873589] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 2.882990] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.904244] smsc95xx v1.0.4
[ 2.967518] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:70:6d:40
[ 3.063153] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[ 3.200211] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6015
[ 3.211729] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.223751] usb 1-1.2: Product: FT230X Basic UART
[ 3.223767] usb 1-1.2: Manufacturer: FTDI
[ 3.223776] usb 1-1.2: SerialNumber: DN00JVC5
[ 3.246477] udevd[173]: starting version 175
[ 3.460410] usbcore: registered new interface driver usbserial
[ 3.470782] usbcore: registered new interface driver usbserial_generic
[ 3.479810] usbserial: USB Serial support registered for generic
[ 3.493193] usb 1-1.3: new low-speed USB device number 5 using dwc_otg
[ 3.499747] usbcore: registered new interface driver ftdi_sio
[ 3.499935] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 3.500315] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[ 3.500545] usb 1-1.2: Detected FT-X


[ 3.502134] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0

ECCO COME INDICATO SULLA RIVISTA /dev/ttyUSB0

[ 3.678480] usb 1-1.3: New USB device found, idVendor=04f3, idProduct=0103
[ 3.690998] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.703407] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 3.722392] input: HID 04f3:0103 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:04F3:0103.0001/input/input0
[ 3.773752] hid-generic 0003:04F3:0103.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 04f3:0103] on usb-3f980000.usb-1.3/input0
[ 3.807587] input: HID 04f3:0103 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:04F3:0103.0002/input/input1
[ 3.883593] hid-generic 0003:04F3:0103.0002: input,hidraw1: USB HID v1.10 Device [HID 04f3:0103] on usb-3f980000.usb-1.3/input1
[ 3.993231] usb 1-1.5: new low-speed USB device number 6 using dwc_otg
[ 4.110608] usb 1-1.5: New USB device found, idVendor=04f3, idProduct=0230
[ 4.124147] usb 1-1.5: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 4.136695] usb 1-1.5: Product: USB+PS/2 Optical Mouse
[ 4.151205] input: USB+PS/2 Optical Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:04F3:0230.0003/input/input2
[ 4.169551] hid-generic 0003:04F3:0230.0003: input,hidraw2: USB HID v1.11 Mouse [USB+PS/2 Optical Mouse] on usb-3f980000.usb-1.5/input0
[ 5.821720] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 5.870878] random: nonblocking pool is initialized
[ 6.046837] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 6.600346] i2c /dev entries driver
[ 8.957684] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 10.506731] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 12.070883] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 14.159741] Adding 102396k swap on /var/swap. Priority:-1 extents:4 across:114684k SSFS
[ 20.628745] uart-pl011 3f201000.uart: no DMA platform data
[ 167.920286] fuse init (API version 7.23)

ma allora perchè non riesco a fare il learnig (apprendimento) dei sensori????

altra curiosità ......ho scoperto lanciando

startx

ed avviando il browser che non si può accedere a internet???????!!!!!!!!, mentre da remoto riesco ad accedere alla pagina web di gestione!!!!

sarà per questo che non si riesce a fare gli aggiornamenti di raspbian....

ho anche scritto alla ditta che produce il materiale e che fornisce il file per creare la sd .......ma non mi hanno ancora risposto.

un saluto a tutti
flavio
fla65ros66@gmail.com
Messaggi: 8
Iscritto il: 10/02/2015, 18:08
Cod. abbonamento Elettronica In: 10015B
Occupazione: Installatore app. elettroniche
Home_Page: http://

[RISOLTO] Domotica UDOiT problemi

Messaggio da fla65ros66@gmail.com »

la ditta UDOiT ha risposto alla email che avevo fatto a suo tempo, allego risposta


Buongiorno,
la sequenza corretta per il learning (veda numero 198 pag. 94 della rivista FE) è:

Cliccare sull'icona a matita, e lasciare il messaggio di richiesta di learning aperto.
Tenere premuto il tasto config sul device fino a portarlo in learning.
POI cliccare sul tasto OK.

Il lampeggio del LED sul device indica che il learning è avvenuto, no messaggi a video.

Per quanto riguarda l'accesso a Internet, in caso di problemi la soluzione più probabile è quella indicata nel numero 201 di dicembre/gennaio pag.
128:

Inserire nel file /etc/resolv.conf

le seguenti righe

nameserver 8.8.8.8
nameserver 8.8.4.4

Quest'ultima soluzione però dipende dalla configurazione della rete.

Cordiali saluti

Roberto Chiarini
Rispondi