The iBLab code is available by anonymous CVS or as a tarball.
The tarball snapshot is updated daily at midnight, UK time. It can be fetched from:
http://anoncvs.aldigital.co.uk/snapshots/iBLabAnonymous CVS lives at:
anoncvs.aldigital.co.uk:/cvsroot/anoncvs.aldigital.co.uk-iBLabto check out with CVS, do the following:
cvs -d ":pserver:email@example.com:/cvsroot" loginpassword is "anoncvs". Once logged in, do:
cvs -d ":pserver:firstname.lastname@example.org:/cvsroot" co anoncvs.aldigital.co.uk-iBLabthis should create a directory called "anoncvs.aldigital.co.uk-iBLab", which will contain the current source tree. At any time, anwhere within this tree, you can type:
cvs updateto get the latest versions and keep your tree up to date.
The offical Dallas Semiconductor iButton home page can be found at:
Cyclic's CVS tools can be found at:
Ryan Lackey runs a related mailing list, "ibuttonpunks", which can be found by mailing:
email@example.com with "help" in the body of the text. iBLab issues should be discussed there.
Also, Dallas only supported Windows and DOS.
If you develop a useful application using iBLab, please let us know and we'll link to it from here.
A.L.: If we develop an application that communicates with the i-buttons, without using the SDK (i.e. we develop our own drivers from the information contained in the data book), are there any licencing issues, or can we freely distribute that code under any conditions we see fit? D.S.: If you develop your own code...it is yours. Adam, you will be doing a lot of work that has already been done for you. Using TMEX will save you a lot of time, but it is your choice.So I guess that means we don't have to use TMEX.
Please send submissions to: iBLab@aldigital.co.uk