Autor Thema: [FHZ] FHZ1300 on windows xp COM port  (Gelesen 590 mal)

Offline Oskar

  • Full Member
  • ***
  • Beiträge: 236
[FHZ] FHZ1300 on windows xp COM port
« am: 12 September 2008, 16:50:16 »
Originally posted by: <email address deleted>

Hello,

I am trying to communicate with a FHZ 1300 device. I have gone through
the installation process and a simple configuration file.

I got the following message: Can't locate Device/SerialPort.pm in
@INC.

At the end of the post is a fragment of the log file. I would like to
know if someone has had this problem before and how I can solve it.
I have also installed the software that came with the unit


2008.09.12 13:10:41 5: Cmd: >attr global port 7073<
2008.09.12 13:10:41 5: Cmd: >attr global modpath /usr/local/lib<
2008.09.12 13:10:41 5: Loading /usr/local/lib/FHEM/99_SUNRISE_EL.pm,
order 99
2008.09.12 13:10:41 5: Loading /usr/local/lib/FHEM/99_Utils.pm, order
99
2008.09.12 13:10:41 5: Cmd: >define FHZ FHZ /dev/tts/USB0<
2008.09.12 13:10:41 5: Loading /usr/local/lib/FHEM/00_FHZ.pm, order 00
2008.09.12 13:10:41 3: FHZ opening FHZ device /dev/tts/USB0
Can't locate Device/SerialPort.pm in @INC (@INC contains: /usr/lib/
perl5/5.10/i686-cygwin /usr/lib/perl5/5.10 /usr/lib/perl5/site_perl/
5.10/i686-cygwin /usr/lib/perl5/site_perl/5.10 /usr/lib/perl5/
vendor_perl/5.10/i686-cygwin /usr/lib/perl5/vendor_perl/5.10 /usr/lib/
perl5/vendor_perl/5.10 /usr/lib/perl5/site_perl/5.8 /usr/lib/perl5/
vendor_perl/5.8 .) at /usr/local/lib/FHEM/00_FHZ.pm line 241, <$fh>
line 9.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHZ1000 users on Linux" group.
To post to this group, send email to FHZ1000-users-on-unix@googlegroups.com
To unsubscribe from this group, send email to FHZ1000-users-on-unix+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/FHZ1000-users-on-unix?hl=en
-~----------~----~----~----~------~----~------~--~-
--
fhem geht auch auf mac os x

Offline Oskar

  • Full Member
  • ***
  • Beiträge: 236
[FHZ] Re: FHZ1300 on windows xp COM port
« Antwort #1 am: 12 September 2008, 17:53:33 »
                                                   

> I would like to
> know if someone has had this problem before and how I can solve it.

Windows should use Win32:SerialPort instead of Device::SerialPort. The
current fhem version (4.4) should request the correct module depending
on the used OS.
The number of fhem@windows users is quite small, I'm afraid (as the
name of this newsgroup tries to suggest :-)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHZ1000 users on Linux" group.
To post to this group, send email to FHZ1000-users-on-unix@googlegroups.com
To unsubscribe from this group, send email to FHZ1000-users-on-unix+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/FHZ1000-users-on-unix?hl=en
-~----------~----~----~----~------~----~------~--~-
--
fhem geht auch auf mac os x

Offline Oskar

  • Full Member
  • ***
  • Beiträge: 236
[FHZ] Re: FHZ1300 on windows xp COM port
« Antwort #2 am: 12 September 2008, 20:12:42 »
Originally posted by: <email address deleted>

here the quickinfo, download and install:
>>> FTDI ComPortDriver "CDM 2.04.06.exe"
http://www.ftdichip.com/Drivers/VCP.htm
http://www.ftdichip.com/Drivers/CDM/CDM%202.04.06.exe
>>> ActivePerl-5.10.0.1003-MSWin32-x86-285500.msi
 >>>http://search.cpan.org/CPAN/authors/id/B/BB/BBIRTH/Win32- SerialPort-0.19.tar.gz

good luck

my german install:

>>> FHZ an USB connecten und Treiber/Software installieren,
 was ja eigentlich schon passiert sein sollte:
 FHZ1300PC-CD-V2.0 ... setup.exe blabla

----
Bitte ELV Software einmal im original testen, damit HardwareFehler
ausgeschlossen werden können.
---

>>> FTDI ComPortDriver download und installieren:
"CDM 2.04.06.exe"
http://www.ftdichip.com/Drivers/VCP.htm
http://www.ftdichip.com/Drivers/CDM/CDM%202.04.06.exe

---
Im GeräteManager schauen, welcher ComPort der FTDI ist.
---

>>> ActivePerl-5.10.0.1003-MSWin32-x86-285500.msi  downloaden und installieren.

>>> Win32-SerialPort-0.19.tar.gz   downloaden und entpacken (winrar):
 http://search.cpan.org/CPAN/authors/id/B/BB/BBIRTH/Win32-Ser ialPort-0.19.tar.gz

D:\shares\Software\Tools\ActivePerl\SerialPort-0.19

12.09.2008  18:55              .
12.09.2008  18:55              ..
05.11.1999  03:11               428 Altport.pm
05.11.1999  05:14             6.772 Changes
12.09.2008  18:41               716 COM1_test.cfg
12.09.2008  18:55               716 com3_test.cfg
01.09.2008  22:48              eg
01.09.2008  22:48              html
12.09.2008  18:54               914 install.pl
01.09.2008  22:48              lib
05.11.1999  05:24             6.005 Makefile.PL
05.11.1999  05:17               419 MANIFEST
05.11.1999  05:16            11.704 README
05.11.1999  05:16            11.040 README.txt
12.09.2008  18:54              t
12.09.2008  18:54               433 test.pl
              10 Datei(en),         39.147 Bytes

>>> wie in Readme so installieren (comport anpassen):
   perl Makefile.PL com3
   perl test.pl
   perl install.pl

>>> fhem-4.4 downloaden und entpacken (winrar), z.b.:
C:\fhem-4.4>
minimale fhem.conf anlegen:
---------------------------------------------------
C:\fhem-4.4>type C:\fhem-4.4\fhem.conf
#Fri Sep 12 19:34:02 2008

attr global logfile c:/fhem-4.4/tmp/fhem-%Y-%m.log
attr global modpath .
attr global port 7072
attr global statefile c:/fhem-4.4/fhem.save
attr global verbose 5

define FHZ FHZ com3
attr FHZ fhtsoftbuffer 0

setdefaultattr
define lamp FS20 8765 01
setdefaultattr
------------------------------------------------
Logverzeichnis anlegen.
comPort anpassen
verbose Level zum Test auf 5 erhöhen.

>>> Fhem Server in cmd starten:
C:\fhem-4.4>fhem.pl fhem.conf

>>> Zur Kontrolle mal ins Log schauen, da sollte dann sowas stehen:
2008.09.12 19:26:30 5: Cmd: >attr global port 7072<
2008.09.12 19:26:30 5: Cmd: >attr global modpath .<
2008.09.12 19:26:30 5: Loading ./FHEM/99_SUNRISE_EL.pm, order 99
2008.09.12 19:26:30 5: Loading ./FHEM/99_Utils.pm, order 99
2008.09.12 19:26:30 5: Cmd: >define FHZ FHZ com3<
2008.09.12 19:26:30 5: Loading ./FHEM/00_FHZ.pm, order 00
2008.09.12 19:26:30 3: FHZ opening FHZ device com3
2008.09.12 19:26:30 3: FHZ opened FHZ device com3
2008.09.12 19:26:32 5: Cmd: >define lamp FS20 8765 01<
2008.09.12 19:26:32 5: Loading ./FHEM/10_FS20.pm, order 10
2008.09.12 19:26:32 0: Server started (version 4.4 from 2008-08-04
($Id: fhem.pl,v 1.51 2008/08/04 14:34:53 rudolfkoenig Exp $), pid
-2596)
2008.09.12 19:26:32 5: FHZ/RAW:
 810cc98b01021f048c071c138023810fc97001028401080780136e402358 1d
(Unparsed: )
2008.09.12 19:26:32 4: FHZ FHZ unknown: 810cc98b01021f048c071c138023
2008.09.12 19:26:32 4: FHZ FHZ unknown:
810fc97001028401080780136e4023581d


>>> Testen, dazu in 2. CMD:
C:\fhem-4.4>fhem.pl localhost:7072 "list"

Type list for detailed info.
_internal_:
  global               ()
FHZ:
  FHZ                  (Initialized)
FS20:
  lamp                 (???)

>>> Device in Lernmodus setzen und dann z.B. so was hinschicken:
C:\fhem-4.4>fhem.pl localhost:7072 "set lamp on"

>>> Device muß dann schon quittieren und geht ab jetzt, z.B.:
C:\fhem-4.4>fhem.pl localhost:7072 "set lamp off"
C:\fhem-4.4>fhem.pl localhost:7072 "set lamp on"

C:\fhem-4.4>fhem.pl localhost:7072 "list"

Type list for detailed info.
_internal_:
  global               ()
FHZ:
  FHZ                  (Initialized)
FS20:
  lamp                 (off)

C:\fhem-4.4>

>>> Auszug aus Log:
2008.09.12 19:27:37 4: Connection accepted from 127.0.0.1:1458
2008.09.12 19:27:37 5: Cmd: >list<
2008.09.12 19:27:37 5: Cmd: >quit<
2008.09.12 19:27:37 4: Connection closed for 127.0.0.1:1458
2008.09.12 19:28:02 4: Connection accepted from 127.0.0.1:1459
2008.09.12 19:28:02 5: Cmd: >set lamp on<
2008.09.12 19:28:02 2: FS20 set lamp on
2008.09.12 19:28:02 5: Sending 8109040101010187650111
2008.09.12 19:28:02 5: Triggering lamp (1 changes)
2008.09.12 19:28:02 5: Cmd: >quit<
2008.09.12 19:28:02 4: Connection closed for 127.0.0.1:1459
<<<

fertig. viel Spaß

PS.: C:\fhem-4.4>fhem.pl localhost:7072 "save"
   speichert den Status in die konfigurierte fhem.save :
type C:\fhem-4.4\fhem.save
#Fri Sep 12 19:34:02 2008
setstate FHZ Initialized
setstate global
setstate lamp on
setstate lamp 2008-09-12 19:28:02 state on


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHZ1000 users on Linux" group.
To post to this group, send email to FHZ1000-users-on-unix@googlegroups.com
To unsubscribe from this group, send email to FHZ1000-users-on-unix+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/FHZ1000-users-on-unix?hl=en
-~----------~----~----~----~------~----~------~--~-
--
fhem geht auch auf mac os x

Offline Oskar

  • Full Member
  • ***
  • Beiträge: 236
[FHZ] Re: FHZ1300 on windows xp COM port
« Antwort #3 am: 15 September 2008, 15:44:20 »
Originally posted by: <email address deleted>

Hello Celica and also Rudolf, Danke für die Antworten.
Ich habe celica step by step guide gemacht und es hat geklapt.

So thank you a lot, I had already done that but maybe I had made something
wrong at the beginning. Just for the record and in case someone else find
himself with this trouble I would like to add the following notes:

I made celica step from the DOS command prompt and once the server was
running I ran the telnet localhost 7072 from a Cygwin prompt, because in the
DOS prompt the data is presented unorganized.

I was unable to assign another COM port different from the COM3, the test.pl
gave me always a lot errors.

I will do my best later to document the application on which I am working
now to give my collaboration to this group.

Regards,
Roberto

On Fri, Sep 12, 2008 at 8:12 PM, celica wrote:

>
> here the quickinfo, download and install:
> >>> FTDI ComPortDriver "CDM 2.04.06.exe"
> http://www.ftdichip.com/Drivers/VCP.htm
> http://www.ftdichip.com/Drivers/CDM/CDM%202.04.06.exe
> >>> ActivePerl-5.10.0.1003-MSWin32-x86-285500.msi
> >>>
>  http://search.cpan.org/CPAN/authors/id/B/BB/BBIRTH/Win32-Ser ialPort-0.19.tar.gz
>
> good luck
>
> my german install:
>
> >>> FHZ an USB connecten und Treiber/Software installieren,
>  was ja eigentlich schon passiert sein sollte:
>  FHZ1300PC-CD-V2.0 ... setup.exe blabla
>
> ----
> Bitte ELV Software einmal im original testen, damit HardwareFehler
> ausgeschlossen werden können.
> ---
>
> >>> FTDI ComPortDriver download und installieren:
> "CDM 2.04.06.exe"
> http://www.ftdichip.com/Drivers/VCP.htm
> http://www.ftdichip.com/Drivers/CDM/CDM%202.04.06.exe
>
> ---
> Im GeräteManager schauen, welcher ComPort der FTDI ist.
> ---
>
> >>> ActivePerl-5.10.0.1003-MSWin32-x86-285500.msi  downloaden und
> installieren.
>
> >>> Win32-SerialPort-0.19.tar.gz   downloaden und entpacken (winrar):
>
>  http://search.cpan.org/CPAN/authors/id/B/BB/BBIRTH/Win32-Ser ialPort-0.19.tar.gz
>
> D:\shares\Software\Tools\ActivePerl\SerialPort-0.19
>
> 12.09.2008  18:55              .
> 12.09.2008  18:55              ..
> 05.11.1999  03:11               428 Altport.pm
> 05.11.1999  05:14             6.772 Changes
> 12.09.2008  18:41               716 COM1_test.cfg
> 12.09.2008  18:55               716 com3_test.cfg
> 01.09.2008  22:48              eg
> 01.09.2008  22:48              html
> 12.09.2008  18:54               914 install.pl
> 01.09.2008  22:48              lib
> 05.11.1999  05:24             6.005 Makefile.PL
> 05.11.1999  05:17               419 MANIFEST
> 05.11.1999  05:16            11.704 README
> 05.11.1999  05:16            11.040 README.txt
> 12.09.2008  18:54              t
> 12.09.2008  18:54               433 test.pl
>              10 Datei(en),         39.147 Bytes
>
> >>> wie in Readme so installieren (comport anpassen):
>   perl Makefile.PL com3
>   perl test.pl
>   perl install.pl
>
> >>> fhem-4.4 downloaden und entpacken (winrar), z.b.:
> C:\fhem-4.4>
> minimale fhem.conf anlegen:
> ---------------------------------------------------
> C:\fhem-4.4>type C:\fhem-4.4\fhem.conf
> #Fri Sep 12 19:34:02 2008
>
> attr global logfile c:/fhem-4.4/tmp/fhem-%Y-%m.log
> attr global modpath .
> attr global port 7072
> attr global statefile c:/fhem-4.4/fhem.save
> attr global verbose 5
>
> define FHZ FHZ com3
> attr FHZ fhtsoftbuffer 0
>
> setdefaultattr
> define lamp FS20 8765 01
> setdefaultattr
> ------------------------------------------------
> Logverzeichnis anlegen.
> comPort anpassen
> verbose Level zum Test auf 5 erhöhen.
>
> >>> Fhem Server in cmd starten:
> C:\fhem-4.4>fhem.pl fhem.conf
>
> >>> Zur Kontrolle mal ins Log schauen, da sollte dann sowas stehen:
> 2008.09.12 19:26:30 5: Cmd: >attr global port 7072<
> 2008.09.12 19:26:30 5: Cmd: >attr global modpath .<
> 2008.09.12 19:26:30 5: Loading ./FHEM/99_SUNRISE_EL.pm, order 99
> 2008.09.12 19:26:30 5: Loading ./FHEM/99_Utils.pm, order 99
> 2008.09.12 19:26:30 5: Cmd: >define FHZ FHZ com3<
> 2008.09.12 19:26:30 5: Loading ./FHEM/00_FHZ.pm, order 00
> 2008.09.12 19:26:30 3: FHZ opening FHZ device com3
> 2008.09.12 19:26:30 3: FHZ opened FHZ device com3
> 2008.09.12 19:26:32 5: Cmd: >define lamp FS20 8765 01<
> 2008.09.12 19:26:32 5: Loading ./FHEM/10_FS20.pm, order 10
> 2008.09.12 19:26:32 0: Server started (version 4.4 from 2008-08-04
> ($Id: fhem.pl,v 1.51 2008/08/04 14:34:53 rudolfkoenig Exp $), pid
> -2596)
> 2008.09.12 19:26:32 5: FHZ/RAW:
>  810cc98b01021f048c071c138023810fc97001028401080780136e402358 1d
> (Unparsed: )
> 2008.09.12 19:26:32 4: FHZ FHZ unknown: 810cc98b01021f048c071c138023
> 2008.09.12 19:26:32 4: FHZ FHZ unknown:
> 810fc97001028401080780136e4023581d
>
>
> >>> Testen, dazu in 2. CMD:
> C:\fhem-4.4>fhem.pl localhost:7072 "list"
>
> Type list for detailed info.
> _internal_:
>  global               ()
> FHZ:
>  FHZ                  (Initialized)
> FS20:
>  lamp                 (???)
>
> >>> Device in Lernmodus setzen und dann z.B. so was hinschicken:
> C:\fhem-4.4>fhem.pl localhost:7072 "set lamp on"
>
> >>> Device muß dann schon quittieren und geht ab jetzt, z.B.:
> C:\fhem-4.4>fhem.pl localhost:7072 "set lamp off"
> C:\fhem-4.4>fhem.pl localhost:7072 "set lamp on"
>
> C:\fhem-4.4>fhem.pl localhost:7072 "list"
>
> Type list for detailed info.
> _internal_:
>  global               ()
> FHZ:
>  FHZ                  (Initialized)
> FS20:
>  lamp                 (off)
>
> C:\fhem-4.4>
>
> >>> Auszug aus Log:
> 2008.09.12 19:27:37 4: Connection accepted from 127.0.0.1:1458
> 2008.09.12 19:27:37 5: Cmd: >list<
> 2008.09.12 19:27:37 5: Cmd: >quit<
> 2008.09.12 19:27:37 4: Connection closed for 127.0.0.1:1458
> 2008.09.12 19:28:02 4: Connection accepted from 127.0.0.1:1459
> 2008.09.12 19:28:02 5: Cmd: >set lamp on<
> 2008.09.12 19:28:02 2: FS20 set lamp on
> 2008.09.12 19:28:02 5: Sending 8109040101010187650111
> 2008.09.12 19:28:02 5: Triggering lamp (1 changes)
> 2008.09.12 19:28:02 5: Cmd: >quit<
> 2008.09.12 19:28:02 4: Connection closed for 127.0.0.1:1459
> <<<
>
> fertig. viel Spaß
>
> PS.: C:\fhem-4.4>fhem.pl localhost:7072 "save"
>   speichert den Status in die konfigurierte fhem.save :
> type C:\fhem-4.4\fhem.save
> #Fri Sep 12 19:34:02 2008
> setstate FHZ Initialized
> setstate global
> setstate lamp on
> setstate lamp 2008-09-12 19:28:02 state on
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "FHZ1000 users on Linux" group.
To post to this group, send email to FHZ1000-users-on-unix@googlegroups.com
To unsubscribe from this group, send email to FHZ1000-users-on-unix+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/FHZ1000-users-on-unix?hl=en
-~----------~----~----~----~------~----~------~--~---
--
fhem geht auch auf mac os x

 

decade-submarginal