Did you reboot the RPI or did you execute
$ sudo udevadm control --reload-rules
before testing?

Hello,
Yes I reboot the RPI after i did the update.
As it does not makes a change, I execute your command line ($ sudo udevadm control --reload-rules) : same as before : the EFW not recognized
Here is the Ekos log :
******
2016-11-19T10:39:07 Unable to establish:
+ ASI Wheel
Please ensure the device is connected and powered on.
******
Here is what terminal retrurns when I lauch the indi server
******
bregou@bregou-desktop:~$ sudo indiserver -v indi_asi_wheel indi_atik_ccd
2016-11-19T09:33:04: startup: indiserver -v indi_asi_wheel indi_atik_ccd
2016-11-19T09:33:04: Driver indi_asi_wheel: pid=3108 rfd=3 wfd=6 efd=7
2016-11-19T09:33:04: Driver indi_atik_ccd: pid=3109 rfd=4 wfd=9 efd=10
2016-11-19T09:33:04: listening to port 7624 on fd 5
2016-11-19T09:33:05: Driver indi_atik_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-11-19T09:33:05: Driver indi_atik_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-11-19T09:33:05: Driver indi_atik_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-11-19T09:33:05: Driver indi_atik_ccd: snooping on CCD Simulator.FILTER_NAME
2016-11-19T09:33:18: Client 0: new arrival from 127.0.0.1:50048 - welcome!
2016-11-19T09:33:38: Driver indi_atik_ccd: snooping on EFW.FILTER_SLOT
2016-11-19T09:33:38: Driver indi_atik_ccd: snooping on EFW.FILTER_NAME
2016-11-19T09:37:38: Client 0: read EOF
2016-11-19T09:37:38: Client 0: shut down complete - bye!
******
And here is the end of /lib/udev/rules.d/99-asi.rules file (the end of CAMERAS section and the FILTER WHEELS section).
******
ATTR{product}=="ASI290MM-Cool" ATTR{idVendor}=="03c3" ATTR{idProduct}=="290d" GROUP="users", MODE="0666"

# FILTER WHEELS
KERNEL=="hidraw*", ATTRS{idVendor}=="03c3", ATTRS{idProduct}=="1f01", GROUP="users", MODE="0666"
******
Hope that help you
David

Hi
Do you have udev installed and running?
Try this:
$ apt-cache policy udev
udev:
Installed: 229-4ubuntu12
Candidate: 229-4ubuntu12

---

if not installed - install it:
$sudo apt-get install udev

if installed check if started:
$ sudo service --status-all | grep udev
[ + ] udev

if shows [ - ] do:
sudo service udev start

if it doesn’t work after this... maybe someone else may be able to help
Here is where my ideas are over...

Rumen

Hello Rumen,
I have checked all you talk about.
Everything was ok :
udev alredy installed and runing on my RPI.
Here is what the termina command returns.
****
bregou@bregou-desktop:~$ apt-cache policy udev
udev:
Installé : 229-4ubuntu12
Candidat : 229-4ubuntu12
Table de version :
*** 229-4ubuntu12 500
500 ports.ubuntu.com xenial-updates/main armhf Packages
100 /var/lib/dpkg/status
229-4ubuntu10 500
500 ports.ubuntu.com xenial-security/main armhf Packages
229-4ubuntu4 500
500 ports.ubuntu.com xenial/main armhf Packages
****
For some tests I have installed "xenial" maybe that is what makes some issues...

Thanks Rumen
Best regards

I am sorry! I did my best to help!
I ran out of ideas
It works fine here.
What I can say is that It is not a driver issue.
It is a system configuration issue.

Rumen

Dear all.
I had a similar issue and was it solved to edit the rule in /etc/udev/ instead of /lib/udev. Unfortunately both exist in the system I don't know why but it was success for me.
Kind regards
Philippe

Hi All,

I made my own udev rules which also create a symlink with a logical name so that I can check for the presence of this named link to see if the system recognizes the device or not. This may help in determining if the udev rules are applied.

which then looks like this in /dev/

This symlink is not used by the driver, it's just intended for Humans

Hy everybody,
Thank you for all your answers.
Unfortunately i miss time to test what you told about.
I keep you inform when i have done it.

This week end I tested the setup on a laptop runing kubuntu 16.04 and everything is the same : EFW recognize only in server mode (as on the RPI).

Best regards, and once more Thanks a lot
David

Hi,
I puchased a EFW and tested it immediately. It worked right from the beginning without any problems on my Ubuntu LTS 16.04. Cool stuff, thanks a lot!

Best regards,
Klaus

Hello, thanks for this information,
So I don't know what hapened to all of my 3 computers runing kubuntu and ubuntu mate !
Best regards
David

David,
Can you verify that you have your rules in only one of the following locations:

/etc/udev/rules.d/99-sx.rules
/lib/udev/rules.d/99-sx.rules

if in both please remove one of them, probably this one /etc/udev/rules.d/99-sx.rules

if this does not help can you move the file from /lib/... to /etc/...
and verify you have this rule:
KERNEL=="hidraw*", ATTRS{idVendor}=="03c3", ATTRS{idProduct}=="1f01", GROUP="users", MODE="0666"

There is some udev problem, but I have no idea what...

David, please try this and let me know, I am curious
good luck!

Rumen

p.s. Klaus, thanks for the positive report of the driver

Hello Rumen,
I have tested what you talk about.
I had 2 rules files in the folder "/etc/udev/rules.d"
They were :
60-ssd-sheduler.rules
99-meadedsi.rules

I remove them, reboot, lauch kstars and indi in local mode : the same as before : EFW not recognized

I copy/paste all the files from /lib/... to /etc/... reboot lauch kstars, indi in local mode : the same as before : EFW not recognized

Moreover I have the rule you talk about at the end of the 99-asi.rules file.
KERNEL=="hidraw*", ATTRS{idVendor}=="03c3", ATTRS{idProduct}=="1f01", GROUP="users", MODE="0666"

As Klaus have good result using ubuntu, i'll try to install ubuntu and not kubuntu on one of my computer (i have a free hard drive somhere ).
I don't know when i will be able to do it, I miss time.
Next week i go for one week in the professionnal observatory "PIC DU MIDI" in the south of France.
If the sky is clear i will be realy busy I hope il will be so.

Hope those new infos help you Rumen.

Best Regards
David