¿ªÔÆÌåÓý

Date

Re: Alignment (or is it ¡°modeling¡±)

 

After building a model, take a screenshot of the model parameters screen on the HC and post here:
?

On Sun, Nov 3, 2024 at 11:30 AM, Dnorton wrote:
I have the latest firmware and at Level 6. I do a cold start. I tried doing a warm start once after creating a model from a previous session but that was a disaster. So last night I started with a cold start and started from scratch. After completing (but I never got to the ¡°save¡± portion of the model building) the alignment I did a catalog search for M13 and it was more than a FOV off. That¡¯s not going to help when hunting down faint PN in a C11.?

Doug?
?
P.S. I appreciate the help. I was so frustrated last night when I came home. 1980 technology trumping 2024 technology doesn¡¯t seem right.
?


Re: Alignment (or is it ¡°modeling¡±)

 

I have the latest firmware and at Level 6. I do a cold start. I tried doing a warm start once after creating a model from a previous session but that was a disaster. So last night I started with a cold start and started from scratch. After completing (but I never got to the ¡°save¡± portion of the model building) the alignment I did a catalog search for M13 and it was more than a FOV off. That¡¯s not going to help when hunting down faint PN in a C11.?

Doug?
?
P.S. I appreciate the help. I was so frustrated last night when I came home. 1980 technology trumping 2024 technology doesn¡¯t seem right.
?


Re: Alignment (or is it ¡°modeling¡±)

 

?
Thanks for the details. The process seems correct.?
A few more questions:

1. do you start with a Cold start, in CWD position? That¡¯s needed to clear out previous model and settings.
?
2. what mount and Gemini firmware version are you using?
?
3. ?after 3 + 1 stars alignment, how far off are the Goto to another bright star?
?
Regards,
?
? ?-Paul
?
On Sun, Nov 3, 2024 at 08:26 AM, Dnorton wrote:

On the hand controller: I set the time to Universal. Polar align through the polar scope (I know I can do that accurately because whenever I do the PA through ASIair I am within 15'). The Site is set down to the foot. Then I transcribed this list from the YouTube video (below). I follow this and it just keeps going and I never get to the "Save" part. For contrast, I have an older GM8 with encoders. I recently bought a vintage Celestron Advanced Astro Master. I can align on three stars and every object I find in the catalog is dead center. I know the concepts of alignment. Maybe I just don't understand what "building a model" is other than a plastic model airplane.?
?
Four star alignment
Three stars West. One East.
?
Menu
Functions
Modeling
West
?
Goto (1st Star)
Center target
Model
Align
Back
?
Goto (2nd Star)
Center
Model
Align
Back
?
Goto (3rd Star)
Center target
Model
Align
Back
?
East (4th Star)
Goto
Center target
Model
Align
Back
Menu
Align
More
Model
Save


Re: Alignment (or is it ¡°modeling¡±)

 

On the hand controller: I set the time to Universal. Polar align through the polar scope (I know I can do that accurately because whenever I do the PA through ASIair I am within 15'). The Site is set down to the foot. Then I transcribed this list from the YouTube video (below). I follow this and it just keeps going and I never get to the "Save" part. For contrast, I have an older GM8 with encoders. I recently bought a vintage Celestron Advanced Astro Master. I can align on three stars and every object I find in the catalog is dead center. I know the concepts of alignment. Maybe I just don't understand what "building a model" is other than a plastic model airplane.?
?
Four star alignment
Three stars West. One East.
?
Menu
Functions
Modeling
West
?
Goto (1st Star)
Center target
Model
Align
Back
?
Goto (2nd Star)
Center
Model
Align
Back
?
Goto (3rd Star)
Center target
Model
Align
Back
?
East (4th Star)
Goto
Center target
Model
Align
Back
Menu
Align
More
Model
Save


Re: Alignment (or is it ¡°modeling¡±)

 

¿ªÔÆÌåÓý

DNorton,

If you are polar aligned, it is relatively simple, you just select a visible star from the Hand Control catalogue, command the mount to slew to the object, centre it in the eyepiece and then select synchronise.

If you are not so accurately aligned then you do the same as above, but then do one or two further stars spread around the sky and select align instead of synchronise.

You need to make sure that everything is configured correctly before doing anything, date, time, location, type of mount etc.

I rarely do the above because I image and the INDI software takes care of it all.

Paul




On 3 Nov 2024, at 12:07:06 pm, Dnorton <dnorton618@...> wrote:

What a convoluted way to align through the hand controller. Two clear nights wasted because it won¡¯t ¡°model¡±. I¡¯ve followed the YouTube videos and whatever else I can find on how to align. It just goes on and on and on star after star. Does it ever actually finish ¡°modeling¡±? I try to go to a catalog object, an easy one like M13 and it¡¯s off.?

ASIair has no problem when I do astrophotography. It can go all night. But when I want to observe and just poke around the sky¡­?
?
I have the polar scope. I know how to use that. I don¡¯t get it. I just don¡¯t.?


--
Paul


Re: Alignment (or is it ¡°modeling¡±)

 

On Sat, Nov 2, 2024 at 09:21 PM, Dnorton wrote:
What a convoluted way to align through the hand controller. Two clear nights wasted because it won¡¯t ¡°model¡±. I¡¯ve followed the YouTube videos and whatever else I can find on how to align. It just goes on and on and on star after star. Does it ever actually finish ¡°modeling¡±? I try to go to a catalog object, an easy one like M13 and it¡¯s off.?

ASIair has no problem when I do astrophotography. It can go all night. But when I want to observe and just poke around the sky¡­?
?
I have the polar scope. I know how to use that. I don¡¯t get it. I just don¡¯t.?
?
It would help if you could describe how you are building the model. Step by step. Many others are able to build a pointing model that works for them, so there's likely something you're not doing right or something that isn't configured correctly. It's hard to guess what that might be without additional details.
?
Generally 3-4 stars are sufficient to get a decent model on one side, plus add one more star on the other. Add more stars if you want better precision. Here are some pages that may help:
?
?
?


Alignment (or is it ¡°modeling¡±)

 

What a convoluted way to align through the hand controller. Two clear nights wasted because it won¡¯t ¡°model¡±. I¡¯ve followed the YouTube videos and whatever else I can find on how to align. It just goes on and on and on star after star. Does it ever actually finish ¡°modeling¡±? I try to go to a catalog object, an easy one like M13 and it¡¯s off.?

ASIair has no problem when I do astrophotography. It can go all night. But when I want to observe and just poke around the sky¡­?
?
I have the polar scope. I know how to use that. I don¡¯t get it. I just don¡¯t.?


Re: threads

 

Glad? to help, Luca!
--
Sonny Edmonds
GM811G HD


Re: Weird Gemini telescope behavior

 

On Thu, Oct 31, 2024 at 02:45 PM, crocco1250 wrote:
This is for Paul kanevsky.? I have two losmandy mounts,? a 2005 g11 with older servo motors and a g11g SLW,? both with Gemini II mini with L06 and servo motor quadrature upgrades. They both "talk" via a linksys wireless router and LAN cable to on-board mini computers (eagle and mele quieter 4c) to my laptop via remote access (win11). I recently had both fired up and communicating via two different laptops.? Gemini telescope would only work if I used the UDP setting (unverified data packet). If I tried using the HTTP setting for both mini computers (one 192.668.0.220, the other... 221), Gemini telescope couldn't resolve which command went to which mount, i.e., both mounts got the same command.? When I switched to udp,? problem resolved.?
?
Now to the weird part.? So I've left my Gemini telescope on udp on startup.? Last night,? I was getting target unreachable on the handset in the 2005 mount (single mount).? I went out and was able to move the mount to the target (m32 in this case,? with the scope pointing east via the handset). While trying to figure out the problem,? the mount went to limit. So I commanded the mount to CWD. The Gemini telescope slewed to CWD and telescope app showed limit and wouldn't allow me to enter track via my laptop.? I reset both the Gemini II and telescope app but it wouldn't let me go from CWD to track.? I finally set Gemini telescope to HTTP with the handset address (....220) and no more issues!!!? This morning I thought I should have looked at the ARP table but didn't.? Weird behavior.? Your thoughts??
?
Chuck
?
The networking term UDP stands for User Datagram Protocol.? Like many computer terms it is an arcane term made up by dudes in garages wearing pointy hats.? AFAIK UDP packets are verified using checksums but the handshake protocol does not wait for receipts from the receiving device(s).? Because of this it is a faster protocol due to the much lower network overhead but UDP can lose packets if the receiver is not ready to accept data.? IME it is very reliable in use with Gemini controllers as Gemini Ethernet is relatively slow by modern standards.? If you are experiencing dropped packets or data loss once the Gemini is talking to the computer this is not likely the fault of the use of UDP protocol but some other layer in your network.? ?
?
--

Chip Louie Chief Daydreamer Imagination Hardware?

Astrospheric - South Pasadena, CA?


Re: threads

 

Thank you so much!
?
Luca


Re: Weird Gemini telescope behavior

 

Thanks Paul. If I run into this problem again, I'll look up the mac addresses and see if that's the problem. At least I'll know where i can modify the address.

Chuck
On Thursday, October 31, 2024 at 03:50:35 PM PDT, Paul Kanevsky <yh@...> wrote:


?
The MAC address should be different for two devices on the same network. UDP relies on it to deliver datagrams. Heres how to change the MAC address:
?
?
Regards,
?
? -Paul

On Thu, Oct 31, 2024 at 06:35 PM, crocco1250 wrote:
Paul

The 2005 has a mele minicomputer from China with both a Wi-Fi and LAN connection. It could be they are not properly resolving the IP address with Gemini udp with a Wi-Fi and LAN address from my router. I'm not sure if this is a hardware issue (Mele) or udp problem. I'm just putting it out there I had this issue. It can be resolved via HTTP. I'm not sure why!!!

Chuck
On Thursday, October 31, 2024 at 03:15:12 PM PDT, crocco1250 via groups.io <crocco1250@...> wrote:
?
?
Paul

I have no idea how I would change the mac address. I assume this is set by the gemini mini LAN physical layer. I could check the router the next time I have both fired up. As I said, Gemini telescope worked OK with both mounts online and Gemini telescope app in udp mode. But the weird behavior was with the single mount with udp. The other mount was not connected. That's what's I find puzzling. The single mount started working with HTTP not udp.

Chuck
On Thursday, October 31, 2024 at 03:05:22 PM PDT, Paul Kanevsky <yh@...> wrote:
?
?
Chuck, if I understand correctly, you have both Gemini connected via ethernet cable to their own mini computers. Did you change the MAC address of at least one of the Gemini units? With both units having the same default MAC address packet or datagram routing would be unpredictable. UDP is the preferred method of communicating with Gemini. HTTP is there for complicated networks where UDP routing may not be possible. UDP for Gemini is a reliable protocol with error detection and recovery built-in, so it's not the unverified, raw version of a UDP broadcast.
?
Regards,
?
? -Paul
?
On Thu, Oct 31, 2024 at 05:45 PM, crocco1250 wrote:
This is for Paul kanevsky.? I have two losmandy mounts,? a 2005 g11 with older servo motors and a g11g SLW,? both with Gemini II mini with L06 and servo motor quadrature upgrades. They both "talk" via a linksys wireless router and LAN cable to on-board mini computers (eagle and mele quieter 4c) to my laptop via remote access (win11). I recently had both fired up and communicating via two different laptops.? Gemini telescope would only work if I used the UDP setting (unverified data packet). If I tried using the HTTP setting for both mini computers (one 192.668.0.220, the other... 221), Gemini telescope couldn't resolve which command went to which mount, i.e., both mounts got the same command.? When I switched to udp,? problem resolved.?
?
Now to the weird part.? So I've left my Gemini telescope on udp on startup.? Last night,? I was getting target unreachable on the handset in the 2005 mount (single mount).? I went out and was able to move the mount to the target (m32 in this case,? with the scope pointing east via the handset). While trying to figure out the problem,? the mount went to limit. So I commanded the mount to CWD. The Gemini telescope slewed to CWD and telescope app showed limit and wouldn't allow me to enter track via my laptop.? I reset both the Gemini II and telescope app but it wouldn't let me go from CWD to track.? I finally set Gemini telescope to HTTP with the handset address (....220) and no more issues!!!? This morning I thought I should have looked at the ARP table but didn't.? Weird behavior.? Your thoughts??
?
Chuck


Re: Weird Gemini telescope behavior

 

?
The MAC address should be different for two devices on the same network. UDP relies on it to deliver datagrams. Heres how to change the MAC address:
?
?
Regards,
?
? -Paul

On Thu, Oct 31, 2024 at 06:35 PM, crocco1250 wrote:
Paul

The 2005 has a mele minicomputer from China with both a Wi-Fi and LAN connection. It could be they are not properly resolving the IP address with Gemini udp with a Wi-Fi and LAN address from my router. I'm not sure if this is a hardware issue (Mele) or udp problem. I'm just putting it out there I had this issue. It can be resolved via HTTP. I'm not sure why!!!

Chuck
On Thursday, October 31, 2024 at 03:15:12 PM PDT, crocco1250 via groups.io <crocco1250@...> wrote:
?
?
Paul

I have no idea how I would change the mac address. I assume this is set by the gemini mini LAN physical layer. I could check the router the next time I have both fired up. As I said, Gemini telescope worked OK with both mounts online and Gemini telescope app in udp mode. But the weird behavior was with the single mount with udp. The other mount was not connected. That's what's I find puzzling. The single mount started working with HTTP not udp.

Chuck
On Thursday, October 31, 2024 at 03:05:22 PM PDT, Paul Kanevsky <yh@...> wrote:
?
?
Chuck, if I understand correctly, you have both Gemini connected via ethernet cable to their own mini computers. Did you change the MAC address of at least one of the Gemini units? With both units having the same default MAC address packet or datagram routing would be unpredictable. UDP is the preferred method of communicating with Gemini. HTTP is there for complicated networks where UDP routing may not be possible. UDP for Gemini is a reliable protocol with error detection and recovery built-in, so it's not the unverified, raw version of a UDP broadcast.
?
Regards,
?
? -Paul
?
On Thu, Oct 31, 2024 at 05:45 PM, crocco1250 wrote:
This is for Paul kanevsky.? I have two losmandy mounts,? a 2005 g11 with older servo motors and a g11g SLW,? both with Gemini II mini with L06 and servo motor quadrature upgrades. They both "talk" via a linksys wireless router and LAN cable to on-board mini computers (eagle and mele quieter 4c) to my laptop via remote access (win11). I recently had both fired up and communicating via two different laptops.? Gemini telescope would only work if I used the UDP setting (unverified data packet). If I tried using the HTTP setting for both mini computers (one 192.668.0.220, the other... 221), Gemini telescope couldn't resolve which command went to which mount, i.e., both mounts got the same command.? When I switched to udp,? problem resolved.?
?
Now to the weird part.? So I've left my Gemini telescope on udp on startup.? Last night,? I was getting target unreachable on the handset in the 2005 mount (single mount).? I went out and was able to move the mount to the target (m32 in this case,? with the scope pointing east via the handset). While trying to figure out the problem,? the mount went to limit. So I commanded the mount to CWD. The Gemini telescope slewed to CWD and telescope app showed limit and wouldn't allow me to enter track via my laptop.? I reset both the Gemini II and telescope app but it wouldn't let me go from CWD to track.? I finally set Gemini telescope to HTTP with the handset address (....220) and no more issues!!!? This morning I thought I should have looked at the ARP table but didn't.? Weird behavior.? Your thoughts??
?
Chuck


Re: Weird Gemini telescope behavior

 

Paul

The 2005 has a mele minicomputer from China with both a Wi-Fi and LAN connection. It could be they are not properly resolving the IP address with Gemini udp with a Wi-Fi and LAN address from my router. I'm not sure if this is a hardware issue (Mele) or udp problem. I'm just putting it out there I had this issue. It can be resolved via HTTP. I'm not sure why!!!

Chuck
On Thursday, October 31, 2024 at 03:15:12 PM PDT, crocco1250 via groups.io <crocco1250@...> wrote:


Paul

I have no idea how I would change the mac address. I assume this is set by the gemini mini LAN physical layer. I could check the router the next time I have both fired up. As I said, Gemini telescope worked OK with both mounts online and Gemini telescope app in udp mode. But the weird behavior was with the single mount with udp. The other mount was not connected. That's what's I find puzzling. The single mount started working with HTTP not udp.

Chuck
On Thursday, October 31, 2024 at 03:05:22 PM PDT, Paul Kanevsky <yh@...> wrote:


Chuck, if I understand correctly, you have both Gemini connected via ethernet cable to their own mini computers. Did you change the MAC address of at least one of the Gemini units? With both units having the same default MAC address packet or datagram routing would be unpredictable. UDP is the preferred method of communicating with Gemini. HTTP is there for complicated networks where UDP routing may not be possible. UDP for Gemini is a reliable protocol with error detection and recovery built-in, so it's not the unverified, raw version of a UDP broadcast.
?
Regards,
?
? -Paul
?

On Thu, Oct 31, 2024 at 05:45 PM, crocco1250 wrote:
This is for Paul kanevsky.? I have two losmandy mounts,? a 2005 g11 with older servo motors and a g11g SLW,? both with Gemini II mini with L06 and servo motor quadrature upgrades. They both "talk" via a linksys wireless router and LAN cable to on-board mini computers (eagle and mele quieter 4c) to my laptop via remote access (win11). I recently had both fired up and communicating via two different laptops.? Gemini telescope would only work if I used the UDP setting (unverified data packet). If I tried using the HTTP setting for both mini computers (one 192.668.0.220, the other... 221), Gemini telescope couldn't resolve which command went to which mount, i.e., both mounts got the same command.? When I switched to udp,? problem resolved.?
?
Now to the weird part.? So I've left my Gemini telescope on udp on startup.? Last night,? I was getting target unreachable on the handset in the 2005 mount (single mount).? I went out and was able to move the mount to the target (m32 in this case,? with the scope pointing east via the handset). While trying to figure out the problem,? the mount went to limit. So I commanded the mount to CWD. The Gemini telescope slewed to CWD and telescope app showed limit and wouldn't allow me to enter track via my laptop.? I reset both the Gemini II and telescope app but it wouldn't let me go from CWD to track.? I finally set Gemini telescope to HTTP with the handset address (....220) and no more issues!!!? This morning I thought I should have looked at the ARP table but didn't.? Weird behavior.? Your thoughts??
?
Chuck


Re: Weird Gemini telescope behavior

 

Paul

I have no idea how I would change the mac address. I assume this is set by the gemini mini LAN physical layer. I could check the router the next time I have both fired up. As I said, Gemini telescope worked OK with both mounts online and Gemini telescope app in udp mode. But the weird behavior was with the single mount with udp. The other mount was not connected. That's what's I find puzzling. The single mount started working with HTTP not udp.

Chuck
On Thursday, October 31, 2024 at 03:05:22 PM PDT, Paul Kanevsky <yh@...> wrote:


Chuck, if I understand correctly, you have both Gemini connected via ethernet cable to their own mini computers. Did you change the MAC address of at least one of the Gemini units? With both units having the same default MAC address packet or datagram routing would be unpredictable. UDP is the preferred method of communicating with Gemini. HTTP is there for complicated networks where UDP routing may not be possible. UDP for Gemini is a reliable protocol with error detection and recovery built-in, so it's not the unverified, raw version of a UDP broadcast.
?
Regards,
?
? -Paul
?

On Thu, Oct 31, 2024 at 05:45 PM, crocco1250 wrote:
This is for Paul kanevsky.? I have two losmandy mounts,? a 2005 g11 with older servo motors and a g11g SLW,? both with Gemini II mini with L06 and servo motor quadrature upgrades. They both "talk" via a linksys wireless router and LAN cable to on-board mini computers (eagle and mele quieter 4c) to my laptop via remote access (win11). I recently had both fired up and communicating via two different laptops.? Gemini telescope would only work if I used the UDP setting (unverified data packet). If I tried using the HTTP setting for both mini computers (one 192.668.0.220, the other... 221), Gemini telescope couldn't resolve which command went to which mount, i.e., both mounts got the same command.? When I switched to udp,? problem resolved.?
?
Now to the weird part.? So I've left my Gemini telescope on udp on startup.? Last night,? I was getting target unreachable on the handset in the 2005 mount (single mount).? I went out and was able to move the mount to the target (m32 in this case,? with the scope pointing east via the handset). While trying to figure out the problem,? the mount went to limit. So I commanded the mount to CWD. The Gemini telescope slewed to CWD and telescope app showed limit and wouldn't allow me to enter track via my laptop.? I reset both the Gemini II and telescope app but it wouldn't let me go from CWD to track.? I finally set Gemini telescope to HTTP with the handset address (....220) and no more issues!!!? This morning I thought I should have looked at the ARP table but didn't.? Weird behavior.? Your thoughts??
?
Chuck


Re: Weird Gemini telescope behavior

 

Chuck, if I understand correctly, you have both Gemini connected via ethernet cable to their own mini computers. Did you change the MAC address of at least one of the Gemini units? With both units having the same default MAC address packet or datagram routing would be unpredictable. UDP is the preferred method of communicating with Gemini. HTTP is there for complicated networks where UDP routing may not be possible. UDP for Gemini is a reliable protocol with error detection and recovery built-in, so it's not the unverified, raw version of a UDP broadcast.
?
Regards,
?
? -Paul
?
On Thu, Oct 31, 2024 at 05:45 PM, crocco1250 wrote:

This is for Paul kanevsky.? I have two losmandy mounts,? a 2005 g11 with older servo motors and a g11g SLW,? both with Gemini II mini with L06 and servo motor quadrature upgrades. They both "talk" via a linksys wireless router and LAN cable to on-board mini computers (eagle and mele quieter 4c) to my laptop via remote access (win11). I recently had both fired up and communicating via two different laptops.? Gemini telescope would only work if I used the UDP setting (unverified data packet). If I tried using the HTTP setting for both mini computers (one 192.668.0.220, the other... 221), Gemini telescope couldn't resolve which command went to which mount, i.e., both mounts got the same command.? When I switched to udp,? problem resolved.?
?
Now to the weird part.? So I've left my Gemini telescope on udp on startup.? Last night,? I was getting target unreachable on the handset in the 2005 mount (single mount).? I went out and was able to move the mount to the target (m32 in this case,? with the scope pointing east via the handset). While trying to figure out the problem,? the mount went to limit. So I commanded the mount to CWD. The Gemini telescope slewed to CWD and telescope app showed limit and wouldn't allow me to enter track via my laptop.? I reset both the Gemini II and telescope app but it wouldn't let me go from CWD to track.? I finally set Gemini telescope to HTTP with the handset address (....220) and no more issues!!!? This morning I thought I should have looked at the ARP table but didn't.? Weird behavior.? Your thoughts??
?
Chuck


Weird Gemini telescope behavior

 

This is for Paul kanevsky.? I have two losmandy mounts,? a 2005 g11 with older servo motors and a g11g SLW,? both with Gemini II mini with L06 and servo motor quadrature upgrades. They both "talk" via a linksys wireless router and LAN cable to on-board mini computers (eagle and mele quieter 4c) to my laptop via remote access (win11). I recently had both fired up and communicating via two different laptops.? Gemini telescope would only work if I used the UDP setting (unverified data packet). If I tried using the HTTP setting for both mini computers (one 192.668.0.220, the other... 221), Gemini telescope couldn't resolve which command went to which mount, i.e., both mounts got the same command.? When I switched to udp,? problem resolved.?
?
Now to the weird part.? So I've left my Gemini telescope on udp on startup.? Last night,? I was getting target unreachable on the handset in the 2005 mount (single mount).? I went out and was able to move the mount to the target (m32 in this case,? with the scope pointing east via the handset). While trying to figure out the problem,? the mount went to limit. So I commanded the mount to CWD. The Gemini telescope slewed to CWD and telescope app showed limit and wouldn't allow me to enter track via my laptop.? I reset both the Gemini II and telescope app but it wouldn't let me go from CWD to track.? I finally set Gemini telescope to HTTP with the handset address (....220) and no more issues!!!? This morning I thought I should have looked at the ARP table but didn't.? Weird behavior.? Your thoughts??
?
Chuck


Re: threads

 

All Losmandy threads are National Course.
?SAE might fit.
1/4x20TPI, 3/8x16 TPI, 1/2x13TPI, Etc.
?
And No, not Whitworth. Withworth is an old English system. My 1965 BSA motorcycle had Whitworth all over the place. 1/4x26TPI for one PITA I remember.
--
Sonny Edmonds
GM811G HD


threads

 

Hi all,
I've recently purchased a Gemini 2 kit for my Losmandy G11 and I need to know which kind of thread is there on the screws circled in red (picture attached). I'm afraid is Whitworth Thread System.
Thank you in advance,
Luca


Re: Serial to USB connection

 

I use a long USB3 cable to go from my computer out to my? telescope. ? ?The USB cable has a 5V powered signal repeater at the telescope end to provide signal conditioning.? I have a usb hub at the mount to carry imaging camera, guiding camera, and Gemini mount info back to my computer, where I use NINA.? ? No need for ethernet to the Gemini.


Re: Serial to USB connection

 

On Tue, Oct 29, 2024 at 11:08 AM, <stargazr39@...> wrote:
Paul,?
Do I understand correctly that a cable from a USB port on my computer connecting to the USB B input on the G2 will accomplish my goal automatically? I am using an HP computer with a Core10 gen 7 chip and running Windows 10.
Ron Abbott?
Yep. That should work.
?
?