×

INDI Library v1.7.8 Released (11 May 2019)

Mid year release of INDI Library v1.7.8 comes with a few drivers and improvements to to existing drivers.

Takahashi Temma 2 users

  • Posts: 11
  • Thank you received: 2

Takahashi Temma 2 users was created by Gene

Hi Guys,

Is there anyone using indi / Kstars / Ekos with a Takahashi Temma 2 mount out there? I'm struggling with getting my NJP synchronized. After I polar align the mount on polaris, I start up indi/Kstars and point my telescope to a bright star like Vega. Since I'm doing this in the late summer / early fall, Vega is on the west side of the meridian. When I do this, two strange things can happen. Either is synchronizes on Vega and when I ask the mount to go to a nearby star like Deneb, it goes in the opposite direction. The other thing that can happen is that I synchronize on Vega and I lose the crosshairs. At first I couldn't figure out what is going on, but then later found that they were on the pointed 180 degrees off. i.e., under the horizon in the green zone in Kstars.

Is there anyone else out there using a Takahashi mount with the Temma 2 controller running into the same problem? I've been struggling with this issue since late September and it still doesn't work. I don't know if I'm doing something wrong. However, before I tried using indi/Kstars/Ekos, I was using Cartes du Ciel with the ASCOM driver for my Takahashi mount and followed the same synchronizaiton/initialization procedure and it worked just fine. I just had to tell the ASCOM driver which side (East or West) the OTA was on when I synchronized on the star that I chose.

Thanks,
-Gene
1 year 6 months ago #21363

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

  • Posts: 8
  • Thank you received: 0

Replied by Pepcm on topic Takahashi Temma 2 users

Hi Gene,
did you solved that error syncing?
I've the same trouble. I figure it can be something related to time configuration but i can't solve it....
Thank you
1 week 6 days ago #39807

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

  • Posts: 11
  • Thank you received: 2

Replied by Gene on topic Takahashi Temma 2 users

Hi Pepcm,

I actually think I did, and it took a while for me to figure it out. I don't think the problem is with the drivers but with the RPi3. The problem is that it doesn't have a battery to keep its memory. What would happen is that the server (RPi3), had a different time than the client (my PC running Kstars/Ekos). My client has the right time, but the pi didn't. The important thing here is that this only happens when I have the RPi3 configured as a hotspot and not via a network connection. If the RPi3 connects to the internet, it updates its clock and everything works fine. However, I find out that if I leave it in hotspot mode, it keeps its last time setting before it is shut down. For example, in my case, if I had the RPI connected to the internet and didn't use it for a month, and hooked it back up in hotspot mode, that's when I ran into trouble. The Temma driver under indi is a month behind and doesn't synchronize to Kstars/Ekos. The symptoms that I see is that it will not point to an object that is low in the East because it thinks it hasn't risen yet or it will go off in some other direction if the object I'm looking for has flipped the meridian.

The way that I found this was through the "date" command. If I typed it I would find that the RPI3 thinks it's a month or so behind the actual date. You can correct this through setting the date using the "date -s " command. (e.g. if you want to set the date to September 3rd at 13:00 hrs. you type: date -s "03 SEP 2016 13:00:00"). The only problem with this is that for some reason, this really messes up the indiwebmanager service and it screws everything up. I particularly find the indiwebmanager very unreliable and do not use it. Since I need a command window to shut down the RIP3 any way, I don't bother with it and just start my INDI drivers manually or through an alias which stars them for me. I find this to be much more reliable than the indi web manager.

In any event, the way that I have fixed this is to either briefly connect the RPI to the internet from time to time so that it updates its clock automatically and then put it back into hotspot mode, or just use the date -s command. Once I do this, the mount points just fine. There may be a better solution out there, but this one works without fail so that's what I'm using. If there are more experienced users who read this message, they may chime in with a better solution, and that would be great if they did.

I think I once heard that the RPI3 should get it's time synced properly once it connects to the client, but this doesn't happen in my case. If in your case, you are using your RPI3 connected to the internet and verified that it has the right date and your mount still won't point properly, then that's a different problem which would be new to me. In all of this for me though, I think the Temma 2 drivers are working properly. It's just that it took a while for me to figure out that it might not be a driver problem but a problem with the RPI3 itself which it was. I'm not a computer person, so it took a long time for me to figure this out and my wife helped me as well since she is pretty savvy with Linux.

The other thing is that one might ask why I use the RPI3 in hotspot mode and just use the internet. Yes, I can do that from home, but if I take my setup in the field where I won't have internet, I don't want to be fumbling with the settings to get everything to work in the field. If I just leave it in hotspot mode, everything will work when I turn it on.

Sorry if I carried on a bit much here, but this was a long process to finally figure out what was going on. Now, the setup works very reliably. Perhaps there is a way for the RPI3 to get the current time when it communicates with the client which would be great. Maybe someone who knows how all of this stuff works a lot better than I do can offer a better solution.

Clear skies,
-Gene
The following user(s) said Thank You: knro, Pepcm
1 week 4 days ago #39869

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

  • Posts: 8
  • Thank you received: 0

Replied by Pepcm on topic Takahashi Temma 2 users

Hi Gene,
thank you for your reply.
I'm almost sure that my problem does not come from time unsincronitzation between server and client. My scope is attached permanently to a pier and the raspberry that hosts the server is connected to my local wifi network. I've tried to put all the computers to UTC with zero offset and i still have problems. I think that there must be something in the telescope controller with bad data. I'm going to try to reset it and reinstall ubuntu and indi on the raspberry.
I hope to share a final solution to all of this soon,
thank you again.
1 week 2 days ago #39968

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

Replied by knro on topic Takahashi Temma 2 users

Gene wrote: Hi Pepcm,

I actually think I did, and it took a while for me to figure it out. I don't think the problem is with the drivers but with the RPi3. The problem is that it doesn't have a battery to keep its memory. What would happen is that the server (RPi3), had a different time than the client (my PC running Kstars/Ekos). My client has the right time, but the pi didn't. The important thing here is that this only happens when I have the RPi3 configured as a hotspot and not via a network connection. If the RPi3 connects to the internet, it updates its clock and everything works fine. However, I find out that if I leave it in hotspot mode, it keeps its last time setting before it is shut down. For example, in my case, if I had the RPI connected to the internet and didn't use it for a month, and hooked it back up in hotspot mode, that's when I ran into trouble. The Temma driver under indi is a month behind and doesn't synchronize to Kstars/Ekos. The symptoms that I see is that it will not point to an object that is low in the East because it thinks it hasn't risen yet or it will go off in some other direction if the object I'm looking for has flipped the meridian.

The way that I found this was through the "date" command. If I typed it I would find that the RPI3 thinks it's a month or so behind the actual date. You can correct this through setting the date using the "date -s " command. (e.g. if you want to set the date to September 3rd at 13:00 hrs. you type: date -s "03 SEP 2016 13:00:00"). The only problem with this is that for some reason, this really messes up the indiwebmanager service and it screws everything up. I particularly find the indiwebmanager very unreliable and do not use it. Since I need a command window to shut down the RIP3 any way, I don't bother with it and just start my INDI drivers manually or through an alias which stars them for me. I find this to be much more reliable than the indi web manager.

In any event, the way that I have fixed this is to either briefly connect the RPI to the internet from time to time so that it updates its clock automatically and then put it back into hotspot mode, or just use the date -s command. Once I do this, the mount points just fine. There may be a better solution out there, but this one works without fail so that's what I'm using. If there are more experienced users who read this message, they may chime in with a better solution, and that would be great if they did.

I think I once heard that the RPI3 should get it's time synced properly once it connects to the client, but this doesn't happen in my case. If in your case, you are using your RPI3 connected to the internet and verified that it has the right date and your mount still won't point properly, then that's a different problem which would be new to me. In all of this for me though, I think the Temma 2 drivers are working properly. It's just that it took a while for me to figure out that it might not be a driver problem but a problem with the RPI3 itself which it was. I'm not a computer person, so it took a long time for me to figure this out and my wife helped me as well since she is pretty savvy with Linux.

The other thing is that one might ask why I use the RPI3 in hotspot mode and just use the internet. Yes, I can do that from home, but if I take my setup in the field where I won't have internet, I don't want to be fumbling with the settings to get everything to work in the field. If I just leave it in hotspot mode, everything will work when I turn it on.

Sorry if I carried on a bit much here, but this was a long process to finally figure out what was going on. Now, the setup works very reliably. Perhaps there is a way for the RPI3 to get the current time when it communicates with the client which would be great. Maybe someone who knows how all of this stuff works a lot better than I do can offer a better solution.

Clear skies,
-Gene


This was one the reason I opted to include DS3231 with StellarMate by default since keeping time is critical. Why don't you install one to your RPI3 and save some headache? They're pretty cheap and not so difficult to set up.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 week 2 days ago #39972

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

  • Posts: 8
  • Thank you received: 0

Replied by Pepcm on topic Takahashi Temma 2 users

Jasem, thanks for your answer.
Your words have make me ask about whats the relation between mount - RPI (indiserver) - kstars (indiclient).
If i'm not wrong, with the option "kstars updates the mount", the server (RPI) sends its time and date to the mount, but it is the client (Kstars in the laptop) who sends coordinates and can sync the position of the mount based on an object in the kstars map. So there are 3 actors in this game.
Thank you
Pep
4 days 1 hour ago #40128

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

  • Posts: 69
  • Thank you received: 12

Replied by giorgio_ne on topic Takahashi Temma 2 users

Hi Jasem, I use Stellarmate on my own Pi. Can I just connect a DS3231 and startup the Pi? Or do I also need any software configuration in Stellarmate?
4 days 18 minutes ago #40131

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

Time to create page: 0.512 seconds