Originally posted by: <email address deleted>
Hi!
Does FHEM support device cm15pro?
--
bessarabov
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-
Am Samstag, 18. April 2009 schrieb bessarabov:
> Hi!
>
> Does FHEM support device cm15pro?
I am currently checking with someone to what extend (none, partially, fully)
it does. Do you have such a device? If so, just try to use it as if it wee a
CM11.
Boris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-
Originally posted by: <email address deleted>
Yes, today I've got such a device and now I'm trying to use it with FHEM.
Still no succes.
The problem is that I don't have /dev/ttyUSB* aftre plugging this
device to my linux box.
dmesg shows that it is connected:
{{{
usb 4-2: new low speed USB device using uhci_hcd and address 9
usb 4-2: configuration #1 chosen from 1 choice
}}}
and I can see it with lsusb:
{{{
Bus 004 Device 009: ID 0bc7:0001 X10 Wireless Technology, Inc.
ActiveHome (ACPI-compliant)
}}}
After plugging this device I'm expecting that some /dev/ttyUSB* will
be created. But it does not appear.
2009/4/18 Boris Neubert :
>
> Am Samstag, 18. April 2009 schrieb bessarabov:
>> Hi!
>>
>> Does FHEM support device cm15pro?
>
> I am currently checking with someone to what extend (none, partially, fully)
> it does. Do you have such a device? If so, just try to use it as if it wee a
> CM11.
>
> Boris
>
>
> >
>
--
bessarabov.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-
Hi Иван,
Иван Бессарабов wrote:
> The problem is that I don't have /dev/ttyUSB* aftre plugging this
> device to my linux box.
Linux instantiates a generic device file for every USB file, e.g.
/sys/bus/usb/devices/1-0:1.0
If the device is recognized as a serial tty, a symlink to /dev/ttyUSB*
is generated by a secondary process (usually defined in
/etc/udev/rules.d). For the CM15 this is obviously not the case as it is
not recognized. Try to put a new rule file in /etc/udev/rules.d with
the following content:
SYSFS{idVendor}=="0bc7", SYSFS{idProduct}=="0001", SYMLINK+="cm15"
After hotplugging the device, a device file /dev/cm15 should appear.
Try whether you can access it via fhem (as CM11 device).
Good luck,
Boris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-
Originally posted by: <email address deleted>
Thank you very much!
Yes, the device apperd in /dev, but it is still not working =(
Here is the details.
I've created file /etc/udev/rules.d/82-cm15pro.rules and after restarting
udev (sudo /etc/init.d/udev restart) and pluggin cm15pro in usb i've got
/dev/cm15
When I start fhem, I can see in log:
{{{
2009.04.22 12:08:42 3: CM11 opening CM11 device /dev/cm15
can't getattr: Inappropriate ioctl for device at
/home/bessarabov/tmp/FHEM/fhem-4.5//FHEM/00_CM11.pm line 177
2009.04.22 12:08:42 3: Can't open /dev/cm15: Inappropriate ioctl for device
2009.04.22 12:08:42 3: No I/O device found for lamp1
2009.04.22 12:08:42 3: No I/O device found for lamp2
2009.04.22 12:08:42 0: Server started (version 4.5 from 2008-12-23 ($Id:
fhem.pl,v 1.59 2008/12/09 14:12:40 rudolfkoenig Exp $), pid 603)
}}}
The commands like "set lamp1 off" are not working (but there is no error in
log file)
I've created the simple perl file:
{{{
#! /usr/bin/perl
use Device::SerialPort;
my $dev = "/dev/cm15";
$po = new Device::SerialPort ($dev);
print "Can't open $dev: $!\n" if(!$po);
}}}
When I execute it, i've got the error:
{{{
can't getattr: Inappropriate ioctl for device at ./test.pl line 5
Can't open /dev/cm15: Inappropriate ioctl for device
}}}
Maybe you can recoomend something is this case?
2009/4/21 Dr. Boris Neubert
>
> Hi Иван,
>
> Иван Бессарабов wrote:
> > The problem is that I don't have /dev/ttyUSB* aftre plugging this
> > device to my linux box.
>
> Linux instantiates a generic device file for every USB file, e.g.
>
> /sys/bus/usb/devices/1-0:1.0
>
> If the device is recognized as a serial tty, a symlink to /dev/ttyUSB*
> is generated by a secondary process (usually defined in
> /etc/udev/rules.d). For the CM15 this is obviously not the case as it is
> not recognized. Try to put a new rule file in /etc/udev/rules.d with
> the following content:
>
> SYSFS{idVendor}=="0bc7", SYSFS{idProduct}=="0001", SYMLINK+="cm15"
>
> After hotplugging the device, a device file /dev/cm15 should appear.
>
> Try whether you can access it via fhem (as CM11 device).
>
> Good luck,
> Boris
>
> >
>
--
bessarabov.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Иван Бессарабов wrote:
> Yes, the device apperd in /dev, but it is still not working =(
Sorry, I am lost. Maybe one of the experts on serial port settings on
that mailing list can comment on this. If not, someone has to go the
hard way and re-engineer the existing device driver on linuxha.com.
Boris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHEM users on Linux" group.
To post to this group, send email to fhem-users@googlegroups.com
To unsubscribe from this group, send email to fhem-users+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/fhem-users?hl=en
-~----------~----~----~----~------~----~------~--~-