FHEM not reading CUL

[Guest]

Originally posted by: <email address deleted>

Hi All,
I have a problem with FHEM not updating information, or giving wrong
information. I have the CUL plugged into a USB socket on my Etrayz
Linux server which runs FHEM, which can access through the pgm2
webpage.

Everything was working Ok until recently, CUL was comunicating with
FHTs and updating pgm2 correctly and I could set temp on FHTs, however
nothing works now.

I dont know what changed to stop it working but since I have done the
following...

1, Removed FHEM.
2, Re-installed the OS so I have a fresh clean install.
3, Re-installed FHEM
4, Re-flashed CUL v3

After all this I have the same problems, which are...

1, FHEM reports the CUL dissapears.
2, The actual temp readings on the plots are infrequent.
3, The desired-temp readings are all wrong.
4, Cant set the temp on FHTs even tho the log says it has.

I have monitored the cul by typing "screen /dev/usb/ttyUSB0" on the
command line. I see messages recieved from the FHTs poping up
regularly so the CUL is alive and recieving correctly I guess.

I think there maybe a problem with timing because I deleted the CUL
module from pgm2 and re-defined a new one however it reported "Timeout
reading answer for get version" but I could see in the "screen" that
it had reported its version but FHEM did not see it.

I hope someone can help because it is so frustrating.

Thankyou
Alan

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[rudolfkoenig]

                                                   

> 1, FHEM reports the CUL dissapears.

Have you checked http://fhem.de/USB.html ?


> however it reported "Timeout reading answer for get version" but I could see
> in the "screen" that it had reported its version but FHEM did not see it.

Wait a moment: you have screen connected to the device, and fhem also running,
trying to read/write to the SAME device? This won't work...

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

Hi,
I read through the website you suggested and looked into the kernel
message log which I have posted below. I dont really know what to look
for, can you see anything wrong at all?

I did have the "screen" and FHEM running at the same time for a short
period but FHEM still wont read the CUL even when "screen" is not
active.

Thankyou
Alan

Feb 24 17:01:31 Etrayz kernel: usbcore: registered new interface
driver usbserial_generic
Feb 24 17:01:31 Etrayz kernel: drivers/usb/serial/usb-serial.c: USB
Serial Driver core
Feb 24 17:01:31 Etrayz kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for ch341-uart
Feb 24 17:01:31 Etrayz kernel: usbcore: registered new interface
driver ch341
Feb 24 17:01:31 Etrayz kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for pl2303
Feb 24 17:01:31 Etrayz kernel: usbcore: registered new interface
driver pl2303
Feb 24 17:01:31 Etrayz kernel: drivers/usb/serial/pl2303.c: Prolific
PL2303 USB to serial adaptor driver
Feb 24 17:01:31 Etrayz kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for FTDI USB Serial Device
Feb 24 17:01:31 Etrayz kernel: usbcore: registered new interface
driver ftdi_sio
Feb 24 17:01:31 Etrayz kernel: drivers/usb/serial/ftdi_sio.c:
v1.4.3:USB FTDI Serial Converters Driver
Feb 24 17:05:57 Etrayz kernel: usb 1-2.1: USB disconnect, address 3
Feb 24 17:05:57 Etrayz kernel: usbserial_generic 1-2.1:1.1: device
disconnected
Feb 24 17:17:40 Etrayz kernel: usb 1-2.1: new full speed USB device
using oxnas-ehci and address 4
Feb 24 17:17:40 Etrayz kernel: usb 1-2.1: configuration #1 chosen from
1 choice
Feb 24 17:17:40 Etrayz kernel: usbserial_generic 1-2.1:1.0: Generic
device with no bulk out, not allowed.
Feb 24 17:17:40 Etrayz kernel: usbserial_generic: probe of 1-2.1:1.0
failed with error -5
Feb 24 17:17:40 Etrayz kernel: usbserial_generic 1-2.1:1.1: generic
converter detected
Feb 24 17:17:40 Etrayz kernel: usb 1-2.1: generic converter now
attached to ttyUSB0
Feb 24 17:19:55 Etrayz kernel: usb 1-2.1: USB disconnect, address 4
Feb 24 17:19:55 Etrayz kernel: usbserial_generic 1-2.1:1.1: device
disconnected
Feb 24 17:19:57 Etrayz kernel: usb 1-2: USB disconnect, address 2
Feb 24 17:20:02 Etrayz kernel: usb 1-2: new full speed USB device
using oxnas-ehci and address 5
Feb 24 17:20:02 Etrayz kernel: usb 1-2: configuration #1 chosen from 1
choice
Feb 24 17:20:02 Etrayz kernel: usbserial_generic 1-2:1.0: Generic
device with no bulk out, not allowed.
Feb 24 17:20:02 Etrayz kernel: usbserial_generic: probe of 1-2:1.0
failed with error -5
Feb 24 17:20:02 Etrayz kernel: usbserial_generic 1-2:1.1: generic
converter detected
Feb 24 17:20:02 Etrayz kernel: usb 1-2: generic converter now attached
to ttyUSB0
Feb 24 17:20:05 Etrayz kernel: usb 1-2: USB disconnect, address 5
Feb 24 17:20:05 Etrayz kernel: usbserial_generic 1-2:1.1: device
disconnected
Feb 24 17:20:07 Etrayz kernel: usb 1-1: new full speed USB device
using oxnas-ehci and address 6
Feb 24 17:20:07 Etrayz kernel: usb 1-1: configuration #1 chosen from 1
choice
Feb 24 17:20:07 Etrayz kernel: usbserial_generic 1-1:1.0: Generic
device with no bulk out, not allowed.
Feb 24 17:20:07 Etrayz kernel: usbserial_generic: probe of 1-1:1.0
failed with error -5
Feb 24 17:20:07 Etrayz kernel: usbserial_generic 1-1:1.1: generic
converter detected
Feb 24 17:20:07 Etrayz kernel: usb 1-1: generic converter now attached
to ttyUSB0
Feb 24 17:22:13 Etrayz kernel: usbcore: registered new interface
driver usbfs
Feb 24 17:22:13 Etrayz kernel: usbcore: registered new interface
driver hub
Feb 24 17:22:13 Etrayz kernel: usbcore: registered new device driver
usb
Feb 24 17:22:17 Etrayz kernel: usb usb1: configuration #1 chosen from
1 choice
Feb 24 17:22:17 Etrayz kernel: usb 1-1: new full speed USB device
using oxnas-ehci and address 2
Feb 24 17:22:17 Etrayz kernel: usb 1-1: configuration #1 chosen from 1
choice
Feb 24 17:23:06 Etrayz kernel: usbcore: registered new interface
driver usbserial
Feb 24 17:23:06 Etrayz kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for generic
Feb 24 17:23:06 Etrayz kernel: usbserial_generic 1-1:1.0: Generic
device with no bulk out, not allowed.
Feb 24 17:23:06 Etrayz kernel: usbserial_generic: probe of 1-1:1.0
failed with error -5
Feb 24 17:23:06 Etrayz kernel: usbserial_generic 1-1:1.1: generic
converter detected
Feb 24 17:23:06 Etrayz kernel: usb 1-1: generic converter now attached
to ttyUSB0
Feb 24 17:23:06 Etrayz kernel: usbcore: registered new interface
driver usbserial_generic
Feb 24 17:23:06 Etrayz kernel: drivers/usb/serial/usb-serial.c: USB
Serial Driver core
Feb 24 17:23:07 Etrayz kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for ch341-uart
Feb 24 17:23:07 Etrayz kernel: usbcore: registered new interface
driver ch341
Feb 24 17:23:07 Etrayz kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for pl2303
Feb 24 17:23:07 Etrayz kernel: usbcore: registered new interface
driver pl2303
Feb 24 17:23:07 Etrayz kernel: drivers/usb/serial/pl2303.c: Prolific
PL2303 USB to serial adaptor driver
Feb 24 17:23:07 Etrayz kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for FTDI USB Serial Device
Feb 24 17:23:07 Etrayz kernel: usbcore: registered new interface
driver ftdi_sio
Feb 24 17:23:07 Etrayz kernel: drivers/usb/serial/ftdi_sio.c:
v1.4.3:USB FTDI Serial Converters Driver



On Feb 25, 4:50 pm, Rudolf Koenig wrote:
> > 1, FHEM reports the CUL dissapears.
>
> Have you checkedhttp://fhem.de/USB.html?
>
> > however it reported "Timeout reading answer for get version" but I could see
> > in the "screen" that it had reported its version but FHEM did not see it.
>
> Wait a moment: you have screen connected to the device, and fhem also running,
> trying to read/write to the SAME device? This won't work...

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

On 02/25/2011 08:15 PM, aam wrote:
> I dont really know what to look
> for, can you see anything wrong at all?

Yes:

> Feb 24 17:05:57 Etrayz kernel: usb 1-2.1: USB disconnect, address 3
> Feb 24 17:05:57 Etrayz kernel: usbserial_generic 1-2.1:1.1: device
> disconnected
> ...
> Feb 24 17:19:55 Etrayz kernel: usb 1-2.1: USB disconnect, address 4
> Feb 24 17:19:55 Etrayz kernel: usbserial_generic 1-2.1:1.1: device
> disconnected
> Feb 24 17:19:57 Etrayz kernel: usb 1-2: USB disconnect, address 2

Your USB system is not working stable. Use a better, shorter cable.
Don't use USB hubs, connect CUL directly to the server. If the problems
persist, disconnect other USB hardware, or remove devices that could
influence USB by electro magnetic pulses (i.e., WLAN, Motors, Power
supplies,...).

Regards,
Thomas

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

Hi Thomas,
The server has always lived behind the TV in the lounge with the CUL
on a short USB extention cable poking out above the TV. It has worked
like that for a while but maybe it was a matter of luck.

Following your suggestions I moved the server upstairs out of the way
of anything electrical then removed the cable and plugged the CUL
directly into the USB socket on the server.

Good news - its starting to wake up and comunicate with the FHTs
again.

Thankyou Thomas and Rudolf for you suggestions, looks like the problem
is solved.

Best regards
Alan


On Feb 25, 7:35 pm, Thomas Böhne wrote:
> On 02/25/2011 08:15 PM, aam wrote:
>
> > I dont really know what to look
> > for, can you see anything wrong at all?
>
> Yes:
>
> > Feb 24 17:05:57 Etrayz kernel: usb 1-2.1: USB disconnect, address 3
> > Feb 24 17:05:57 Etrayz kernel: usbserial_generic 1-2.1:1.1: device
> > disconnected
> > ...
> > Feb 24 17:19:55 Etrayz kernel: usb 1-2.1: USB disconnect, address 4
> > Feb 24 17:19:55 Etrayz kernel: usbserial_generic 1-2.1:1.1: device
> > disconnected
> > Feb 24 17:19:57 Etrayz kernel: usb 1-2: USB disconnect, address 2
>
> Your USB system is not working stable. Use a better, shorter cable.
> Don't use USB hubs, connect CUL directly to the server. If the problems
> persist, disconnect other USB hardware, or remove devices that could
> influence USB by electro magnetic pulses (i.e., WLAN, Motors, Power
> supplies,...).
>
> Regards,
> Thomas

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

Hi Alan,

On 02/26/2011 11:12 AM, aam wrote:
> The server has always lived behind the TV in the lounge with the CUL
> on a short USB extention cable poking out above the TV. It has worked
> like that for a while but maybe it was a matter of luck.
>
> Following your suggestions I moved the server upstairs out of the way
> of anything electrical then removed the cable and plugged the CUL
> directly into the USB socket on the server.

You didn't have to follow _all_ the hints I gave, maybe just removing
the USB cable would have done the job. But good to hear it's working now.


Regards
Thomas

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.