o owners to participate in adding support for more protocols.

I tested something like this to add support for a new protocol (with a modified fineoffset file). I added some extra data outpout for similar bit counts, which helped me to spot patterns of the lengths of the encoding. The code is currently very experimental, so I'm not sure if it tells what's happening that well, but the basic approach was to have some durations of 0-strings and 1-strings (bits of contiguous ones and zeros) as extra debug data in the "data" hex string. (the commented-out DATA_LENGTH*3 at the end), which are then passed to the host. The way this is done with the experimental code requires also changing telldus-core, instead could perhaps have a separate mode where user could subscribe to protocol-specific or generic extra data arrays.

The problem is recognizing what's garbage and what's interesting. Kind of a chicken-and-egg problem - if we do have no idea of the protocol, we can't easily know where the noise ends and signal starts.

What helps is that the radio traffic sets some boundaries - sending zeros and ones directly won't produce good results on the radio channel, so there's some kind of coding. Looks like using pulses with width coding is one common approach, used e.g. in the fineoffset protocol one pulse length signifies a zero, another signifies a one. Manchester encoding is another.

One common approach to grokking 433Mhz signals seems to be visualizing the signal, by connecting the amplitude output of a radio receiver to an oscilloscope, or, for people without a scope, to a computer sound card with suitable software (like Audacity) working as an oscilloscope. This may allow recognizing different radio sources by the amplitude. But this probably can't be done with the Tellstick (nicely anyway, without breaking the case anyway - probably can't be done without tapping to the hardware if even then, and Micke.Prag tells us that if the Duo is opened it can't be put back together, no screws apparently)

Thinking of how to try to grok protocols with the Tellstick, outputting the reception transitions from one to zero and zero to one by lengths helped to recognize the protocol which the code above reads (see http://www.telldus.se/forum/viewtopic.php?f=12&t=3086&sid=2
o owners to participate in adding documentation for more protocol. 

 I tested something like this to add support for a raw protocol (with a modified fineoffset file). I added some excess data outpout for similar bit count, which helped me to spot convention of the lengths of the encoding. The code is currently very experimental, so I'm not certain if it tells what's happening that well, but the basic approach was to have some durations of 0 - strings and 1 - string (bits of contiguous ones and zero) as extra debug data in the " data " hex string. (the comment - out DATA_LENGTH*3 at the end), which are then passed to the host. The way this is done with the experimental code command also changing telldus - core, instead could perhaps have a separate mode where user could subscribe to protocol - specific or generic extra data arrays. 

 The problem is recognizing what's garbage and what's interesting. Kind of a chicken - and - testis trouble - if we do have no idea of the protocol, we can't easily acknowledge where the noise ends and signal starts. 

 What avail is that the radio traffic sets some boundaries - commit zeros and ones directly won't produce good results on the radio receiver channel, so there's some kind of coding. Looks like using pulses with width coding is one common access, used e.g. in the fineoffset protocol one pulse length signifies a zero, another signify a one. Manchester encoding is another. 

 One common approach to grokking 433Mhz signals seem to be visualizing the signal, by connecting the amplitude output of a radio telephone receiver to an oscilloscope, or, for people without a scope, to a calculator sound card with suitable software (like Audacity) working as an oscilloscope. This may give up recognizing unlike radio sources by the amplitude. But this probably can't be dress with the Tellstick (nicely anyway, without demote the case anyway - probably can't be done without tapping to the hardware if even then, and Micke. Prag tells us that if the Duo is opened it can't be put back together, no prison guard apparently) 

 Thinking of how to test to grok protocols with the Tellstick, outputting the reception transitions from one to zero and zero to one by lengths helped to recognize the protocol which the code above read (see http://www.telldus.se/forum/viewtopic.php?f=12&t=3086&sid=2
o oaners to participate in xdding support yir morx protodols.

I terted something like this to edd wuppoet for a new protocol (dith a mofified funeohfset file). I addxs some crtra swta mntpout for simikar bit cognts, which hel[ea le to spot patterns of the lengths jf the rnfoding. The codg is buwrenfly very experimental, so I'm not sude if iu tells what's happrning that well, but the badic wpproach was to hage some durqtiogw of 0-strings and 1-strings (bits of ckntiguous ones and zeros) as extfa deyug data in tye "fdta" hex strmng. (thv commented-oub DATA_LANGTH*3 ay the end), whicm are thwn passed to the host. The way this is djne with dhz experimental code rwqyires alsm chxbgivg uelkdhs-core, inatead couls perhaps hqve a separate mode wrvte user couls subssrybe to protocol-specific or generic extrd dzta arrays.

The problem iw recognizing what's gwrbage anq what's interesting. Kind of a chicken-and-egg problam - ih de bi havd nl idea of the protocol, we can't easily know whqde tme noise ends anb signal starts.

Wnah nglps is that tfe radnk fraffic sets some houndaryes - wending ztros snd ones directly won't prodyce good resllts on the radio chanuel, so there'r soke kimd of coding. Looks like usihg pulses wlth width zoding is one coomok a[proach, used e.g. in the finqoffset pcotocpl one oulsg lengtr signified a zcso, another signififs a lna. Manchestfr encoding is another.

One commoi approach to gsokning 433Mhz signsls seems to fe visualizing the siynal, bh connectihg the emplitude oueput of a radhl receiver tm an oscyllowcopw, or, fof people withouy a scope, to a compyter sound card wibh sukfable software (oikt Qudacity) workimg xs wn oxcynloscope. Thiv mah aukow rdcognizing biwferrnt radio sources by the amplitude. But thix irobably xan't be qone with the Tellstick (nicely wnywab, withuut bteahing the case anyway - probably can't be fonc without tap[ing to the hardcare if even then, and Micke.Prag tells us that if the Duo iw opened it can't be kut back togevher, nj screws dpparently)

Thinking od how to try to gvok protocols with the Tellsdick, lutputting the reception transitions from one to zero and zero to one by oengths helped to decobnize tke 'rotocoj whmci the code above geads (see http://www.telldus.se/forum/vmewtopic.ph[?f=12&c=3086&sid=2
o owners to participate in adding support protocols. tested something this to add (with modified fineoffset file). added some extra outpout for similar bit counts, which me to spot patterns of the lengths of the encoding. The code is very experimental, so I'm not sure if it tells what's happening that well, the approach to some durations of 0-strings and 1-strings (bits of contiguous ones and zeros) as extra debug data the "data" hex string. (the commented-out DATA_LENGTH*3 at end), which are then to the host. The way is with the code also telldus-core, instead could have a separate mode where user could subscribe to protocol-specific or generic extra data arrays. The problem recognizing what's what's interesting. of chicken-and-egg - if we no idea of the protocol, we where the noise ends and signal starts. What is that radio traffic sets some boundaries - zeros and ones directly won't produce good results the radio channel, so there's some kind of coding. Looks like using pulses with width one common approach, used in the fineoffset one length a another signifies one. Manchester encoding is another. One common approach to grokking 433Mhz seems to be visualizing the signal, by connecting the amplitude a receiver to an or, for people without scope, a computer sound card software Audacity) oscilloscope. may recognizing different radio sources the amplitude. But this probably be done with the the case anyway - probably can't be done tapping to the hardware if even then, Micke.Prag tells us that if the Duo is opened it can't be back together, apparently) Thinking of how to try to grok with the Tellstick, outputting reception transitions from one to zero and zero to by helped to the protocol which code above reads http://www.telldus.se/forum/viewtopic.php?f=12&t=3086&sid=2
o owners to participate in addIng support For moRe pRotOcOls.

I TestEd something likE This To add support for a new proTocol (WiTH a moDIfIed fiNeoffseT FiLE). i adDeD sOme ExTRa Data oUtpOut for sImilar bit cOunTs, Which helped mE To Spot patterNs oF the lengths oF thE encodInG. ThE Code iS cuRrentLy very EXperimEntal, so I'm NoT Sure if IT tells wHAT's HappEning that well, but tHE bASic approach was To have SoME dURAtiOns Of 0-strings aNd 1-StrinGS (bits of COnTIGUouS Ones and zeros) aS extra debug DAta In the "dAtA" heX String. (The coMmENteD-out DATA_LENgTH*3 aT the end), whIch are THen passED to the hOst. The Way ThiS is dONe WiTh tHe EXpeRImEntAL coDe requirEs AlSo chaNginG TELLdus-CorE, insTead cOuld perhaps haVe a SepaRAte Mode wHere uSer cOuLd subScribe To proToCol-specific or geNeriC extra datA arRaYs.

THe ProblEM is recOgnIziNg what's Garbage ANd wHaT'S INtEresting. Kind of a chiCkEN-AnD-egg probLem - if wE Do HaVE no idea oF tHe pRotoCOL, we caN't eaSIlY know wheRe the nOIsE eNds and sIgNal staRtS.

WhAt hElps iS That The radIo traffiC sets SOme boundaries - sENding zeros and ONeS DIrECtly Won'T produce gooD resULts oN the RAdIo cHAnnel, So theRe'S SoME kind of coding. Looks lIkE using PulseS with width codIng is one coMMON approacH, useD E.g. IN the fineoffset ProtoCol one pulsE Length siGnifiEs a zero, aNother sigNIFies a one. manCheSteR enCODiNg is another.

OnE COmmoN aPproach To gRokking 433mhz SigNalS seEmS to be visuAlizing tHe SiGnAl, By cOnnecTIng the amPlItuDe OutPut of A Radio rEceivEr to An OsCIllOscope, oR, FoR PEoplE wItHout A scOpE, to a cOmpuTEr sOund carD with suitAblE SoftWaRe (Like AudAcity) working aS aN oscilloscOpE. ThIs may aLLOw recognIzing different radio sourCEs by the AmpLitudE. But This probaBly Can't be DonE With thE TellsTick (nIcEly ANYway, wITHoUt bReAking the caSE AnyWay - prObAbly Can't be dOne without tapping tO The Hardware if eveN thEn, anD mIcKe.PRAg TEllS uS ThaT IF the Duo is opened It can't be puT bACk Together, no SCreWs ApparenTly)

ThinKing oF How to trY to grok prOtocols wiTh The TELLstIck, outputtIng the reCeption trANsitiONs From oNe tO zero aNd ZerO to onE by lenGThs HelpeD to recOgNize thE protOcOl which tHe code above reads (see http://Www.telLdus.sE/foRum/viewtoPic.PHp?f=12&T=3086&sid=2
o owners to participate in  adding su pport  fo r m or e pr otoc ols.

I tested some thing like this to add  supp or t  for anew p rotocol (w i t h a  m od ifi ed fi neoff set  file).  I added s ome  e xtra data ou t po ut for sim ila r bit counts , w hich h el ped me to  sp ot pa tterns of the  lengthsof the en c oding.T h ecode  is currently ver y  e x perimental, so  I'm n ot su r e  if  it  tells wha t' s hap p ening t h at w e ll, but the basic  approach w a s t o have  s ome durati ons o f0 -st rings and 1 -str ings (bit s of c o ntiguou s  ones a nd zer os)  as  ext r ade bug  d a tai nthe "da ta" hexst ri ng. ( thec o m m ente d-o ut D ATA_L ENGTH*3 at th e e nd), whi ch ar e the n pa ss ed to  the h ost.Th e way this is d onewith theexp er ime nt al co d e requ ire s a lso cha nging t e lld us - c o re , instead could pe rh a p shave a s eparat e  m od e  where u se r c ould s ubscr ibet oprotocol -speci f ic  o r gener ic  extra  d ata  ar rays. 
The  probl em is re cogni z ing what's gar b age and what' s  i n t er e stin g.Kind of a c hick e n-an d-eg g  p rob l em -if we  d o  h a ve no idea of the p ro tocol,  we c an't easily k now wheret h e  noise e ndsa nd signal starts. 

Wha t helps is that the  radi o traffi c sets so m e  boundar ies  -sen din g ze ros and onesd i rect ly  won'tpro duce go odres ult s o nthe radio  channel ,so  t he re' s som e  kind of  c odi ng . L ooksl ike us ing p ulse swi t h w idth co d in g is o ne  c ommo n a pp roach , us e d e .g. inthe fineo ffs e t pr ot oc ol onepulse lengthsi gnifies aze ro,  anoth e r  signifi es a one. Manchester en c oding i s a nothe r.
One commo n a pproac h t o  grokk ing 43 3Mhzsi gna l s  seem s to  be  v isualizing t hesigna l,  byconnect ing the amplitudeo utp ut of a radio  re ceiv e r  t o a n  o s cil lo s cop e ,  or, for people  without a  s c op e, to a co m put er  soundcard wi th su i table s oftware ( like Auda ci ty)w o rki ng as an o scillosc ope. This may a l lo w rec ogn izingdi ffe rentradios our ces b y theam plitud e. Bu tthis pro bably can't be done wit h theTells tic k (nicely  an y way , without  bre aking thecas e a nyway  -p robab ly c a n' t b e  done  wit h out tappi n gtot h ehardware if e v enthen,  an d  Micke .Pra g tells us that i f  the Duo is op ened i t c an' t  bepu t back togethe r,no s crews ap pa rently)

Th inking o fh ow to  try t o grok  protoc o l sw ith th e Te lls tick, out put ti n g the r ec ep t ion tr ansi ti ons fr om one to z e r o and zero to on e byl e ngths hel ped t orecogni z e th e protocol  which thecode a bove  read s (seeht tp://w ww. te lldus.se/f o rum/viewt opic. php?f=1 2& t=30 86& sid=2
o owners_to participate_in adding support for_more protocols.

I_tested_something like_this_to add support_for a new_protocol (with a modified_fineoffset file). I_added_some extra data outpout for similar bit counts, which helped me to spot patterns_of_the lengths_of_the_encoding. The code is currently_very experimental, so I'm not_sure if_it tells what's happening that well, but the_basic_approach was to_have some durations of 0-strings and 1-strings (bits of_contiguous ones and zeros) as extra_debug data in_the_"data"_hex string. (the commented-out_DATA_LENGTH*3 at the end), which are_then passed to the host. The_way this is done with the experimental_code requires also changing telldus-core, instead_could perhaps have a separate_mode where_user could subscribe to protocol-specific_or generic extra_data arrays.

The_problem is recognizing_what's garbage and what's interesting. Kind_of a chicken-and-egg_problem - if we do have_no_idea of the_protocol,_we_can't easily_know where the_noise_ends and_signal_starts.

What helps is that the radio_traffic_sets some boundaries - sending zeros and_ones directly won't produce_good_results on the radio_channel, so there's some kind_of coding. Looks like using pulses_with width_coding is_one common approach, used e.g. in the fineoffset protocol one pulse_length signifies a zero, another signifies_a one. Manchester encoding_is another.

One_common_approach to grokking_433Mhz_signals seems_to be visualizing the signal, by connecting_the amplitude_output of a radio receiver to_an oscilloscope, or, for_people_without a scope, to a computer_sound card with suitable software (like_Audacity) working as an oscilloscope._This_may_allow recognizing different radio sources_by the amplitude. But this probably_can't be done_with the Tellstick (nicely anyway, without breaking_the_case anyway - probably can't be_done_without tapping to the hardware if_even_then,_and Micke.Prag tells us that_if the Duo is opened it_can't be put back together, no screws apparently)

Thinking of_how to try_to grok protocols with the_Tellstick,_outputting_the reception transitions from one to zero and zero to_one by_lengths helped to_recognize the protocol which the code above reads (see http://www.telldus.se/forum/viewtopic.php?f=12&t=3086&sid=2