comehoogl.blogg.se

1. Stellarium crashes on startup how to#
2. Stellarium crashes on startup serial#
3. Stellarium crashes on startup driver#

Voila! Then the PMC8 will be in normal use mode permanetly. all you need is to make a small adaptor cable where by you disconnect the PMC8 DTR (pin4) from the computer end and then connect the PMC8 end pin4 to pin5(gnd). #define PMC8_AXIS0_SCALE 4147200.0 #define PMC8_AXIS1_SCALE 4147200.0 But I am not sure best way to handle these kinds of choices, so submitted the issue to the INDILIB gitbub.Īs far as a program to keep inverting the DTR in the FTDI firmware.

Stellarium crashes on startup how to#

pmc8driver.cpp:#define PMC8_AXIS0_SCALE 4608000.0 pmc8driver.cpp:#define PMC8_AXIS1_SCALE 4608000.0 Coincidentally, I was looking at how to do this.

Stellarium crashes on startup driver#

The current INDI driver for PMC8 is for the LoMandy G11. In fact, I've used the same pi to control my old Celestron mount just fine. My location in Kstars is slightly off (the difference between downtown and the suburbs), but it should be fine. Some additional info in case it's helpful. After reprogramming the cable back to its default settings (I had inverted DTR per the indi driver instructions), I started up StellariumScope and then slewed to the same objects in Stellarium.

Stellarium crashes on startup serial#

Just to check my cable, I unplugged the serial cable from the pi and into my laptop. The slew was off again by what appeared to be the same amount. So I parked the mount again, and made a remote connection to the indi client from Stellarium on my laptop. I didn't measure exactly, but it seemed to be by about 10-15 degrees each time. I tried several objects from the parked position, each time re-parking the mount and clearing the alignment. After some initial connection difficulty, I realized the default baud rate was incorrect, switched it to 115200, and got a connection. I opened Kstars, went to the Ekos menu, created a new profile using "Explore Scientific PMC-Eight" as the mount, and started up the Indi client. So then I switched to a serial connection and connected my raspberry pi. I tried slewing to several targets without choosing any alignment stars, and the mount slewed to them almost perfectly. I am hoping someone could provide some insight in to this issue.I polar aligned the mount using the polar scope and tested that everything was working by connecting to the mount with ExploreStars. I know on my end I even had our tech support trying to figure it out. Since MS does not seem to want to provide assistance for their own product, after all how could it be their fault ) Needless to say that I as well as others have The automated MS assistant is a joke and I have found no other valid course to revive Visio. It does not seem to exist either in Windows 10 or the versions of Office I have been working with. I could not find the online repair option that I have read about. Tried the repair options both for just Visio as well as for the overall Office.

I have uninstalled and reinstalled Visio and/or All of Office, including different versions of both (32 & 64 bit).

I did try to uninstall some of the Visio updates to no avail.

I have the sense that this was caused by a MS update, but have no hard proof. If I answer 'yes' the program stops working and displays the 1st msg.Īfter looping through this I will eventually get this msg. If I answer 'yes' the program crashes attempts to restart and I get this msg. When I try to start Visio I get this msg.