In case is needed I posted my lsusb -v here goo.gl/yuVJJC
device number was 100

(hope it works never used this)

Thx,
franco

Trying to use the FocusLynx software will not work as they are completely different device controllers.

I too am very interested in whether anything further has been achieved. I have tried to use the feathouch controller on my Mac with Nebulosity, but even this option was very hit and miss as it would easily lock up and it does not have an auto focus capabilty which means I am better off using the hand controller to do the focusing.

Regards

Paul

This weekend I got an email from Dean Koenig at Starizona with some really helpful information after bugging him with my emails, sorry for that . I started to modify the Moonlite driver to make it work with the Microtouch protocoll. Right now, basic movement is working. It is not pretty, but promissing.

Marco

Ready to support you with testing....if needed

Thx,
Franco

I too am happy to beta test too. Thanks for your efforts!

Marco,

I am sure there are many that would like to test this, I am happy to hear that something is progressing.

Regards

Paul

FYI,

knro committed on GitHub 19 hours ago

Merge pull request #40 from mp77/master
Initial Microtouch driver, based on Moonlite driver

Basic movement, getting Temperature, set TempCallibration, get/set Motorspeed and abort/zero works. Still some work to do.
//ToDo

TempComp
Reset to Position
...

Marco,

I have have had a go at trying to use the microtouch controller but can't get any further than the following:

indiserver -v -m 100 indi_microtouch_focus
Driver indiserver indi_microtouch_focus: pid=1870 rfd=3 wfd=6 efd=7
bind: Address already in use
good bye

Regards

Paul

Another instance of INDI server is running. Stop/kill it first

I don't believe the message is the real issue.

Each time I run indiserver it says address already in use but the pid is different each time.

The is being run on a Raspberry Pi 2 with raspian.

Not sure what the problem is, just tried it here and it starts fine. There is a process that uses port 7624 on your Pi, if not INDI server then find out what.

Hi Paul,

I am not able to reproduce the problem here on raspbian rpi2. What is the output of:

netstat -tulpn | grep :7624

Marco