Originally posted by: <email address deleted>
Is it possible to control a FHT 8v valve directly with a CUL as I
already have 1wire temperature sensors.
Thanks
--
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.
On Tue, Mar 30, 2010 at 08:44:36AM -0700, floyd wrote:
> Is it possible to control a FHT 8v valve directly with a CUL as I
> already have 1wire temperature sensors.
CUL can control FHT 8v's directly (tested myself), but the fhem support is very
rudimentary :)
The way the CUL controls the 8v's right now is very like to how they are
controlled by the FHT80b. I received some patches for proposed changes wich
should make things on the CUL side even better, but they were never integrated.
Regards,
Rudi
--
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.
Originally posted by: <email address deleted>
On Mar 30, 8:48 pm, Rudolf Koenig wrote:
> On Tue, Mar 30, 2010 at 08:44:36AM -0700, floyd wrote:
> > Is it possible to control a FHT 8v valve directly with a CUL as I
> > already have 1wire temperature sensors.
>
> CUL can control FHT 8v's directly (tested myself), but the fhem support is very
> rudimentary :)
>
> The way the CUL controls the 8v's right now is very like to how they are
> controlled by the FHT80b. I received some patches for proposed changes wich
> should make things on the CUL side even better, but they were never integrated.
Rudi, could you give me some sample commands that I can test with
screen.
Which is the best CUL firmware to use (CUL or CUL_FHT8v)?
My 8v is conrad and it's state is 'AC' - waiting for security code.
I guess this is the house code, but I don't know how to set it from
the CUL.
Thanks,
Floyd
--
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.
> Rudi, could you give me some sample commands that I can test with
> screen.
This is all from memory, so beware:
- define your CUL housecode (1234):
T011234
(check it with T01)
- Press the 8v button until you hear a beep
- Send out a pair command:
T1234002f00
(The 8v should beep now, and the antenna symbol should quit blinking)
I am not sure here, perhaps it has to be T1234012f00 for the first 8v,
T1234022f00 for the second, and so on.
- Set all 8v valves to 20% (this is queued):
T1234002633
20*255/100 == 33 hex.
- Check when this command will be sent out:
T11
- Check the 8V buffer in the CUL
T10
- Clear the buffer:
T011234
or
T123400FF00
The third byte (00) is the 8v adress, there are 9 slots in total (00 == all 8v).
I think this is where the 8 in the name comes from.
> Which is the best CUL firmware to use (CUL or CUL_FHT8v)?
If you want to talk to an FHT8v, than I would propose the CUL_FHT8v :)
--
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.
Originally posted by: <email address deleted>
On Mar 30, 11:12 pm, Rudolf Koenig wrote:
> > Rudi, could you give me some sample commands that I can test with
> > screen.
>
> This is all from memory, so beware:
> - define your CUL housecode (1234):
> T011234
> (check it with T01)
> - Press the 8v button until you hear a beep
> - Send out a pair command:
> T1234002f00
> (The 8v should beep now, and the antenna symbol should quit blinking)
> I am not sure here, perhaps it has to be T1234012f00 for the first 8v,
> T1234022f00 for the second, and so on.
> - Set all 8v valves to 20% (this is queued):
> T1234002633
> 20*255/100 == 33 hex.
> - Check when this command will be sent out:
> T11
> - Check the 8V buffer in the CUL
> T10
> - Clear the buffer:
> T011234
> or
> T123400FF00
>
> The third byte (00) is the 8v adress, there are 9 slots in total (00 == all 8v).
> I think this is where the 8 in the name comes from.
>
> > Which is the best CUL firmware to use (CUL or CUL_FHT8v)?
>
> If you want to talk to an FHT8v, than I would propose the CUL_FHT8v :)
Thanks, the above commands worked perfectly.
Is there a command reference somewhere? I found one for FS20 at
fhx4linux but I can't see the commands you described. I thought the
FHT devices were based on FS20 - is this not the case?
--
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.
> Thanks, the above commands worked perfectly.
Thanks for the info, you are welcome to enter them into the wiki. :)
> Is there a command reference somewhere? I found one for FS20 at
> fhx4linux but I can't see the commands you described.
There are different partial documents. My reference is the 11_FHT.pm fhem
module, in the function FHT_Parse, the part with "actuator". Not very readable,
I have to admit.
> I thought the FHT devices were based on FS20 - is this not the case?
Not really. Single FHT and FS20 messages are alike up to (but not including)
the checksum. Above that FS20 sends out a message 3 times and does not wait for
an ack. FHT80b -> FHT8v is repeated twice, with no reply. FHZ<->FHT80b is not
repeated, but it is a request/reply protocol with start message / end message.
Transmitting a single byte (temperature) from the FHT80b to the FHZ consists of
6 messages from the FHT80b, and 6 replies from the FHZ (i.e. CUL), each of them
consisting of 5+1 bytes of data.
--
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.
Originally posted by: <email address deleted>
What other commands do you need next to setting the % of the valve to
open?
--
I am working on the same for my FHT8W, but besides that it can receive
10 signals and the FHT8v only one the same commands work.
Basically before we go any further it should be clear that we have the
CUN/CUL_FHT8v simulating the function of a FHT80b, the software fully
replaces the FHT80b in this case, and your heating fully depends on
your software, not sure if this is what you wish for.
First you tell the FHT8v/w device what to listen to, as nicely
described above.
You can send a command to tell the FHT8v/w device how much % the valve
should be open.
You can send this with the command (Following the 1234 house code
example)
T1234012600 -> Sets the valve to 0% open.
T1234012685 -> Sets the valve to 52% open.
T12340126FF -> Sets the valve to 100% open.
Well Rudolf already showed you how to do the Math.
The format, as far as I figured out.
THHHHDDCCVV
T = FHT protocol
HHHH = The hex House code
DD = The Device number in hex
CC = Command
VV = Value
Commands that I know:
2f
Pair.. This is just a command to let the FHT80b device know it is
there, or in this case it can be used to once tell your FHT8v/w device
the CUN/CUL_FHV8v is acting like one.
26
FHT8v = Open the valve for x %, in 8bits of Hex
FHT8W = If this is higher as the threshold set x % switch the central
heater on, in 8bits of Hex
I guess there are other commands, for low battery and maybe other
things the FHT8v/w device can do, not sure, it is opening the valve,
that is the main purpose.
Feel free to add more code's and or signals the device send or can
receive (can the FHT8v/w send?).
--
To
On 31 mrt, 17:17, floyd wrote:
> On Mar 30, 11:12 pm, Rudolf Koenig wrote:
>
>
>
>
>
> > > Rudi, could you give me some sample commands that I can test with
> > > screen.
>
> > This is all from memory, so beware:
> > - define your CUL housecode (1234):
> > T011234
> > (check it with T01)
> > - Press the 8v button until you hear a beep
> > - Send out a pair command:
> > T1234002f00
> > (The 8v should beep now, and the antenna symbol should quit blinking)
> > I am not sure here, perhaps it has to be T1234012f00 for the first 8v,
> > T1234022f00 for the second, and so on.
> > - Set all 8v valves to 20% (this is queued):
> > T1234002633
> > 20*255/100 == 33 hex.
> > - Check when this command will be sent out:
> > T11
> > - Check the 8V buffer in the CUL
> > T10
> > - Clear the buffer:
> > T011234
> > or
> > T123400FF00
>
> > The third byte (00) is the 8v adress, there are 9 slots in total (00 == all 8v).
> > I think this is where the 8 in the name comes from.
>
> > > Which is the best CUL firmware to use (CUL or CUL_FHT8v)?
>
> > If you want to talk to an FHT8v, than I would propose the CUL_FHT8v :)
>
> Thanks, the above commands worked perfectly.
>
> Is there a command reference somewhere? I found one for FS20 at
> fhx4linux but I can't see the commands you described. I thought the
> FHT devices were based on FS20 - is this not the case?- Tekst uit oorspronkelijk bericht niet weergeven -
>
> - Tekst uit oorspronkelijk bericht weergeven -
--
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.
Note 1: Just received a bugreport (unverified), which tells me that culfw
version 1.37 has problems with directly controlling the 8v's
Note 2: I plan to finish Alexander Tietzels work, and implement his proposals
in culfw and fhem for controlling the 8v's directly. In his proposal culfw
would not use the FHT device id (Byte 3) to distinguish different FHT8v's, but
the housecode (Byte 1 and 2). I hope this wont have undesired side-effects.
--
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.