If you have or can run a cable, something to consider which works well and will be one less usb connection to manage is to use the Mach1's ethernet connection instead.

---

I have both connected. typically no problem with the mount.
seems fine now. But I have some software questions. And slaving issues.
GETTING THERE!

It doesn't seem to know (the dome) where the scope is pointing. I have SNOOP device set to
telescope = astrophysics Experimental ? (is that what I put?) and weather set to AAG Cloud Watcher.

I think at this point, someone team viewing into my machine could do a proper setup at this point.

(Ignore telescope or telescope locks?)

WAIT - uut... just slaved to the scope. I'll keep experimenting.
nope - it slaved from park to perfect spot for scope.
I then moved the scope North... a little 20 deg? and the dome slit went South about 20deg.
I dunno if I should flip EAST/WEST or REVERSE.

NO CLUE - I was trying to tweak settings - the shutter closed and now the rotator and shutter do not repond at all.
I was so excited = (

Mount is giving the old errors again.
how do I lock the ports? Just by turning off search?

mount works again, dome connects but no control. I need to get away from it for a couple days. Close to going back to my SGP/windows setup.

I can't help with the dome. If the "old error messages" are about usb connections you can proably avoid them if you don't use usb for the mount. Check which you using by checking the INDI window shown in screenshot.

There is a 'linux way' to presistant port mapping across reboots and device attachments. There is a description here.
indilib.org/support/tutorials/157-persis...al-port-mapping.html

Read it - it's above my pay grade. = (

WOTALOTA - I took your advice. I have both connected USB and LAN - so I just configured a test equipment setup and changed it to serial and put in IP and port.
The mount connects and works - kinda - the hand control is messed up. See? One less com port is a positive. But something is amiss. !?!?!

Controller has status error. Says it's parked and mount is unparked. ? Pushing the direction buttons does move the mount. Any idea how to get them in sync?
What does WARMING over riding mach1 configuration mean in the log window?

mount settings refuse to accept UTC time?

I do not have a hand controller or understand the relationship of using both the hand controller and the computer to control the mount. I just use Ethernet between the computer and the mount in preference to having a USB connection. You said you had both ethernet and usb connections to the mount, was the ethernet for the computer and the usb for the hand controller? If so then I misunderstood when you seemed to be saying there were problems with the mounts USB connection and you already were using ethernet for the connection.
I am not sure where you are now, what does your indi panel showing which kind of connection you are using between the computer and the mount (similar to the one I attached) look like? Perhaps you can go back to your standard setup and get back to where you were.
Tom

I don't have or like hand controllers either. (the controller in the capture is part of the Ekos control. It's how you can manually move the mount from Kstars/ekos?

I have once again put the PI out there and connected everything. I have better luck. But how do I 'lock" or make a connection static? I saw a aweome utility called serial Serial port assistant. I see the button, but nothing happens.
(I've only seen it work on stellarmate).

Anyway I'm back to the PI and once again I find it (to slow and a bit laggy and crashes if I open a browser too) to much stuff per 1 gig ram? But my snapcap did connect and works. And the mount seems to connect and work.
My nexdome should (does connect) but I have a problem with it - I think I need a new Xbee card in it. (another topic).

I wondered if I use the PI and note all the ports? I might use same posts on the nuc? I don't get it - it says USB0 and USB1 (where is USB2, 3,4, etc? It says no file exsists? (must I create a file?)
Does anyone know - HOW MANY PORTS ARE THERE? do I have to much stuff?

Why can't it search out ports that aren't already in use?

I had USB and LAN both hooked up so I can access either one. I am using LAN with the pi. The PI is connected to the mesh router, the GTO4 is connected to the router, as is my cloud watcher.
I don't get what linux is doing to (usb ports)? IS THERE A LIMIT?

Ron,

Looking over the thread there is a lot going on at the same time.
Not the least using a new operating system. I'd look at this
as a parallel development project while you continue to use Windows
ASCOM to do your imaging. Taking Jasem's advice
simplify and get the mount working reliably first. Then getting
help on the dome. Disconnect everything but what has been working
well for a time to deal with interactions after the indivicual device
is working okay. Just the mount and camera connected might be a place
to start.

There are a few minor issues that I see also, like the controller
being flagged as too old occasionally and the message about
overriding your ekos configuration. Don't know why or what is
being overriden, but does not seem worth pursuing at this time.

If using the ethernet as the mount connection doesn't work out
for some reason then removing the irritation of linux switching
usb connections on you should first be addressed. This will become
more important as additional devices are brought in. One way to
approach it is to disconnect all usb connections from the
PC except for the mount, and gather the information for that one
device.

$ lsusb

Will produce a list of controllers hubs and connected devices.
From the list you posted this appears to be for the mount.

Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

$ ls /dev

With everyting else disconnected, there should be just the
one device for example ttyUSB0. Need to use that information in
the following command.

$ udevadm info -a -n /dev/ttyUSB0 | grep '{serial}' | head -n1

It will produce something like ATTRS{serial}=="A105Q7RY"
Now create a file called 99-observatory.rules using the information
collected to later copy into a privileged location.
The initial contents of the file should look something like this
substituting your own information:

# Mach1 Mount (FTDI FT32 Serial UART)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A105Q7RY", MODE="0666", SYMLINK+="mount"

idVendor, idProduct and serial values were collected above for that
particular usb device. The SYMLINK name is what you want to use instead
of /dev/ttyUSB0

To be effective the file needs to be placed in a directory with root
privileges. I think you are using a ubuntu based operating system so
the sudo command with your normal password should be good.
Check you do not already have that file in the directory.

$ ls -l /lib/udev/rules.d/

Then copy it:
$ sudo cp 99-observatory.rules /lib/udev/rules.d/

To confirm locate the new file and confirm its protection looks
like the others.

$ ls -l /lib/udev/rules.d/

Then a reboot of the computer so that it picks up the new file.

Basically each usb device can be added to the file and given its
own unique name that can be used instead of the usual
/dev/ttyUSB0 name, you enter /dev/mount

I do not have all this setup myself but the above is a based on
what is found in Jasem's document.

I did create a rules file and had to save it in a easy place as it wouldn't let me save it in there. I put in one number as a test. (how does the system find this obsy/rules file I'm creating?

I do tend to jump in head first. Anyway here is where I'm at.

Unplugged the nuc and placed with RBPI. plugged in all my gear. (really cold out there to sit and do ID lookup one by one. But I may need to. (isn't there a easier way? where is this serial port assistant?) I saw it in a stellarmate video? I'd happily buy the SD card if it will give me that functionality in Astroberry? (or is it just better to replace astroberry with stellarmate sd?

So with the PI plugged in - it finds most of my gear more easily? (why?) and with less problems. (Isn't there a way to SAVE a config when it's all working? So that the same ports are always used??!? (I'm use to windows here!)

With the PI - the mount has always connected (does it search for a port each time? or does it keep the working port?) and even got my snapcap working.

HOWEVER - on the downsize - the pi crashes kstars often. I suspect ram limit - if I open or do to much it crashes to the OS. So how get by that? Read on = )

I then proceeded to setup the PI in webserver mode and run Kstars from my desktop in the house. This uses the speed and power of my desktop and limits the PI to being the hardware interface and this works NICELY. No crashes since.

So mainly I've been trying to get familar with the program. Connecting everything, taking shots at the inside of my lens cap... etc. HOWEVER to my surprise I went to use the camera to grab a test shot today and my SNAPCAP opened!

THATS A PROBLEM because my dome doesn't allow enough clearance. It jammed... and I'd like to know where I can shut that off and make the cap only open or closed WHEN I PUSH THE BUTTON. Though it was cool the system

was smart enough to open the cap to grab an exposure.

So that's where I'm at now. At this point I'd like to "SAVE port configurations? " or get this serial assisant so I can name each port. Then I'd like to connect the 2 missing items. (Pyxis and cloud watcher).

I've not been able to test the dome because It has intermittent problems with communications (I think I need to replace the Xbee module). So slaving is on the back burner.

STILL as setup - I'm not using 3.0 speeds for my camera. I'd prefer the nuc but at this point I'll settle for the PI.

Is there a way to see a FREE PORT? I might connect the last 2 devices to? Doing a LS /DEV - I see a slew of devices. Are these available or used?

When I see ttyusb0 , 1 , 2 is that all I have 3 USB ports?

Ron,

I had assumed the hand controller was a physical device. I don't think the apparent mismatch between Ekos and INDI mount driver would be due to the using ethernet for the connection. It is probably still an option for you to get it out of the usb port assignment stew.

There will be some maximum number of usb devices that can be supported depending on how many internal usb control hubs your computer contains. It must be quite hight I would think, supporting the physicalconnections provided plus being able to support multiple external hubs. Don't think that need be a concern. There will be commands to explore that but not in the form of a list of USBx identifiers.
You only see those when they are assigned as devices are connected. This is just how it seems to me, not a definitive explanation. There is a level of indirection of some kind it seems when it comes to assigning the USB identifiers. As devices are discovered they are assigned an identifier. While the system is up and the device remains connected that assignment of identifier to device will be retained. Different identifiers can be assigned to the devices depending on the order they are discovered. USB connected cameras are not a problem. The mount can be eliminated by using the ethernet connection. I am left with just two devices at the moment the roof controller and the focuser so it is easy to see which identifiers are in use and make the adjustment if needed. Once assigned they tend to stay the same. The udev mapping previously mentioned is a way to provide a name that can be referenced in the user interface that is stable and can be referenced whichever USB identifier wound up getting assigned. This is a better course to take if you have a lot of devices and is a one time chore.
Tom