Doug S replied to the topic 'PHD2 can't be used as guider in KStars 3.4.3' in the forum. 4 days ago

Unless you worked on the hardware, it's hard to believe that you could have done any lasting damage by running/uploading PEC curves. Did you try afterwards to just turn off PEC in the mount HC (assuming you don't like any uploaded file)? If you want to send me a private message, we might be able to sort out what you did and how it went awry. We probably can get you back again without a repair bill....

Read More...

Doug S replied to the topic 'Averaging PEC control files' in the forum. 5 days ago

Those first two graphs do not look like a PEC training run. The third one does, but I'll note that it doesn't compare favorably with your guide results (analyzed from your other/separate thread). I would recommend you use Celestron's CPWI and PECTool for this (on your Celestron mount). Both are free, and PECTool does one or multiple runs (batch mode) and auto averages them into the final file for you to upload to the mount. It will also upload to the mount.

Read More...

Doug S replied to the topic 'PHD2 can't be used as guider in KStars 3.4.3' in the forum. 5 days ago

@JCJ: Venturing an educated guess, but I think there's no way you have a 1441 second PE. That result should be viewed as suspicious (either as a software bug or algorithm problem). When I opened your log in the LogViewer and analyzed the long 2.5 hour guide period, I see a 390 second PE with a magnitude of 1.5 arcsecs. Not sure if you've already run a PPEC run on your mount or not, but if not, I'd suggest it. Beyond the 390 second period, you have some minor increased error (> 0.5 arcsecs) between 100 secs and 390; probably nothing to worry about unless you want peak performance. If this is a raw mount output (no PPEC run done), it's pretty nice! My CGX-L raw values are MUCH higher (order of magnitude)! Cheers, Doug



Read More...

Doug S replied to the topic 'PHD2 can't be used as guider in KStars 3.4.3' in the forum. 1 week ago

Agree with Paul (phomer60) on drift align and dark library. There are just some instances where a drift align is highly desired. I would like to use the internal guider, but absence of drift align is an issue for me. I guess I could start with PHD2, drift align, then disconnect and switch profile to use the internal guider, but that's a pain I could avoid if Ekos included a drift align feature. I will try this dual/split config during next dark time.

Read More...

Doug S replied to the topic 'interesting USB conflict on Pi 4 (SSD vs SD card)' in the forum. 1 week ago

I and others are using SSDs for imaging, and they work fine. My ASI183 cam creates 40MB raw frames, and those frames are short (30 seconds). I use a 2 sec delay between exposures. I'm not booting from the SSD (yet), but I do run everything from SSD, just using VNC to see what's happening (over wireless). I'm running SM OS (latest release). So, can you say a bit more about your run-time config? Are you running from a laptop using wireless or ethernet & VNC, or ?? Is a laptop the download target or SSD filesystem? In my case, I have the SSD plugged into a powered USB3 hub (in fact, all my devices are plugged into the hub). A final thought about power. SSDs require a good burst of power at startup. Is your power supply to Pi4 up to the job? You might give a powered hub some thought...

Read More...

Doug S replied to the topic 'Re:Running out RPi of USB ports' in the forum. 2 weeks ago

@Mohamed: Re: "about the relationship between the LAN/WAN connection and USB".

If you are using an ethernet cable plugged into the Pi4 comm port, then you can use the USB3 port on the Pi4 for your powered hub data connect. You can also use the Pi4 USB3 port if you are communicating to Pi4 using 5Ghz wireless (i.e. no ethernet cable). However, if you are communicating using 2.4Ghz wireless, you won't have access to a stable USB3 port on the PI4. Search other posted topics for "RF interference" to read the details. If you are wireless to the Pi4, but don't know whether you're using 2.4Ghz or 5Ghz, you'll either need to log into your router to verify, or assume 2.4Ghz (and avoid USB3 until you have an ethernet cable attached to the PI). Then run your tests as previously discussed. What we're doing here is getting to a stable Pi4 power and USB config. After you've done this, you should know whether you're struggling with the new OS upgrade or not. I have upgraded (SM OS), and I don't have the issue. I run 6 USB devices (all connected to a powered USB3 hub). All work fine. If you are methodical about your setup, you'll soon have it working at peak performance. But first verify your power and comm setup, then USB2, and afterward, USB3 depending on Ethernet or 5Ghz wireless.

Read More...

Doug S replied to the topic 'Running out RPi of USB ports' in the forum. 2 weeks ago

You don't state whether you are using wireless or ethernet (and 2.4Ghz or 5Ghz if wireless). The safest bet (slower but more stable) is to start your tests by running your powered hub data cable to the PI4 USB2 port (NOT the PI4 USB3 port just yet). Make sure you have proper power for the Pi4 (3amp, 5v). Connect all your devices to the HUB's USB ports. I'll assume you have plenty of power for the HUB (verify). Power up your hub first and let it stabilize a few seconds, then, power up the Pi4. After the PI4 boots, run your Ekos devices profile; you should see and be able to access the devices. In the odd chance you have a port conflict, you may need to scan ports and/or use a port mapper config (see tutorials for this). Note that if you are using wired ethernet or 5Ghz wireless, you can use the Pi4's USB3 port for the HUB data connect instead of the PI4 USB2 port. This is MUCH faster (and should be the goal). Don't try to use wireless 2.4Ghz and the PI4's USB3 ports. Won't be stable. Good luck....

Read More...

Doug S replied to the topic 'No ASI Camera after Update - Suspect port mapping' in the forum. 2 weeks ago

@Avocette: The danger is peak draw during startup. If you're monitoring amps from PPB, you probably can't be sure what the true peak is (I think it's more of an time sampled/avg peak). FWIW, I also see mild amp draw once the whole config is up & running, which the charging port might be ok to handle. Just wouldn't trust the 1.5 during startup, especially if anything is connected to the Pi4 USB3 ports.

Read More...

Doug S replied to the topic 'No ASI Camera after Update - Suspect port mapping' in the forum. 2 weeks ago

@Avocette, regarding " the hub is powering the RPi itself through....one of the three charging ports":

A bit OT, but this is definitely a marginal power setup for Pi4 that could easily get you to odd instabilities. The Pi4 power spec is 3 amps. The actual power delivery to the Pi4 from your hub is dependent on the total power draw on the hub (all ports). Recommend you reconsider and power the Pi4 either direct from a separate 5v, 3amp PS, or from a 12v-5v (3 amp) buck converter connected between PPB and Pi4. Powering the PI4 from a hub charging port will be flaky (sooner or later). USB and wireless are the first to go on Pi4 when power is insufficient (my own experience with Pi4). Cheers, Doug

Read More...

Doug S replied to the topic 'Port is already used error' in the forum. 3 weeks ago

I experience this error as both a result of the semi-random order that the tabs start up (thus devices start up), and as a result of not using the port mapper. Jasem has a video on mapping ports to named devices that would likely solve this for you. I'm just too lazy to do it. It's pretty easy to just scan the ports if necessary at startup contention and set another available port. But I believe the youtube video gives details on how this is done to avoid it entirely. Cheers, Doug

Read More...

Craig thanked Doug S in topic KStars v3.4.3 Released 3 weeks ago

Doug S replied to the topic 'USB failure after yesterday’s upgrading' in the forum. 3 weeks ago

@AradoSKYindi: "Now that a distinction between USB 2.0 and USB 3.0 has been established, I surmise that this update trued up USB 3.0".

While it's possible you're right, I think it's important to post your full communication setup before making too many assertions. There are at least 3 known / documented issues with PI4's USB3 on the forum (all with solutions or workarounds). Here are the 3 Pi4 USB3 issue threads I know about:
www.indilib.org/forum/general/6576-pi4-u...erference.html#56911
www.indilib.org/forum/stellarmate/7382-f...rp3-or-pc.html#57229
www.indilib.org/forum/stellarmate/7374-n...t-mapping.html#57258
The first post deals with USB3 RF interference for wifi, bluetooth, HDMI, and some screen resolutions. The second one deals with an extension of the same interference issue to GPS. The third one is related to a Raspian kernel issue triggered in this latest release. So, to know which issue you're tripping up against, you should indicate your communications setup. Then you'll have a better idea of whether you're facing something new or not. Cheers, Doug

Read More...

Doug S replied to the topic 'Finally solved: GPS doesn't work on RP4, only on RP3 or PC' in the forum. 3 weeks ago

This is a variant of the USB3 issue documented here:
www.indilib.org/forum/general/6576-pi4-u...erference.html#56911
Although you've found a solution that works, there may be other solutions that could work for you (or others). See the post for details.
Cheers, Doug

Read More...