540 replies to this topic

[DavidOrDave]

Try:

 

username: root  or  pi

password: raspberry

[sve]

Is anyone using a robofocus setup? If so, how is it connected? New to this. Any help is appreciated!

Edited by sve, 19 January 2019 - 02:30 PM.

[Mehmetcan9292]

I also have a raspberry pi3 b +. screen freezes on boot. doesn't it have a solution? i want to use iastrohub very much

[DH Lu]

I also have a raspberry pi3 b +. screen freezes on boot. doesn't it have a solution? i want to use iastrohub very much

iAstrohub works well in Pi3B under Raspbian Jessie OS.

However, Raspbian Jessie is not support  Pi 3 B+ due to hardware driver problem.

There are some methods to upgrade drive on Jessie, I tried, it can be work on Pi 3B+, but it was not stable.

So I gave up using iAstrohub on Pi3B+.

Edited by DH Lu, 31 January 2019 - 12:10 AM.

[rserpell]

Hi everyone,

Recently I have been able to play again with iAstrohub after a long pause in my astro-activities. I'm currently using an ASI120mm and an old Tamron 135mm f/2.8 lens to guide a Skywatcher Star Adventurer mount (thus in RA only). The mount carries a Takahashi FS60 at f/6.2 (with the Tak flattener) fitted with a modded Sony NEX-5 camera.

 

Since the only option for remote shooting the NEX-5 is via IR, I have resorted to using the FTDI option of iAstrohub to control it. For this, I'm using an arduino nano to read the FTDI RTS pin level and control an IR emitter accordingly (see the attached diagram). You can see my first semi-successful result here: https://www.astrobin...395540/?nc=user

 

 

Unfortunately, I have found annoying glitches with my setup. After an apparently random number of exposures the shutter would not close after finishing, as if the level on the RTS pin would remain constant. Despite iAstrohub showing that the exposure is over, and even after showing that a new one has started, the arduino doesn't seem to detect any level change. I still have to test this in more detail, but I'd love to hear if someone else is using the FTDI option to control a camera shutter and what your experience has been with it. 

 

I'll post back if I find something myself. In the meantime, thanks to all of you for keeping iAstrohub alive and improving. 

 

Ricardo

Edited by rserpell, 23 March 2019 - 10:31 PM.

[THX59]

Hi everyone,

Recently I have been able to play again with iAstrohub after a long pause in my astro-activities. I'm currently using an ASI120mm and an old Tamron 135mm f/2.8 lens to guide a Skywatcher Star Adventurer mount (thus in RA only). The mount carries a Takahashi FS60 at f/6.2 (with the Tak flattener) fitted with a modded Sony NEX-5 camera.

 

Since the only option for remote shooting the NEX-5 is via IR, I have resorted to using the FTDI option of iAstrohub to control it. For this, I'm using an arduino nano to read the FTDI RTS pin level and control an IR emitter accordingly (see the attached diagram). You can see my first semi-successful result here: https://www.astrobin...395540/?nc=user

 

test.jpg

 

Unfortunately, I have found annoying glitches with my setup. After an apparently random number of exposures the shutter would not close after finishing, as if the level on the RTS pin would remain constant. Despite iAstrohub showing that the exposure is over, and even after showing that a new one has started, the arduino doesn't seem to detect any level change. I still have to test this in more detail, but I'd love to hear if someone else is using the FTDI option to control a camera shutter and what your experience has been with it. 

 

I'll post back if I find something myself. In the meantime, thanks to all of you for keeping iAstrohub alive and improving. 

 

Ricardo

I Ricardo,
In my opinion, you should try to use the Rpi's GPIO pins to control directly your NEX-5 with a wire.
See below the code collected from some bodyelse. I have never try it and I will not be able to help you more.
https://drive.google...jRsAQJqqqY7khwN

Enjoy it !
Richard

Edited by THX59, 24 March 2019 - 01:49 AM.

[ccs_hello]

@ Ricardo

 

Great work!

 

Perhaps using D13 LED to show (from Arduino Nano point of view) the RTS status.

[rserpell]

@css_hello:

Yes, my arduino script already lights the builtin red led when the shutter is open (RTS level low). That is why I know there was not an issue with the arduino script. BTW, this is the Arduino code:

/*
  IR shutter for Sony Nex 5, controlled via FTDI RTS signal on pin 2. Ricardo Serpell 2019
  Uses multiCameraIrControl by Sebastian Setz: https://codebender.cc/library/multiCameraIrControl#multiCameraIrControl.h
  (beware: there is an older -2012- version of multiCameraIrControl that doesn't work with this script)
*/
#include <multiCameraIrControl.h>

Sony Nex5(2);
int RTSpin = A7;
int threshold = 500;
bool oldstate = false;
bool newstate = false;

void setup() {
  // initialize digital pin LED_BUILTIN as an output.
  pinMode(LED_BUILTIN, OUTPUT);
}

void loop() {
  // compare the voltage on RTS pin with predefined threshold and modify state value
  if (analogRead(RTSpin)<threshold) {   
    newstate = true;
  }
  else {
    newstate = false;
  }

  // checks for changes of state and activates shutter
  // in bulb mode, Sony NEX shutter changes of state with each IR command (first signal: open shutter, next signal: close shutter, ...)
  if (newstate!=oldstate) {
    oldstate = newstate;
    Nex5.shutterNow();
    // Show shutter state using builtin led
    if (newstate==true) {
      digitalWrite(LED_BUILTIN, HIGH); 
    }
    else {
      digitalWrite(LED_BUILTIN, LOW);  
    }
  }
  // wait a while for next check, 100 milis
  delay(100);                      
} 

It's not perfect (should have used low and high thresholds instead of a single value), but it works.

 

 

@THX59:

Yes, that would probably be best in the long run, but I wanted to make use of the FTDI functionality that is already "builtin" in iAstrohub. Seemed like a good starting point.

 

Anyway, today my linux-expert-brother and I were able to make great progress. The error messages stored by the operating system showed that the usbserial module was failing, crashing the FTDI module. We decided to apply a brute-force solution. We modified the dslr_usb0 executable to reset both modules at the beginning of every exposure (by removing and restarting them), and also whenever a command to the FTDI resulted in an error. I have had the camera taking pictures all afternoon today without a single error (exposures between 3 and 5 minutes).

 

I'll let you know as soon as I have a chance to test everything under the skies.

 

Till then, clear skies!

Edited by rserpell, 25 March 2019 - 07:12 AM.

[Radiant]

"All three work fine (downloading cr2 file BTW) from ssh reporting current exposure time."

Do you mean if you repeat one of those commands, you keep getting the images without any problem? Do you set 6D at the Bulb mode? If yes, I will send you a patch for 6D.

Or you can edit shutter.sh and change from "eosremoterelease=0" to "eosremoterelease=4" and let me know.

Anat

Hi
I have the same problem with 6D and iAH 3.0.
Could anyone help me to fix it?
Thank you

Edited by Radiant, 01 June 2019 - 04:58 AM.

[cygnushan]

Hi, everyone!

   I have some problem with ZWO ASI120mc on iAstrohub 3.0 for raspberry pi 3B.

   When I enter the Linguider interface, there is en error message "Video input is not initialized", Could anyone help me to fix it?

   error images: https://drive.google...tiR-Hq7pa5mPfLJ

   error images: https://drive.google...Gm1LphQwKeBqH2H

   I'm already update the libasicamera.

   There are some informations from Raspberry Pi 3B:

 

# system info

root@iAstroHub:~# lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 8.0 (jessie)
Release:        8.0
Codename:       jessie

 

# usb seems work well

root@iAstroHub:~# lsusb -v

Bus 001 Device 004: ID 03c3:120b 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x03c3
  idProduct          0x120b
  bcdDevice            0.00
  iManufacturer           1 ZWOptical company 
  iProduct                2 ASI120MC
  iSerial                 3 00000
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 HighSpeed Configuration
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              5 Camera Interface
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0002
  (Bus Powered)
  Remote Wakeup Enabled

 

root@iAstroHub:~# dpkg -l |grep asi
ii  libasicamera                         1.14.0227-0                               armhf        ZWO ASI camera interface library

Edited by cygnushan, 18 July 2019 - 10:12 AM.

[telfish]

Having issues installing this.

 

I downloaded the image and prepared a 16 gb sandisk extreme formatting to fat32. Burned the image with Win32diskimager but it will not boot in my Pi3 b version. No green lights. Tried two different Pc's and several downloads. On verifying I get an error at sector 8139 on several cards so the cards are not at fault. Any ideas. Same pi runs astroberry fine.

[THX59]

Hi,

I recommend an Scandisk Ultra 16 Go.

Regards

[ccs_hello]

Use the download method of:

Google Drive transfer to your own cloud drive folder, then let G.D. sync by itself. (Never direct download...)

[arturpp]

Hi,

 

Did anyone have success with connecting iAstrohub with Meade LXD75 mount, or other using Autostar controller? I am wondering if any kind of USB-serial adapter will be compatible with Lin-Guider

[Astrofilo66]

Hi iAstrobub 3 function for Raspberry Pi 4b?

[blodgar]

Hi,

 

Did anyone have success with connecting iAstrohub with Meade LXD75 mount, or other using Autostar controller? I am wondering if any kind of USB-serial adapter will be compatible with Lin-Guider

I used the Aten USB to serial adapter recommended by Anat with my Pi 2B and Pi 3. It worked successfully.