Just to bring my issue to closure; I reviewed the StellarMate Faq's and there was a handful of possible causes of the failure to connect.   stellarmate.com/support/faq.html?view=faq&faqid=27

I went through this list up to the point of receiving a new Nikon to StellarMate video cable.  Today I tested the new cable out and believe it or not it worked.  I went back to the old cable to see if this might be a fluke.  Even though this connection can be found by doing the lsUSB command the old cable did not connect properly.

This issue is resolved and another lesson was learned.  


This afternoon after updating the StellarMate OS I tried to connect only 2 devices on my StellarMate Plus. (I also have a separate USB Hub that only has the dew heater).  The Pegasus Pocket Box connected with no issues every time.  The other device which was the Nikon D5300 did not connect once.

There were times that the Nikon camera showed up in the INDI Control Panel, but the majority of the time it didn't show up at all.

I tried sorting this out with making assignments in the Serial Port Assistant.  I got an error message saying something to the effect that you can't add duplicate devices.

The Nikon camera did show up as not connected for a while but after I pulled out and plugged back in the Nikon's power cable in the Pegasus device it did not show up again.

My PPB is registering at port 0.

The Nikon camera is showing up in the USB listing.


Does everything look correct in this listing?

Any ideas in how to get the Nikon D5300 listing in the INDI Control Panel?


Last evening in doing an online search I was able to find a sudo script that erased the majority of the images in the trash bin.

This was:   sudo rm -rf ~/.local/share/Trash/*

As going through this process of erasing on the Pi hard drive is quite tedious I would certainly prefer locating my FITS images on a USB flash drive, but I've found that this just doesn't work.

I may end up getting an extra long ethernet cable and snake it through my house and outside to prove out whether bad WiFi signal is the culprit of the whole download latency or failure issue.


Alright, I think the issue might be because I have 22 Gigs in my trash can.  Unfortunately I am unable to delete the trash can using right click delete or just clicking on the trash can to delete.

Any ideas in how to get rid of the data I put in the trash can?

Here is the screen I am getting on the Pi.


Is there a command or permissions that can help me move these files off?


Last evening I attempted to capture some flat images using Ekos CCD tab.

The captured images were directed to the Pi device.

I was able to capture 7 flats but with quite a bit of download latency.  (The pop up showed 11 seconds but it likely was longer between images).

On the 8th image the capture errored out; this was what was on my screen.


I tried shutting down and coming back up again but could not get the capture process working.  It would try once with the long delay and then the camera clicked at good capture speed with errored out images.

Normally the download takes around 5 seconds, but I've not been able to capture images to a USB flash drive due to download latency.

I believe some updates over the weekend may have helped in one area but created some extra latency.

Here is the error message that I am seeing on the Nikon screen.


Any ideas in doing a test to see what's going on?  Might there be a setting or 2 that I need to review?

In the future I might do some house wiring projects to get the proper circuit run outside to connect a TP Link power line type adapter to my network.

However my EQ6R mount is directly outside my door so I should have adequate WiFi signal.

Really hoping to be able to finally get my Ekos setup for the EQ6R mount up and running.



Yes, I do wish this would exit the INDI Control Panel properly but even so at least now I can continue with the rest of the set up and tweak these minor details instead of being stopped dead at the starting line.


AstroNerd:  I used the sudo script and it did go through an update routine.  As far as I know this has resolved the connection issue as every time I enter Ekos the connection resolves itself.

I am however seeing one undesirable behavior when I hit the disconnect button to close the INDI Control Panel this drops me to the Stellarmate desktop without actually closing the INDI Control Panel.  The next time I get into Ekos and the INDI Control Panel it warns me that an instance is still running.

I'm hoping that the sudo script went successfully all the way through the install routine.

Just in the event that it didn't I'll attach a screen shot of the end of the install.

If this looks normal I guess I can't suspect that it was due to the install fading out.


Even if the exit to the desktop disconnect is not fixable it is very awesome that the connection behavior appears to be resolved.

Thank you!



As far as I know everything is up to date with the Stellarmate Software.

I went through the Software Update icon on the Stellarmate desktop.


As far as I know everything is up to date with the Stellarmate Software.

I went through the Software Update icon on the Stellarmate desktop.

I am using the SM OS 1.5.8.

The INDI Control Panel does look different than the previous version I was using in the Connection tab.


I am using the SM OS 1.5.8.

The INDI Control Panel does look different than the previous version I was using in the Connection tab.

I am not sure what you are referring to as far as being connected to the stable channel.

If you need any specific information from my setup for bug detection let me know.




Thank you for this idea.  I thought that it would immediately work as it should remove the auto connect confusion.

I replicated your instructions and the connection still failed.

I think there might be one more problem that may or may not need untangled.

The image below shows that there are 2 port connection options.  Highlighted is the Focus Cube unique serial ID even though I'm in the INDI control panel under the PPBA device.  Is there a way to remove the unwanted device's serial id.  I think that my PPBA wants to connect as the Focus Cube.

Hopefully this might resolve some of the conflict.  Thank you.




Jasem:  I am using the "Pegasus Focus Cube" driver.

It does appear however that Jerry's issue may be resolved by switching out the DMFC driver.

Any thought about the USB port behavior that I am still seeing from my last post in this thread?  I tried a number of combinations yet nothing is making connection consistent? 

It would seem that since each serial device is registered by it's own unique serial id that it would lock the USB ports in place and not cause the auto search confusion that I am seeing.


This afternoon I tried a flurry of different changes to hopefully find the reason for the perpetual Pegasus Port conflict failures.

Not really thinking that this might solve the problem, yet hoping for perhaps a breakthrough with a fresh install I installed the SM OS 1.5.8 on a purportedly faster micro SD card.  When I got this up and running I could see that this did not remove the port conflict between Pegasus Devices.

Next I removed the Pegasus Focus Cube USB connection from the PPBA and moved it into the Raspberry Pi device.  Initially both the PPBA and the Focus Cube came up fine.  The ports seemed to stay stable with the PPBA having USB0 and the Focus Cube taking USB1.  I started up several times with no issues.

Seeing the general issue itself possibly fixed I was very happy and I next added my last serial device which is the EQ6R Pro mount.

Immediately this did not work.  None of the serial devices were able to connect.  I tried numerous little things to get the combination of 3 serial devices to work with each other to no avail.   I found out the USB assignments in this arrangement.  Surprisingly the PPBA moved to USB2 and the EQ6R took over USB0.

I removed the EQ6R connection from my setup and still had a failure between the PPBA and the Focus Cube that I initially did not have.  The difference that I noted was that the Focus Cube took over USB0 and the PPBA had USB1.

Of course going back to where the PPBA was the only serial device made it work.  And this slid it back to USB0.

Very frustratingly I discovered that by adding the Focus Cube back both connections once again failed.  In verifying the USB assignments I could see that the Focus Cube wanted USB0, and the PPBA slid over to USB1.

It seemed the only stable connection occurred when the PPBA stayed at USB0.

Maybe I'm missing something blatantly obvious but why won't the devices keep their USB assignments?  I would love to hear that I did something wrong with my setup but there doesn't appear to be a way to keep everything from sliding around when devices are added.

It would be nice if the auto search could be disabled on a device once it successfully comes up.  Let's say the PPBA comes up successfully by itself on USB0, the 1st thing I do is make sure auto search is disabled and then I hit "Save" under options.  When I add another device then there is a battle for USB0, both devices go back to auto search until the search is concluded.  If the PPBA loses then both devices don't connect.

To have the unique serial ID represented for the USB port is a very good idea, but it doesn't lock the port in place.  Am I the only one that is noticing this?

Is this only a StellarMate OS issue as the moderator on the Pegasus Forum suggested?

You can't imagine how frustrated I am with this issue.  I am doing my best to keep patient.

I can certainly imagine that it is frustrating on the programming end as well.
The unique serial port idea should solve the problem, but why doesn't it lock?