Page 1 of 1
Update 4.9d
Posted: Fri Jan 27, 2012 4:58 pm
by admin
Hot fix for the bug introduced with 4.9c which resulted in dropping TH sensors on "sensors" page when using certain weather station types.
4.9d can be installed the usual way.
Re: Update 4.9d
Posted: Mon Feb 06, 2012 12:38 pm
by Aussie101
Just had sensors saying no data for 4h
This is a new install based on the 4.9 image updated to 4.9d after install
Sensors page says
Code: Select all
error receive data from socket 127.0.0.1:5555: Resource temporarily unavailable
Warning: Data logging has been halted
I'm updating to 4.9e now.
Re: Update 4.9d
Posted: Mon Feb 06, 2012 1:19 pm
by admin
what type of weather station do you use?
Re: Update 4.9d
Posted: Mon Feb 06, 2012 1:22 pm
by Aussie101
admin wrote:what type of weather station do you use?
I have a WMR968 and I'm testing a Vantage Vue with serial USB FTDI adapter
Seems that the Vantage usbserial is no longer coming up since the update. Are there any kernel changes?
Re: Update 4.9d
Posted: Mon Feb 06, 2012 1:33 pm
by Aussie101
See
viewtopic.php?f=18&t=6933#p11520
Came up as ttyUSB0 on connection under 4.9d but errors with
Code: Select all
Feb 6 22:00:05 meteohub kernel: usb 2-2: new full speed USB device using ohci_hcd and address 34
Feb 6 22:00:05 meteohub kernel: usb 2-2: device descriptor read/64, error -62
Feb 6 22:00:05 meteohub kernel: usb 2-2: device descriptor read/64, error -62
Feb 6 22:00:05 meteohub kernel: usb 2-2: device descriptor read/64, error -62
Feb 6 22:00:05 meteohub kernel: usb 2-2: new full speed USB device using ohci_hcd and address 35
Feb 6 22:00:05 meteohub kernel: usb 2-2: device descriptor read/64, error -62
Feb 6 22:00:06 meteohub kernel: usb 2-2: device descriptor read/64, error -62
Feb 6 22:00:06 meteohub kernel: usb 2-2: new full speed USB device using ohci_hcd and address 36
Feb 6 22:00:06 meteohub kernel: usb 2-2: device not accepting address 36, error -62
Feb 6 22:00:06 meteohub last message repeated 3 times
Feb 6 22:00:06 meteohub kernel: usb 2-2: device not accepting address 36, error -62
Feb 6 22:00:06 meteohub kernel: usb 2-2: new full speed USB device using ohci_hcd and address 37
Feb 6 22:00:07 meteohub kernel: usb 2-2: device not accepting address 37, error -62
Feb 6 22:00:07 meteohub kernel: usb 2-2: device not accepting address 37, error -62
Since update to 4.9e (this may not be the fault of 4.8e, I have only connected the Vantage today)
Serial USB adapter is FTDI Sparkfun FTDI Basic breakout 3.3v DEV-098373
Re: Update 4.9d
Posted: Mon Feb 06, 2012 1:43 pm
by admin
Hi,
can you please send me the USB section of the "dmesg" log on "Log Files" page.
What Meteohub HW are you using? or output of "lsusb" when working on the linux shell.
one more thought... the vantage serial logger does deliver full +/- 12v signals,
or are you working with a home brew data logger directly connecting to the consoles
20 pin header as discussed on "wxforum.net"?
Re: Update 4.9d
Posted: Mon Feb 06, 2012 2:02 pm
by Aussie101
admin wrote:Hi,
can you please send me the USB section of the "dmesg" log on "Log Files" page.
What Meteohub HW are you using? or output of "lsusb" when working on the linux shell.
one more thought... the vantage serial logger does deliver full +/- 12v signals,
or are you working with a home brew data logger directly connecting to the consoles
20 pin header as discussed on "wxforum.net"?
Homebrew, as above. Sparkfun FTDI adapter as described on wxforum.
Hardware is Alix.3d
USB Serial worked on initial plugin under 4.9d:
Code: Select all
Feb 5 19:49:47 meteohub kernel: usb 2-2: new full speed USB device using ohci_hcd and address 2
Feb 5 19:49:47 meteohub kernel: usb 2-2: configuration #1 chosen from 1 choice
Feb 5 19:49:47 meteohub kernel: ftdi_sio 2-2:1.0: FTDI USB Serial Device converter detected
Feb 5 19:49:47 meteohub kernel: drivers/usb/serial/ftdi_sio.c: Detected FT232RL
Feb 5 19:49:47 meteohub kernel: usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0
dmesg today after 4.9e:
Code: Select all
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[..]
ehci_hcd 0000:00:0f.5: EHCI Host Controller
ehci_hcd 0000:00:0f.5: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:0f.5: irq 10, io mem 0xefffd000
SCSI subsystem initialized
ehci_hcd 0000:00:0f.5: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
[..]
ohci_hcd 0000:00:0f.4: OHCI Host Controller
ohci_hcd 0000:00:0f.4: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:0f.4: irq 10, io mem 0xefffe000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
usb 2-2: new full speed USB device using ohci_hcd and address 2
usb 2-2: device descriptor read/64, error -62
usb 2-2: device descriptor read/64, error -62
[..]
usb 2-2: new full speed USB device using ohci_hcd and address 3
usb 2-2: device descriptor read/64, error -62
usb 2-2: device descriptor read/64, error -62
usb 2-2: new full speed USB device using ohci_hcd and address 4
usb 2-2: device not accepting address 4, error -62
usb 2-2: new full speed USB device using ohci_hcd and address 5
usb 2-2: device not accepting address 5, error -62
lsusb:
Code: Select all
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
lsusb -v
Code: Select all
Bus 001 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.24-etchnhalf.1-486 ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 0000:00:0f.5
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 4
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Port 3: 0000.0100 power
Port 4: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
Bus 002 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed hub
bMaxPacketSize0 64
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.24-etchnhalf.1-486 ohci_hcd
iProduct 2 OHCI Host Controller
iSerial 1 0000:00:0f.4
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 4
wHubCharacteristic 0x0002
No power switching (usb 1.0)
Ganged overcurrent protection
bPwrOn2PwrGood 3 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0101 power connect
Port 3: 0000.0100 power
Port 4: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
Doesn't look good

Re: Update 4.9d
Posted: Mon Feb 06, 2012 2:55 pm
by admin
There have not been any changes to the usb serial drivers between the versions.
So my guess is, that the adapter has somehow stopped operation or is not
properbly connected on the USB side or does not get power.
As long as no product/verndor IDs are shown via lsusb, Meteohub has no chance to setup a usb serial channel.
Re: Update 4.9d
Posted: Mon Feb 06, 2012 2:57 pm
by Aussie101
Ok, thanks Admin, I see that.
Will investigate the other side.
Cheers.