×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

How Update Kstars on Astroberry RPi4

  • Posts: 326
  • Thank you received: 50
Not since the one which seemed to ‘fix’ the issue that I referred to in the post. After that the RPi was never connected to the internet and was always used in HotSpot mode.
3 years 7 months ago #58885

Please Log in or Create an account to join the conversation.

  • Posts: 326
  • Thank you received: 50
So I tried putting an old microSD card last used in March into the RPi in place of the 'mostly working' SSD. lsusb didn't recognise the FTDI device from the Pegasus PPB either and there were the usual hystrionics where neither the Sky-Watcher EQMOD mount nor the PPB were present in Ekos/Indi. So I replaced the SSD and was preparing for just working with the PPB disconnected from the USB hub since I only use this to monitor the temperature and humidity during a capture run - dew heater control is preset to be automatic in any case. However on switch on I ran lsusb and there was the FTDI device along with all the others. A subsequernt check and all devices were connected and working in Ekos/Indi. So in the meantime the only thing I had done was to remove the USB cable from the PPB to the hub and ultimately plugged it back in and all was working again. Here is the lsusb device list:
astroberry@astroberry:~ $ lsusb
Bus 002 Device 003: ID 0781:558c SanDisk Corp.
Bus 002 Device 005: ID 03c3:533f
Bus 002 Device 004: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 008: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 009: ID 03c3:120e
Bus 001 Device 007: ID 04b4:6572 Cypress Semiconductor Corp.
Bus 001 Device 006: ID 04d8:fac2 Microchip Technology, Inc.
Bus 001 Device 004: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
3 years 7 months ago #58914

Please Log in or Create an account to join the conversation.

  • Posts: 67
  • Thank you received: 0
I downloaded AstroBerry 2.0.0 a couple of weeks ago and I just did sudo apt update and sudo apt upgrade.

My version of KStars shows 3.4.3, which successfully upgraded from 3.4.2.

However, I have seen references to version 3.5.0 here.

Should I be able to download/update to that version?
3 years 7 months ago #58986

Please Log in or Create an account to join the conversation.

  • Posts: 348
  • Thank you received: 69

Version 3.5.0 is the testing version that you get on the Kstars nightly train, once it is released as stable you will then shortly find it available on the Astroberry repo.

If you want to go into the testing mode, on astroberry, then you will probably have to compile the program from source.
Last edit: 3 years 7 months ago by Giles. Reason: mistake
3 years 7 months ago #58987

Please Log in or Create an account to join the conversation.

  • Posts: 67
  • Thank you received: 0

OK. Thanks.
Do you know if it will include the new SVBONY SV305 driver that was released 2 days ago?

www.indilib.org/forum/wish-list/6373-ind...meras.html?start=120

(see last post)

BTW system reports AstroBerry version 2.0.3.
Last edit: 3 years 7 months ago by Doug MacGregor.
3 years 7 months ago #58988

Please Log in or Create an account to join the conversation.

  • Posts: 348
  • Thank you received: 69
That will be included when the INDI drivers are updated, which is separate from the kstars package.

If that driver was included with 1.8.6 of the indi drivers then it is either already there, or will be there in the next release of INDI on Astroberry.

Just note, compiling kstars 3.5.0 will not update your indi package, that's something else, but the INDI package takes less time to manually compile than kstars will, you can check the "Get Indi" --> Source for more details.
3 years 7 months ago #58989

Please Log in or Create an account to join the conversation.

  • Posts: 67
  • Thank you received: 0
Thanks.
I don't see it listed in the details of 1.8.6 so it will probably be at least 1.8.7 before it is included.

I tried compiling my own driver but since I am new to this I was unsuccessful. I can wait.
Camera works fine on my Win7 laptop and Win10 Desktop.

My RPi 4B controls my Celestron NexStar GoTo mount and am planning on having it control my camera as well.
Last edit: 3 years 7 months ago by Doug MacGregor.
3 years 7 months ago #58990

Please Log in or Create an account to join the conversation.

  • Posts: 348
  • Thank you received: 69
Radek, who maintains Astroberry, will see this and be able to advise.

In my experience, he keeps to the stable versions, and holds back the releases after the kstars/indi main release for a week or so after the mainstream releases, this, in my opinion, is prudent, but I'm sure he's also quite a busy person.
The following user(s) said Thank You: Doug MacGregor
3 years 7 months ago #58991

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375
SVBONY SV305 is included in the latest INDI update to 1.8.6
3 years 6 months ago #59158

Please Log in or Create an account to join the conversation.

  • Posts: 67
  • Thank you received: 0

I don't see it listed at the top of the page in the list of additions/changes.

Thanks
3 years 6 months ago #59168

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

As an AstroBerry user, I checked KSTARS under Device Manager. I see svBony as a CCD option. With the svBony device attached and Device Manager on svBony, start the service. If the device is recognized, then 1.8.6 does have this device. If not, then a simple LSUSB command should identify the device. Next, a rule may need to be tweaked to get INDI to see the device. Sometimes, 1 digit off is enough for a rule to fail. “*” are useful for any digit provided all load sequences are the same.

I have to use two sets of rules for my QHYCCD devices. When plugged in, the product is one number. When the firmware is loaded, the product number changes. Reboots are when the trouble starts.
3 years 6 months ago #59191

Please Log in or Create an account to join the conversation.

  • Posts: 67
  • Thank you received: 0
That driver is for the SV103 & SV205 cameras.
A new driver was being written for the SV305.
The existing SVBONY driver does not work for the SV305.
The current information I have is that the driver work is finished and is waiting to be included in the PPA and OS's such as StellarMate and Astroberry, both of which use KStars/Ekos.

Check the last few posts in this thread...

www.indilib.org/forum/wish-list/6373-ind...meras.html?start=120

When Kaczorek made the statement that 1.8.6 included a driver for the SV305 I was confused because it doesn't appear in the list of additions/changes listed for 1.8.6.

lsusb shows the device but not the name/manufacturer. That is another issue entirely and does not affect the driver.
3 years 6 months ago #59192

Please Log in or Create an account to join the conversation.

Moderators: Radek Kaczorek
Time to create page: 0.922 seconds