[FHZ] New module for USF1000S in fhem

[Tobias]

                                             

Hi,

the CVS version of fhem now supports the ultrasound fill-meter USF1000
from ELV. The state contains the fill level in % (lower case v in the
device state) and the current volume in liters (upper case V in the
device state). Measured distance to the liquid's surface, fill level,
volume and warnings (Test mode, Battery low) are available. Due to the
design of the USF1000S protocol, you can have only one USF1000S in range
of your FHZ as these devices cannot be distinguished.

Usage:

define USF1000

determines the form of the tank and the position of the
sensor. The following geometries are currently supported:

- cub
- cylv

cub stands for a cuboid whose base is × . cylv stands
for a vertical cylinder whose diameter is . is the
distance of the surface of the liquid from the ground if the tank is
full. is the distance of the sensor relative to the surface of
the liquid. All quantities are expressed in meters.

Example:

define MyTank USF1000 cylv 2 1 0.3: a cylindrical water tank with 2
meters diameter. The water stands 1 meter high if the tank is full. The
sensor is fixed 1,3 meters above ground.

Regards,
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
-~----------~----~----~----~------~----~------~--~-

[erwin]

Originally posted by: <email address deleted>

Boris,

this works only with the FHZ receiver and not with CUL, I suppose?
Is there hope that it will work with the CUL someday?

Thx,
Markus.

On 21 Jun., 09:49, "Dr. Boris Neubert" wrote:
> Hi,
>
> the CVS version of fhem now supports the ultrasound fill-meter USF1000
> from ELV. The state contains the fill level in % (lower case v in the
> device state) and the current volume in liters (upper case V in the
> device state). Measured distance to the liquid's surface, fill level,
> volume and warnings (Test mode, Battery low) are available. Due to the
> design of the USF1000S protocol, you can have only one USF1000S in range
> of your FHZ as these devices cannot be distinguished.
>
> Usage:
>
> define USF1000
>
> determines the form of the tank and the position of the
> sensor. The following geometries are currently supported:
>
> - cub
> - cylv
>
> cub stands for a cuboid whose base is × . cylv stands
> for a vertical cylinder whose diameter is . is the
> distance of the surface of the liquid from the ground if the tank is
> full. is the distance of the sensor relative to the surface of
> the liquid. All quantities are expressed in meters.
>
> Example:
>
> define MyTank USF1000 cylv 2 1 0.3: a cylindrical water tank with 2
> meters diameter. The water stands 1 meter high if the tank is full. The
> sensor is fixed 1,3 meters above ground.
>
> Regards,
> 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
-~----------~----~----~----~------~----~------~--~-

[rudolfkoenig]

                                                   

> this works only with the FHZ receiver and not with CUL, I suppose?
> Is there hope that it will work with the CUL someday?

It should be enough to append USF1000 to the $hash->{Clients} in
CUL_Initialize, like it is done in 00_FHZ.pm. Adding an entry to the
MatchList  (as "0:USF1000"! ) is optional. FS20 commands (like the
USF1000 telegrams) are converted to the FHZ format by 00_CUL.pm.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[UliM]

Originally posted by: <email address deleted>

Hmm.
I did this - however not yet there:

2009.06.24 23:17:52 3: CUL: Unknown FS20 device detected, define one
to get detailed information.

What I added to fhem.cfg is "define Wasser USF1000 cub 285 68 155 20"

My 00CUL reads:

$hash->{Clients} = ":FS20:FHT:KS300:CUL_EM:CUL_WS:USF1000:";
  my %mc = (
    "1:FS20"  => "^81..(04|0c)..0101a001",
    "2:FHT"   => "^81..(04|09|0d)..(0909a001|83098301|c409c401)..",
    "3:KS300" => "^810d04..4027a001",
    "4:CUL_WS" => "^K.....",
    "5:CUL_EM" => "^E0.................\$",
    "6:USF1000" => "^810c04..0101a001a5ceaa00...."
  );


Any idea?

Thx,
Markus.


On 24 Jun., 17:33, Rudolf Koenig wrote:
> > this works only with the FHZ receiver and not with CUL, I suppose?
> > Is there hope that it will work with the CUL someday?
>
> It should be enough to appendUSF1000to the $hash->{Clients} in
> CUL_Initialize, like it is done in 00_FHZ.pm. Adding an entry to the
> MatchList  (as "0:USF1000"! ) is optional. FS20 commands (like theUSF1000telegrams) are converted to the FHZ format by 00_CUL.pm.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[Tobias]

                                             

Markus Voss wrote:
>   my %mc = (
>     "1:FS20"  => "^81..(04|0c)..0101a001",
>     "2:FHT"   => "^81..(04|09|0d)..(0909a001|83098301|c409c401)..",
>     "3:KS300" => "^810d04..4027a001",
>     "4:CUL_WS" => "^K.....",
>     "5:CUL_EM" => "^E0.................\$",
>     "6:USF1000" => "^810c04..0101a001a5ceaa00...."
>> It should be enough to appendUSF1000to the $hash->{Clients} in
>> CUL_Initialize, like it is done in 00_FHZ.pm. Adding an entry to the
>> MatchList  (as "0:USF1000"! ) is optional. FS20 commands (like theUSF1000telegrams) are converted to the FHZ format by 00_CUL.pm.


please try to put USF1000 first in the list of patterns as the USF1000
pattern is more special than the general FS20 pattern.

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
-~----------~----~----~----~------~----~------~--~-

[Guest]

Originally posted by: <email address deleted>

> please try to put USF1000 first in the list of patterns as the USF1000
> pattern is more special than the general FS20 pattern.


I really appreciate your help - thanks.
So new version is like this:

  $hash->{Clients} = ":USF1000:FS20:FHT:KS300:CUL_EM:CUL_WS:";
  my %mc = (
    "1:USF1000" => "^810c04..0101a001a5ceaa00....",
    "2:FS20"  => "^81..(04|0c)..0101a001",
    "3:FHT"   => "^81..(04|09|0d)..(0909a001|83098301|c409c401)..",
    "4:KS300" => "^810d04..4027a001",
    "5:CUL_WS" => "^K.....",
    "6:CUL_EM" => "^E0.................\$"
  );

However, every half hour I still get:
2009.06.25 09:18:12 3: CUL: Unknown FS20 device detected, define one
to get detailed information.

Can I do anything to debug this?

Markus.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[rudolfkoenig]

                                                   

> However, every half hour I still get:
> 2009.06.25 09:18:12 3: CUL: Unknown FS20 device detected, define one
> to get detailed information.

I checked in a modified 00_CUL.pm / 09_USF1000.pm, which hopefully
will do it. I tested it with fake commands, so I am not quite sure if
it works. Please give us feedback.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[Tobias]

Originally posted by: <email address deleted>

Will do -
in the meantime I have increased loglevel and see the following
sequence from CUL in the log:

2009.06.25 10:18:14 5: CUL/RAW: /FA5CEAA374F25
2009.06.25 10:18:14 4: CUL: FA5CEAA374F -55.5
2009.06.25 10:18:14 5: CUL dispatch 810a04xx0101a001a5ceaa00374f

Point seems to be that match-Code is different from what Boris has.
Maybe devices are different.
If I read your "new" code correctly, this new code will not recognize
this diffent match-code, right?

Markus.


On 25 Jun., 10:07, Rudolf Koenig wrote:
> > However, every half hour I still get:
> > 2009.06.25 09:18:12 3: CUL: Unknown FS20 device detected, define one
> > to get detailed information.
>
> I checked in a modified 00_CUL.pm / 09_USF1000.pm, which hopefully
> will do it. I tested it with fake commands, so I am not quite sure if
> it works. Please give us feedback.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[Guest]

Originally posted by: <email address deleted>

Info:
I have manually changed the matchcode to what I have seen in the log
and technically it works now!!
I am very pleased.

However, I would prefer if the fhem sources would directly support.
@Boris: if triggers for level/volume/warning would be there to enable
DBlogging, that would be even nicer.

Thx,
Markus.


> Point seems to be that match-Code is different from what Boris has.
> Maybe devices are different.
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[rudolfkoenig]

                                                   

> However, I would prefer if the fhem sources would directly support.
I changed the matchcode too. Are you sure you are using the current
09_UFS100.pm?

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[Guest]

Originally posted by: <email address deleted>

You're right. It works. I misread the code.

Markus.

On 25 Jun., 11:33, Rudolf Koenig wrote:
> > However, I would prefer if the fhem sources would directly support.
>
> I changed the matchcode too. Are you sure you are using the current
> 09_UFS100.pm?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-

[Dr. Boris Neubert]

                                             

Markus Voss schrieb:
> 2009.06.25 10:18:14 5: CUL dispatch 810a04xx0101a001a5ceaa00374f

The difference is in the second byte which is 0x0a in your case and 0x0c
in any other know case up to now.

Shouldn't the second byte contain the remaining length of the datagram,
which is 0x0c (=12) in any case? In other words, isn't the above a
corrupt message in the FS20 sense?

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
-~----------~----~----~----~------~----~------~--~-

[rudolfkoenig]

                                                   

> Shouldn't the second byte contain the remaining length of the datagram,
> which is 0x0c (=12) in any case? In other words, isn't the above a
> corrupt message in the FS20 sense?

Not really, it is a corrupt FHZ message. 00_CUL.pm reformats the
messages to the (imho quite strange) FHZ format, so that the existing
FS20/HMS/etc modules can be reused. As the modules up till now did not
checked the length of the message, the buggy reformatting did not
caused any problems.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~-