RPI3 ASI224 only connecting as root

maudy

Any ideas how to get ASI224MC-cooled connecting to indi server when not running as ROOT.

Via my other thread there was mentioned how to get ASI224 running under a user other than root:

"..the 99-asi.rules or asi.rules is located in /lib/udev/rules.d or /etc/udev/rules.d,

only in the case it is located in /etc/udev/rules.d, you can open ASI224 without root."

I moved the rules file: sudo mv /lib/udev/rules.d/99-asi.rules /etc/udev/rules.d/99-asi.rules

Kstars is running as user pi, not root.

Started the indiserver via ekos as mode: local.

ASI 224 will not connect: 2017-03-10T01: Error connecting to the CCD (5)

I am trying to get everything running as a non-root user.

yang

you should replug the camera or reboot your RPI3 after mv the rules to /etc/udev/rules.d

maudy

RPI3 has been rebooted after the moved file. The issue remains with the same error.

Any ideas?

Below is a review of what has been tried. The ASI1600MM-cooled works fine.

Setup is:

1. /etc/udev/rules.d/99-asi.rules

2. Kstars/Ekos running as pi

3. tried remote localhost server as run as pi: /home/pi/indi/indiwebmanager/servermanager/drivermanager.py

4. tried local host server as pi

5. tried running as a service as User pi: sudo systemctl start indiwebmanager.service

Not sure what I am doing wrong, as 3, 4, and 5 only work if running as root.

In case it helps, the ASI EFW does run under User pi using 3 and 5, and but not as 4.

yang

that's strange, what's the content of your 99-asi.rules?

maudy

The rules file is attached in the zip. It is the version that comes with Kstars for Ubuntu-mate.

There is an ASI1600mm-c v3, ASI224MC-c and ASI EFW all connected to the the same RPI3.

The RPI3 is connected to the ASI1600, and then the EFW and 224 is connected to to the ASI1600 USB.

Thank you for checking.

yang

the attached rules is normal.

I have just tested on my RPi3 as your setup with INDIGO driver, and find that if there is messy code in camera name, like

'ZWO ASI224MC-Cool(??????Y) #0' attached.

02.981827 indigo_server: indigo_ccd_asi: 'ZWO ASI224MC-Cool(??????Y) Guider #0' attached.

then it can't be connected in INDIGO driver, is this case the same as you?

maudy

The log, if it is the correct one, shows:

2017-03-29T19 ZWO CCD ASI224MC-Cool is online.

2017-03-29T19 Guider port from Telescope Simulator is ready.

2017-03-29T19 Telescope Simulator is online.

maudy

In case it helps, here is some additional information:

2017-03-31T00: World Coordinate System is enabled. CCD rotation must be set either manually or by solving the image before proceeding to capture any frames, otherwise the WCS information may be invalid.

2017-03-31T00: Setting frame buffer size to 1272704 bytes.

2017-03-31T00: UpdateCCDFrame ASISetROIFormat (1304x976, bin 1, type 0)

2017-03-31T00: ISNewSwitch->SetControlValue 6 40.00

2017-03-31T00: ISNewSwitch->SetControlValue 4 95.00

2017-03-31T00: ISNewSwitch->SetControlValue 3 52.00

2017-03-31T00: ISNewSwitch->SetControlValue 0 350.00

2017-03-31T00: ISNewNumber->set ctrl 2: 50.00

2017-03-31T00: ISNewNumber->set ctrl 0: 350.00

2017-03-31T00: setupParams ASISetROIFormat (1304x976, bin 1, type 0)

2017-03-31T00: The CCD Temperature is 0.000000

2017-03-31T00: Supported Video Format: ASI_IMG_RAW16

2017-03-31T00: Supported Video Format: ASI_IMG_Y8

2017-03-31T00: Supported Video Format: ASI_IMG_RGB24

2017-03-31T00: Supported Video Format: ASI_IMG_RAW8

2017-03-31T00: CCD ID: 0 Width: 1304 Height: 976 Binning: 1x1 Image Type: 0

2017-03-31T00: setupParams->set USB 40

2017-03-31T00: Control #18: name (Cooler on), Descp (turn on/off cooler(cool camera only)), Min (0), Max (1), Default Value (0), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Control #17: name (TargetTemp), Descp (Target temperature(cool camera only)), Min (-40), Max (30), Default Value (0), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Control #16: name (CoolPowerPerc), Descp (Cooler power percent), Min (0), Max (100), Default Value (0), IsAutoSupported (False), isWritale (False)

2017-03-31T00: Control #15: name (Temperature), Descp (Sensor temperature(degrees Celsius)), Min (-500), Max (1000), Default Value (20), IsAutoSupported (False), isWritale (False)

2017-03-31T00: Adding above control as writable control number 14

2017-03-31T00: Control #14: name (Mono bin), Descp (bin R G G B to one pixel for color camera, color will loss), Min (0), Max (1), Default Value (0), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Adding above control as writable control number 13

2017-03-31T00: Control #13: name (HighSpeedMode), Descp (Is high speed mode->No 1->Yes), Min (0), Max (1), Default Value (0), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Adding above control as writable control number 12

2017-03-31T00: Control #12: name (HardwareBin), Descp (Is hardware bin2->No 1->Yes), Min (0), Max (1), Default Value (0), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Adding above control as writable control number 11

2017-03-31T00: Control #11: name (AutoExpMaxBrightness), Descp (Auto exposure maximum brightness value), Min (50), Max (160), Default Value (100), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Adding above control as writable control number 10

2017-03-31T00: Control #10: name (AutoExpMaxExpMS), Descp (Auto exposure maximum exposure value(unit ms)), Min (1), Max (60000), Default Value (100), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Adding above control as writable control number 9

2017-03-31T00: Control #9: name (AutoExpMaxExp), Descp (Auto exposure maximum exposure value(unit second)), Min (1), Max (60), Default Value (30), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Adding above control as writable control number 8

2017-03-31T00: Control #8: name (AutoExpMaxGain), Descp (Auto exposure maximum gain value), Min (0), Max (600), Default Value (300), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Adding above control as writable control number 7

2017-03-31T00: Control #7: name (Flip), Descp (Flip: 0->None 1->Horiz 2->Vert 3->Both), Min (0), Max (3), Default Value (0), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Adding above control as auto control number 4

2017-03-31T00: Adding above control as writable control number 6

2017-03-31T00: createControls->set USB 40

2017-03-31T00: Control #6: name (BandWidth), Descp (USB bandwidth percentage), Min (40), Max (100), Default Value (50), IsAutoSupported (True), isWritale (True)

2017-03-31T00: Adding above control as writable control number 5

2017-03-31T00: Control #5: name (Brightness), Descp (Brightness(offset)), Min (0), Max (240), Default Value (1), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Adding above control as auto control number 3

2017-03-31T00: Adding above control as writable control number 4

2017-03-31T00: Control #4: name (WB_B), Descp (White balance: Blue component), Min (1), Max (99), Default Value (95), IsAutoSupported (True), isWritale (True)

2017-03-31T00: Adding above control as auto control number 2

2017-03-31T00: Adding above control as writable control number 3

2017-03-31T00: Control #3: name (WB_R), Descp (White balance: Red component), Min (1), Max (99), Default Value (52), IsAutoSupported (True), isWritale (True)

2017-03-31T00: Adding above control as writable control number 2

2017-03-31T00: Control #2: name (Gamma), Descp (Gamma), Min (1), Max (100), Default Value (50), IsAutoSupported (False), isWritale (True)

2017-03-31T00: Control #1: name (Exposure), Descp (Exposure Time(us)), Min (32), Max (2000000000), Default Value (10000), IsAutoSupported (True), isWritale (True)

2017-03-31T00: Adding above control as auto control number 1

2017-03-31T00: Adding above control as writable control number 1

2017-03-31T00: Control #0: name (Gain), Descp (Gain), Min (0), Max (600), Default Value (200), IsAutoSupported (True), isWritale (True)

2017-03-31T00: CCD is online. Retrieving basic data.

2017-03-31T00: Setting intital bandwidth to AUTO on connection.

2017-03-31T00: Attempting to open ZWO CCD ASI224MC-Cool...

yang

your camera name is correct. I tried to reproduce your problem, I connect 1600 to RPi3 and connect 224 to 1600's hub, install INDI driver on my RPi3 as http://www.indilib.org/download/raspberry-pi.html, and connect 224 via Kstar/EKOS on a x86 ubuntu, but all work normally, did I miss something?

maudy

yang wrote:
your camera name is correct. I tried to reproduce your problem, I connect 1600 to RPi3 and connect 224 to 1600's hub, install INDI driver on my RPi3 as http://www.indilib.org/download/raspberry-pi.html, and connect 224 via Kstar/EKOS on a x86 ubuntu, but all work normally, did I miss something?

This is the tutorial i followed. There are some differences: http://www.indilib.org/support/tutorials/169-ekos-on-raspberry-pi-complete-guide.html

Perhaps this is where the difference is.

Also, not sure if it makes a difference, the RPI3 uses a USB3 cable (RPI3 is USB2 only) to connect to ASI1600, and then a USB 2 cable connect the ASI224 to the ASI1600 and a USB2 cable to connect the ASI EFW to the ASI1600.

yang

USB3.0 or USB2.0 cable doesn't affect

maudy

Does following the other tutorial change things, such as its use of ubuntu-mate instead?

kcobby

Maybe check that the non-Root user has access to the directories where you installed the Indi download. Sudo chown the user

kcobby

maudy wrote:
Does following the other tutorial change things, such as its use of ubuntu-mate instead?

Installing Ubuntu Mate on the Raspberry Pi allows you to install the full indi library and kstars / ekos bleeding via the ppa. Consequentially you can then sudo apt-get update and be assured of using the latest versions. You can also run Ubuntu Mate headless so the graphical GUI is not loaded when the Raspberry Pi starts up.

maudy

kcobby wrote:
maudy wrote:Does following the other tutorial change things, such as its use of ubuntu-mate instead?

Installing Ubuntu Mate on the Raspberry Pi allows you to install the full indi library and kstars / ekos bleeding via the ppa. Consequentially you can then sudo apt-get update and be assured of using the latest versions. You can also run Ubuntu Mate headless so the graphical GUI is not loaded when the Raspberry Pi starts up.

This is exactly why Ubuntu-mate is used.

The issue is that ASI1600 works fine whether indi_server is run locally or via indi web server, as well as either root or user (pi in this case).

The EFW and ASI224MM-cooled are connected to the ASI1600 USB hub.

When the indi_server is run as root, no issues. When the INDI server is run as pi then the connection errors occur. Moving the 99-asi.rules from lib to etc and reboot has been tried in an attempt to resolve this, and it has not.

For me it is stuck. Recreation of the Ubuntu-mate on SD card was attempted once already. It is not clear what I have a miss.

kcobby

Is the pi@ user included in the appropriate groups?

Dialout and plugdev are the important ones I think.

maudy

Yes, I believe so:

pi adm dialout cdrom sudo dip video plugdev input lpadmin sambashare spi i2c gpio

Not sure if it matter, updating RPI3's INDI from PPA, always puts the 99-asi.rules and the 99-efw.rules in the /lib/udev/rules.

Oddly, ASI1600MM-c always behaves nicely. It is only the ASI224mc-c and ASI EFW that seem to require the indiserver to be root.

Even when just connecting ASI224mm-c to RPI3 directly, it requires root.

maudy

Any ideas why root is required?

INDIserver best practises indicate not to run as root.

Even using this image, it is easy to reproduce: http://indilib.org/forum/general/2183-astroberry-server.html

To confirm is it not a wiring issues - USB2.0 from RPI3->ASI1600MM-c, then using ASI1600MM-c hub two USB2.0 wires to each of ASIEFW and ASI224mc-c

it would be great to get this resolved!

Thank you

maudy

Were you able to reproduce the issue?

The issue is easily reproducable using ASI1600mm-c, ASI224mc-c, and ASIEFW on the RPI3 with ubuntu mate. You can use this image https://github.com/rkaczorek/astroberry-server/ to test.

The connections are typical: connect ASI1600mm-c directly to the RPI3, and then both the ASI224mc-c and ASIEFW are each connected directly to the ASI1600 hub.

Whether starting indiserver via command line, or via indiWebserver, the only way to get all three working is via root user, which is not preferred or recommended.

To use indiwebserver you will need to edit this file /etc/systemd/system/indiwebmanager.service, and change the astroberry user to root.

Please help correct this. The udev rules were confirmed, and there does not seem to be any options.

yang

I can't reproduce your problem, I copy the rules to /etc/udev/rules.d/, it works normally on my RPi3.