Page 1 of 1
Tellstick DUO long pulses
Posted: Fri Mar 17, 2023 9:45 am
by jrathert
When I try to send a pulse or space longer than 2550us with tdtool it is not working.
I think the 1 byte is not working in the DUO firmware.
I tried it with firmware V4 and V5.
The command is like the following:
'S',10,255,1,45,10,'+'
It should be 100 us pulse , 3ms space and 100 us pulse .
Best regards,
Jan Rathert
Re: Tellstick DUO long pulses
Posted: Fri Mar 17, 2023 9:45 am
by c0rner
Good post Jan,
I've also been looking into this since I found a note about this "trick" somewhere.. do not remember where and the documentation on the Tellstick protocol is a bit dodgy.
Anyway, looking at the Tellstick NET source (send.c) you see this code which indicates that the it has support for sending long pulses, the code will basically "skip" a pulse and flip the hi/low status back enabling long pulses.
Code: Select all
if ( (*j) == 1 ) {
status=~status;
continue;
}
UPDATE!
As for the standard TS and the Duo I cannot find any indication of this being implemented,unfortunately I have no access to http://git.telldus.com/telldus-common.git/ to verify.
Looking at the Duo source it seems it too has this functionality, not sure if available in fw V4 though.
Code: Select all
if (string[i] == 1) {
rfNextIsZero = 1;
continue;
}
//Martin
Re: Tellstick DUO long pulses
Posted: Fri Mar 17, 2023 9:45 am
by jorang
...or maybe you can use one of these:
http://intertechno.at/produkte/empfaeng ... index.html
Download the a applicable version/ language of the product catalogue at the top

Re: Tellstick DUO long pulses
Posted: Fri Mar 17, 2023 9:45 am
by c0rner
A comment from Telldus would be nice. Does the V4 and/or V5 fw support long pulses? It's in the source code but there is no indication of version..
Re: Tellstick DUO long pulses
Posted: Fri Mar 17, 2023 9:45 am
by micke.prag
Yes, TellStick Duo supports long pulses. It is used for some protocols.
Re: Tellstick DUO long pulses
Posted: Fri Mar 17, 2023 9:45 am
by c0rner
Thanks! I can verify that this works on a Duo running fw5 after I fixed a bug in my software
