ASCOM does not open the com port about ascomplatform HOT 10 CLOSED

Being short isn't actually being helpful. It doesn't help anyone help you. If you have information about a problem and you're not volunteering it, and are purposefully avoiding any effort to provide it even after being asked, your report can't be taken seriously. It's a bit presumptuous for you to expect that multiple people will suddenly shift to spending their time trying to figure out what you're complaining about when all you're giving are vague references or clues on purpose. If it were up to me, this case would have already been closed due to the reporter's refusal to provide actionable and coherent information.

Now, for hopefully the last time, are you able to describe in further detail the situation and problem which prompted you to create this case? So far you've bounced around the framework, Device Hub, and ASCOM Remote - three completely different entities. You have not described what you're trying to do, how you're doing it, the ASCOM driver(s) involved, and the actual problem you seem to be having with COM ports. Can you please spend some time to explain it?

from ascomplatform.

Hi, thanks for the issue report but it appears to be missing some important details, such as a reasonably-detailed example of the problem and what you are doing to fix it yourself.

from ascomplatform.

from ascomplatform.

You'll have to be more specific, with at least an example of where you're encountering this. Many ASCOM drivers use the ASCOM serial port framework without issue. According to your rather vague description, the issue you are talking about would be quite visible across many drivers if it were in fact something wrong with the framework. You've billed yourself as an "IT professional" so I would presume you would be aware of the value of a detailed problem report and not be flippant?

from ascomplatform.

Hi Andrew,

You said: "Also you should seriously upgrade your visual studio as some of your source files need to be upgraded in order for me to work on this in visual studio 2022"

I use up to date Visual Studio versions, currently 17.9.5, and I'm just waiting to see if any serious issues are reported with 17.9,6, which was released very recently.

Please be clearer in how this VS upgrade issue manifests itself?

For backward compatibility we continue to maintain some .NET 3.5 components and I have not found a way to install the .NET 3.5 targeting pack in a new VS2022 install. The only way round this that I've found is to install VS2019, with its .NET 3.5 targeting pack and then everything compiles properly in VS2022 without further need for VS2019.

I really have no idea about the COM port issue you report because the Serial component code base hasn't changed for many years. As Dale says, greater detail please.

Best wishes, Peter

from ascomplatform.

I'm also wondering whether you are referring to the ASCOM Platform, where you have raised this issue, or whether you are actually referring to another software product?

Please can you confirm the name of the software to which you are referring?

Many thanks, Peter

from ascomplatform.

from ascomplatform.

That's... a rather odd statement since Device Hub doesn't deal directly with serial ports. At all. Device Hub is a proxy for ASCOM drivers, and it's those drivers which can or do connect to hardware via COM port.

Is this a case where you are trying to use an ASCOM driver via Device Hub and you have not configured that driver's own COM port settings via its setup window, thus causing the driver to fail to connect to its equipment?

from ascomplatform.

from ascomplatform.

Closing due to no recent activity.

from ascomplatform.