×

INDI Library v1.9.3 Released (11 Nov 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones. Some highlights:

Problem getting Bluetooth to work with OnStep

  • Posts: 3
  • Thank you received: 0
Hi all

Trust sombody can help me with a problem getting a connection with Bluetooth working with the Onstep mini controller using a Raspberry PI 4 (loaded with the latest Astroberry con fig)

I have tried using the USB connection and yes it does work, but sort of defeats the reason for using the Pi to get rid of cables which I seem to have a problem with all the time

The original set I have, was using Bluetooth to control the mount from my laptop  which worked fine.all be it ascom driven.

At this point in time I have the ASI183 camera ASI120 guide scope and ASIi focuser working. The Bluetooth appears to be working OK see attached screen shots.

it appear to be attached to rfcomm0 all indications is its working OK excerpt when I try to connect it goes yeelow for a few second then goes red 

I have searched through previus error on the site but this has got me beat  oh  yes have changed the LX200 Onstep file to read port rfcomm0 (which did get rid of a reported error port not found even though it was set through the control panel to read rfcomm0 Hi all

Trust sombody can help me with a problem getting a connection with Bluetooth working with the Onstep mini controller using a Raspberry PI 4 (loaded with the latest Astroberry con fig)

I have tried using the USB connection and yes it does work, but sort of defeats the reason for using the Pi to get rid of cables which I seem to have a problem with all the time

The original set I have, was using Bluetooth to control the mount from my laptop  which worked fine.all be it ascom driven.

At this point in time I have the ASI183 camera ASI120 guide scope and ASIi focuser working. The Bluetooth appears to be working OK see attached screen shots.

it appear to be attached to rfcomm0 all indications is its working OK excerpt when I try to connect it goes yeelow for a few second then goes red 

I have searched through previus error on the site but this has got me beat  oh  yes have changed the LX200 Onstep file to read port rfcomm0 (which did get rid of a reported error port not found even though it was set through the control panel to read rfcomm0 
  
 
2 months 4 days ago #76159
Attachments:

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

  • Posts: 3
  • Thank you received: 0
Hi All
Found the issue the indi LX200 onstep it is semi broken!
went to Kstars/ tools /device manager and tried a number of LX200 drivers. I found the LX200astro when fired up connected straight away, so to had the LX200 Onstep ?
Mount would now move to a selected star and repark etc
The only other issue Ekos does not minimise had to drag it smaller to see Kstars the other problem there now seems to be a number of dead mouse arrows on the screen

Trust sombody with greater experiance than me can pin point the problem
1 month 3 weeks ago #76432

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

  • Posts: 148
  • Thank you received: 35
Interesting, I started playing with code with regards to the Handshake (OnStep uses lx200 standard) and found some interesting behaviour at least on OnStep V4 & V3. I'm not sure if since I never touched the handshake that's always been there, or if it's a new thing.

When I first plug it in, it fails for a while, but if closed (Stopping indi and restarting) and reopened it works fine. This also works with the lx200_teamastro driver. This is USB based. I'll look at it more.

If you can, tell me if you have the same behaviour?
1 month 3 weeks ago #76474

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

  • Posts: 3
  • Thank you received: 0
Hi james
I spent a week or so playing with diffrent settings have lost count the number of times I have reloaded astroberry mainly due to diffrent things I have tried

stopping and starting indi made no differance for me the only one that worked was to change the INdi driver ( ndi_lx200autostar) was the one that triggered a connection under the device manager in Kstars. When the connection dialogue screen poped up there was two LX200onstep and Lx200autostar both appeared to be connected and i was able to move the mount.

shutting down the whole system resulted in the same problem as first indicated, blutooth was connected and runnig but would not fire up indi.LX200 onstep so again tried the LX200autostar Bang connected straight away

Haven had a change to look into it further

trust this helps
1 month 3 weeks ago #76475

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

Time to create page: 1.065 seconds