Hi Andrew, I'm one of those "software makers" you refer to. Would you mind detailing some of these lessons I ought to learn? I'm curious about the differences between the app that I help make and a co

Glad that your issue is solved. Most settings in the plugin have an explanatory tool tip if you mouse over them:

I'm in and out of connectivity this week and weekend, so I'm trying to catch up on this thread. It seems that you're specifying a possibly corrupt APPM settings file in the plugin's configuration? Jus

Can you provide the NINA log file from an example session so we can see what's going on from NINA's point of view?

NINA interacts with mounts only through their respective ASCOM driver. If PHD2 is connected to the A-P ASCOM driver, and the driver blows up when NINA attempts to use it, then something is detonating

I'm a bit late to the thread due to getting back from a week of work travel. Thanks for posting the instructions, Sébastien. Yes, the original Utilities for Astro-Physics Mounts plugin was superseded

Ah! I never noticed the magnifying glass. It never really registered as a place that would show the hostnames it found. Modally, I guess I expected them to be listed in a combox UI widget for the Host

It's an aluminum to aluminum interface. I imagine that the mount would have to be in a visibly poor shape and pretty much extremely abused for the dec and RA axis to be bonded via corrosion in such a

1. Call AP and order a grease kit. It's cheap and has both types you'll need. You may also want to replace the delrin clutch plugs if your axis is rather stiff when unclutched. A baggie of those doesn

I just noticed in the P02-13 release notes[1] that the mDNS responder feature of the embedded OS is now put into use. This is great. Kudos to Mike Hanson, I would guess? mDNS refers to multicast DNS a

The conversion isn't done on the electrical signal level; it's done on the protocol level. Ethernet frames are encapsulated in USB packets on one end and decapsulated on the far end, back into etherne

I would avoid these kinds of hacks. You might as well just do a straight USB connection to the CP5 and dispense with the extra and excessive machinery around converting from ethernet to USB and back t

Thanks. This is junk I've had to learn because of the problems that users in our world of astrodevices have to deal with. I'd much rather it just all work so I could redirect these brain cells to more

USB doesn't work like ethernet's CSMDCD. It's a protocol design where the host (technically, the "root hub") interrogates each device on the bus for whether it has any data it wants to send. The host

Yeah a big advantage with ethernet is that you can easily crimp your own cables. I wired my house with cat6 (I actually do run a 10Gb ethernet network here). I've got a few hundred feet of cable in my

It may have been that you started NINA first, then connected the camera to your system, and didn't press the refresh button to update the list of connected cameras? /dale

What you think is correct - from an app's perspective, cameras can do only one thing at a time. The image has to be downloaded before the command to start the next exposure can be given. But, on CMOS

60 millions pixels, times 16 bits per pixel, divided by 8 to convert to bytes, does yield 120MB images, modulo the extra little bit for file format headers. A note about binning - on CMOS, any binning

Yeah, I'll give you that, there. It's not so much the fault of their design but rather the use cases they're being shoehorned into. An inordinate amount of my abject ire towards micro, and mini-USB co

Raw CPU speed is one aspect in this. The other is the performance of the memory itself. Its latency (CAS latency, or CL) and clock speed are crucial to these operations where apps are copying large am