×

INDI Library v1.9.7 Released (29 Jul 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

myFocuserPro or myFocuserPro2 and INDI

  • Posts: 77
  • Thank you received: 14
If someone wanted to donate a working device I would be happy to have ago at porting the existing driver.
2 years 8 months ago #46214
The topic has been locked.
  • Posts: 212
  • Thank you received: 26
If the command set is the same for the TCP connection, then it might be easy by changing
setSupportedConnections(CONNECTION_SERIAL) to setSupportedConnections(CONNECTION_SERIAL | CONNECTION_TCP)
That should make it possible to choose in control panel between serial / tcp connection.

And probably a few changes to the sendcommand. (If the driver has been implemented from the skeleton)
Should be easy to emulate by just opening a listener on on the tcp port tho see how the driver sends the command. )

Paul

some update: changed that setSupportedConnections(CONNECTION_SERIAL | CONNECTION_TCP) and recompiled

then on linux used nc to do some tcp traffic on port 1026

nc -l -v 1026

from kstars configured myfocuser2 to ip adress and port 1026

Could see the the driver sending the first command (#03) but then got stuck in sending the answer.

Paul
Last edit: 2 years 8 months ago by PDB.
2 years 8 months ago #46223
The topic has been locked.
  • Posts: 35
  • Thank you received: 3
myFocuserPro2Linux only uses serial as it talks to a serial based focuser. One would not use it to talk to a focuser using TCP/IP.

myFocuserPro2ELinux only uses TCPIP. (E for ESP chips or WiFi). It is now renamed as myFP2ESP-Linux and is posted at sourceforge.
2 years 8 months ago #46243
The topic has been locked.
  • Posts: 35
  • Thank you received: 3
Command set is identical [though there are a few EXTRA commands for ESP info, which one could easily ignore]

By default the esp code uses port 2020 and the ip address will vary depending on the controller mode and if dynamic ip allocation is being used.

You cant do this with a myFocuserPro2 controller - because that only supports serial.

A myFP2ESP controller [different hardware and firmware] supports tcpip/serial/bluetooth/web-server/ascom-remote

Cheers
Robert
2 years 8 months ago #46244
The topic has been locked.
  • Posts: 35
  • Thank you received: 3
Email me: Am happy to donate a board with components, but postage is another thing. If you were willing to contribute with postage then it is possible.
2 years 8 months ago #46245
The topic has been locked.
  • Posts: 29
  • Thank you received: 5
Hi All,

Thanks to Robert and everyone involved with Myfocuserpro and myfocuserpro2.I can confirm the original driver (when modified for WiFi) works for the ESP32.

I followed his suggestion to change from SERIAL to TCP, and changing Firmware version in my clone of the myfocuserpro2 indi driver.

I would have gotten there much sooner but I kept installing the driver's XML file in the wrong place.

My breadboard setup works as expected. I learned so much about drivers and have an appreciation of the effort that goes into all the open source software we have.
2 years 8 months ago #46572
The topic has been locked.
  • Posts: 147
  • Thank you received: 28
Hi all, I have been reading the posts and I have to say excellent work.

I'm building a focuser based on the ESP32 board using the myFP2ESP code (thanks roberto). I want to eliminate another USD cable from my rig.

Just looking at MyFocuserPro2 in the indi control panel (I'm running the latest KStars v3.3.8 ) there is only a serial connection option.

I am wonder if (and if not, when) the TCP method has been pushed for use yet?

regards
Takahashi FC-100DF refractor
ZWO ASI 071 imaging camera
ZWO ASI 224MC on 50mm guidescope
HEQ5 Pro mount
Raspberry Pi 4 running KStars/indi
Last edit: 2 years 8 months ago by Petar Milevski. Reason: spelling
2 years 8 months ago #46720
Attachments:
The topic has been locked.
  • Posts: 35
  • Thank you received: 3
I made a windows controller emulator for the esp controller. If you run this on the windows pc it will start an emulator (and tell you the ip address) - you then can connect to it and it behaves just like a esp controller. I use it all the time for testing, running inside its own VM
2 years 8 months ago #46721
The topic has been locked.
  • Posts: 147
  • Thank you received: 28
Cool. I don't have a windows computer. I only use Ubuntu. Can you send a link to the emulator and I'll try running it with wine.
Takahashi FC-100DF refractor
ZWO ASI 071 imaging camera
ZWO ASI 224MC on 50mm guidescope
HEQ5 Pro mount
Raspberry Pi 4 running KStars/indi
2 years 8 months ago #46722
The topic has been locked.
  • Posts: 35
  • Thank you received: 3
The following user(s) said Thank You: Petar Milevski
2 years 8 months ago #46728
The topic has been locked.
  • Posts: 77
  • Thank you received: 14
If it is as simple as adding TCP_CONNECTION, then I can do this, the problem is I have noway of testing this. So if I do it, could somebody check the new code before I do a pull request?

The problem will then be a lot of people who do not understand the first thing about networking, complaining that the driver does not work, when they have not set their devices correctly!
Last edit: 2 years 8 months ago by Alan Townshend.
2 years 8 months ago #46740
The topic has been locked.
  • Posts: 77
  • Thank you received: 14
Can I suggest we close this thread, as the Serial driver is working as expected, and new issues are put into new threads?
2 years 8 months ago #46741
The topic has been locked.
Time to create page: 0.554 seconds