×

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

Bi-monthly release with minor bug fixes and improvements

Driver OnStep (LX200 like) for INDI

  • Posts: 20
  • Thank you received: 1
as I said I have changed "lx200driver.cpp" source and now every time I am able to connect without any intervention

I just disable checking condition in "check_lx200_connection" function

//if (nbytes_read == 1)

I know I broke the driver mechanism, and is not working properly, but it worked for me now.
may be this will direct you how to fix it properly
regards,
7 years 6 months ago #9847

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

  • Posts: 20
  • Thank you received: 1
Hello Alain,
my hardware setup is as per below;

OnStep (Teensy3.2) <=> FTDI Serial (ttyUSB0) <=> RaspberryPi2 <=> "indiserver indi_lx200_OnStep" <=> WiFi/Eth <=> Kstars on Win7 PC

regards,
7 years 6 months ago #9848

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

  • Posts: 20
  • Thank you received: 1
Alain,
you are so right, this is not happening on ArduinoMega2560
I had a ArduinoMega laying araound, and test showed, original driver is working as expected on ArduinoMega

If you want to buy a Teensy go ahead, because it is worth to have one.
But as I know Teensy 3.5/3.6 is on the way (kickstarter.com)
7 years 6 months ago #9851

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

  • Posts: 153
  • Thank you received: 29
Hi guys,
I think I have found and fixed the "Telescope did not respond to ACK" problem. The root cause is a copy/paste error in the firmware. All responses to the ACK command were being sent to serial port 0. This explains why I was able to connect using serial port 0, but not serial port 1. I have fixed the code and submitted a pull request to Howard. Here are my changes in case anyone is interested:
[ben@zen OnStep]$ git diff --staged
diff --git a/Command.ino b/Command.ino
index 415f7dd..4554ff2 100644
--- a/Command.ino
+++ b/Command.ino
@@ -1262,9 +1262,9 @@ boolean buildCommand_serial_one(char c) {
// (chr)6 is a special status command for the LX200 protocol
if ((c==(char)6) && (bufferPtr_serial_one==0)) {
#ifdef MOUNT_TYPE_ALTAZM
- Serial_print("A");
+ Serial1_print("A");
#else
- Serial_print("P");
+ Serial1_print("P");
#endif
}

Thanks,
Ben
The following user(s) said Thank You: Alain Zwingelstein, Kemal YILDIRIM
7 years 6 months ago #9858

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

  • Posts: 20
  • Thank you received: 1
Hello Ben,
thanks for your update,
this is explaining why I was successfully connecting from Arduino Serial0
but on teensy serial1 was in my setup

Kemal
7 years 6 months ago #9862

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

  • Posts: 452
  • Thank you received: 71
Hi guys,

this is the wonderful world of open source, thinks are not perfect but perfection in on the way :)
The teensy is already ordered so I will be able to run my tests also on this one.

Thanks a lot to you for this step forward.
The following user(s) said Thank You: Ben Gilsrud
7 years 6 months ago #9865

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

  • Posts: 60
  • Thank you received: 1
Hello
I have a problem with OnStepEspServer and indi_lx200_onstep.
My configuration: Arduino Mega 2560 (OnStep), Wemos mini (OnStepESPServer).
It's work fine with Onstep Telescop Control via wifi (Andoid app), ASCOM on Windows (via wifi).
On Linux With OnStep directely connected in USB, works fine too.
But i can't use indi dirver with wifi.
My parameters Connexion network 192.168.0.1 port 9999.
Cannot connect :-(

<OnStep> -> USB -> Indi: OK
<OnStep> -> <OnStepESPServer> -> Wifi -> Indi: NOK (works on ASCOM driver on windows).

Thanks for your job.
6 years 10 months ago #16929

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

  • Posts: 68
  • Thank you received: 2
hello i need your help !

I connect to OnStep via my raspberry 3. In my OnStep I am a teensy 3.2.

When I try to connect:

2017-07-26T03:19:29: Handshake failed.
2017-07-26T03:19:29: Failure. Telescope is not responding to ACK!
2017-07-26T03:19:19: Testing telescope connection using ACK...
2017-07-26T03:19:19: Connection successful, attempting handshake...
2017-07-26T03:19:19: Port FD 3
2017-07-26T03:19:19: Connecting to /dev/arduino


I set the connection name of onstep with you.
6 years 8 months ago #18143

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

  • Posts: 153
  • Thank you received: 29
Are you sure you're using the right serial port? You can use gnu screen or even cat to send simple commands and see onstep respond to them since it's all just ascii.
-Ben
6 years 8 months ago #18149

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

  • Posts: 68
  • Thank you received: 2
Yes. i create 99-usb-seriel.rules with teensy ID and seriel number.
6 years 8 months ago #18153

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

  • Posts: 68
  • Thank you received: 2
Hello !

I tested a lot of different things.

With an arduino Mega card and Onstep no connection problems.
With teensy card, connection problems.

I managed to connect to the teensy only by sending a command via the serial console of the arduino software.
I kept looking. In fact it is necessary to install the file rules of teensy!
sudo cp 49-teensy.rules /etc/udev/rules.d/

www.pjrc.com/teensy/49-teensy.rules
I also install the latest version of arduino and teensyduino to be on.

After that, no problem connecting Arduino Mega and teensy
6 years 7 months ago #18553

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

  • Posts: 155
  • Thank you received: 10
Hello to all OnStep users,

I finally returned to testing my Mega2560 / OnStep project and ran into a couple of errors which I feel are a difference in my Date format vs what OnStep would like. Can any which uses a Mega2560 post their INO? Or possibly a link to the one they use? I will reprogram mine to be like the present driver wants to send.

Thanks in advance for any help,
Dan
6 years 4 months ago #21250
Attachments:

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

Time to create page: 0.874 seconds