Thank you for your reply Jasem. If memory serves me right I do remember seeing a driver documentation page for the temma driver when I first considered using Indi and I was searching for supported mounts.
I completely re-wrote the temma driver a few months back. Ours is not yet installed in the observatory, but that should come in the near future. Since I have inherited the job of maintaining the temma driver, and I'm using an NJP in the observatory, once ours is in place and set up, I think it's safe to say it'll be as well supported as possible.
I do have some minor issues wit the temma mount, not the least of which is, when we power it up, it starts out tracking, and this is a bit of an issue regarding park positions, the mount wont be in the exact same spot it was when parked after a driver connects, it will have moved by as much a sideral rate changes it between power up and driver connect. I have more thoughts on how to deal with the issue, but, I wont get to that until we have it in the observatory and a telescope mounted. Should only be a few weeks now.
I really appreciate your efforts on the temma driver and I will eagerly follow any update. I have an EM-200 temma 2M, I'm aware that the Ascom temma driver is no longer maintained and I feel edgy on having to rely on the Windows os and its tantrums.
The indi temma driver as it sits in the repositories now works well in my office with the mount in the corner. If you are not in a permanent setup, I'd expect it to 'just work' for the most part. The only issue is regarding the startup sequence and trying to get it to 'wake up' with the correct position due to the issue I mentioned above.
The simple work-around, after it wakes up, the stored park will be 'pretty close', do one slew then solve and sync. From there, it should be correct after the first sync gets the mount back in sync with stars. If the time delay between power up and starting driver is short, that should only be off by a few arcseconds anyways. If you are doing a from scratch setup for each outing, this is more or less a non issue.
The code for the pulse guide stuff is fleshed out in the driver, and appears to work with the test setup in the office. I haven't had it under stars to test, groundwork for the observatory build starts this upcoming weekend, so it shouldn't be to long now.