... assumed to have a range of movement that begins at zero. We had to pick *some* value and zero was it. Remember, you're specifying an absolute position, not...
It is just the convention that has been adopted. Absolute focusers are assumed to have a range of movement that begins at zero. We had to pick *some* value and...
I didn't say that typing wasn't important, I said that using typing to enforce your input range is bad design. The ASCOM specs are as general as possible; if...
... Are you serious ?! I totally disagree with you on this point :-( Typing is _very_ _very_ important ! If I take the MaxStep property as an example, the...
My previous email got posted to the group hours after it was sent, sorry it's after the fact....... Regards, Chuck Faranda http://ccdastro.com ... From: "Chuck...
Tim, ... provide a method that performs this check and abstracts away all the formatting, conversion and localization issues. The client would supply their...
Yes, specifying the allowed range for any value is a good idea when defining specs. There's no need for unsigned integers, since signed integers will always...
What would be a better (long term) solution is for the platform to provide a method that performs this check and abstracts away all the formatting, conversion...
Peter, I've understood this issue (about long/int usage). Btw, the assembly are using Int32 integers. What I was noticing is that the missing "unsigned" type...
Oops !!! You caught me :-) Please replace the "if" line with the following : if (CheckVersion.CompareTo(new Version("5.7")) >= 0) The "5.7" string is the...
Hi Christophe, ... instead of UInt64. (We could discuss the choice of Int64 instead of Int32, but it's not my purpose, here). Hopefully I can clarify the issue...
Peter, I think the warning would be welcome ;-) Btw, in C#, it's not that hard to check for versions : ================== ASCOM.Utilities.Util UtilObject = new...
Christophe, ... contains "Current Platform version in m.n form". But it does not say that it is representing a float. So, programs/drivers that do the ...
That's pretty much the scenario I had in mind when I created NotConnectedException, even though the name doesn't quite fit when disconnecting. I didn't want to...
This post is related to the ASCOM-32 issue. As suggested in this issue, I was going to modify the focuser doc to introduce the "new" types : Int32/Int64 for...
Hi Hartmut, ... Thanks for reporting back, I'm glad that worked. The installer must be comparing the version number as a string rather than as a number. ...
I think that this problem is a mis-interpretation of the documentation. Specs say that the PlatformVersion property returns a string that contains "Current...
Hi Peter, in a conversation with Chuck regarding the update of his driver he found the problem. My decimal separator is a comma, not a period! I changed the OS...
Hi all, In the Move() method, the actual specs say that : - "Position parameter of the Move() method is an integer between 0 and MaxStep." if the focuser is...
Hi Hartmut, ... This sounds like the RoboFocus installer is keyed into expecting exactly version 5.0, as you saw, the updater does change the platform version...
Hi, I tried to install RoboFocus(3.0.9)Setup.exe but the program reported The ASCOM Platform 5 is required for this driver. Platform Version utility and...
Does anybody know of an diy ascom filter wheel project.I can built the electronic but the software and firmware is a little outside of my abilities Regards ...
Yes, I understand, but System.Exceptions (as well as Ascom exceptions, btw) can provide a text string describing the error encountered. So here, the exception...
The error should report what went wrong, to help the user and/or developer solve the problem. The exception will vary depending on what happened, for example: ...
Hello, in the focuser doc : "An exception will be raised if the link fails to change state for any reason." What exception should be raised ? I don't see any...