Same hardware but two sets of parameters for two tubes
Version 2 of the myFocuser Project
Brought to you by:
brownrb
Menu
▾
▴
Hello.
I have read about controlling two focusers at the same time, but I think this is NOT what I need. I have a single controller and two telescopes with two identical motors. I would like to be able to quickly select the proper values for step size, maxsteps, backlash... that are different in the two telescopes, depending on which tube I am using that night.
Is that possible?
All the best
Juan
Hi Juan
You did not mention if you want to do this in ASCOM or WINDOWS application.
Using the Windows Application with two different telescopes/etc
This video outlines the use of Profiles
https://www.youtube.com/watch?v=-LSDK2fTHwc
For a single controller with two different telescopes
First telescope setup
Start Windows app. On connection tab, On Connect Send group
Select the radio button None,
Click Connect.
Change whatever settings you need to to set values.
Go though the various tabs and change the values as neccessary
When you have set the values on the tab, click Set to send them to the controller
Change to the next tab, change, then Set etc
Now you can save all of these as a profile.
Open the Profile tab, specify the name of the profile, then click Save
Disconnect, power off, move controller to the other telescope
Second telescope setup
Repeat every thing as per the 1st telescope
BUT
Use a different profile name when saving the profile.
Now you have to remember which profile is for which telescope
Tonight I will use the 1st Telescope profile
Connect the controller to the 1st telescope, power on
Start Windows application
In the On Connect Send group, select the radio button Profile,
Click on the Profile tab, click Load, navigate to the folder where the profile was saved, and click on the saved profile for the 1st telescope.
Click Connect.
Good to go
Tonight I will use the 2nd Telescope profile
Connect the controller to the 2nd telescope, power on
Start Windows application
In the On Connect Send group, select the radio button Profile,
Click on the Profile tab, click Load, navigate to the folder where the profile was saved, and click on the saved profile for the 2ns telescope.
Click Connect.
Good to go
Note
Prolfiles do NOT save/restore the position value, because the controller keeps track of that.
So that is for Windows.
Using ASCOM
Currently the ASCOM driver does not support profiles.
But you can use the ascom app to handle 1 controller and 2 telescopes
In the driver connection tab, when you select the ASCOM driver in the chooser, and select properties,
Make sure that all the checkboxes in the Update On Connect group are all UN-checked
Then click Connect. No values are changed, only Read from the controller.
Note: Can I use the same trick with Windows App
The Windows app also has settings for all the controls on each tab. These settings, along with the Controller settings, are saved/loaded using profiles. So you have the visual clues that show you what telescope you are working with
Photos attached (in sequence)
Regards
Robert
Just a note for clarification.
In the above examples, each telescope requires it's own controller.
To use 1 controller for both scopes is not really viable. All the scenarios presented here require dedicated controllers for each telescope.
Position is saved by the controller (as well as other settings). If the controller was fitted to telescope 1 and the last position saved was 3546, then, when the controller is fitted to telescope 2, the position to start is 3546, which is wrong for telescope 2. The chances of telescope 1 and 2 having identical positions is highly unlikely, you probably have better chances of winnng Lotto jackpots.
regards
Robert
Thanks a lot, Robert.
Indeed, a wrong value of position is not a problem for me because I have a home position sensor so the first thing I do is going home to reset the 0 position... Are there any other problems?
I have done a few tests and sometimes the values set in the program are not written in the txt file... I have changed them by hand with the notepad, but I think sometimes are not well read, neither...
Then, If I have well understood, the solution for the moment to use a single controller with two tubes is creating 2 profiles in the windows app, enter to write the proper values depending on the equipment of that night, then disconnect and enter in ascom (I use NINA) without changing things. Am I right?
By the way, in case someone ask you: I have had to change the simbol used for the decimal point to " . " in windows regional options because by default in Spain it is ", " and the values of step size were not correctly set (I believe the others are all integers).
Regards
Juan
Hi Juan
You can do similar things using the ASCOM driver using Send On Connect.
But as of right now, the ASCOM driver does not support profiles.
For Windows there is always the choice of using the myfp2 windows app and the myfp2mini windows app. The mini app was several versions being.
There is a new release which is imminent. I will post a message re this today,
As for the Regional locale issue. Yes, but this should be fixed in the next release. If you send me an email on gmail then I can provide access to the next release and I would appreciate any feedback as to if the issues of , and , are resolved.
In terms of the saved profile, and reloading etc, this should be fixed by the new code.
Regards
Robert
Just a quick update re this
In the new PDF uploaded today, v328 I have included more explanations and examples of using two telescope systems, using a single Windows or ASCOM driver, as well as using multiple versions of Windows and ASCOM
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/Documentation/myFP2-328.pdf/download
pgs 132 and pg 146
Regards
Robert
Thank you so much. I will test it as soon as I can and let you know.
Hello again. I am afraid I have spoiled all the configuration trying all these stuff of profiles...
I have installed ASCOM driver 300 and windows program 2.5.0.4, which I believe are the latest versions.
Windows app opens but when connects it seems sends some commands but in the end beeps agains and says "not connected"
If I access to ascom options through nina I can connect, although it complains all the time about position being >= maxsteps... Only if I set pos=0 allows to connect... Also, I have a second ascom driver that says "autoregistered by " that does not work... and I don't know how to remove...
Is there a way to reset everything and start again all the configuration? I am now so confused that I don't know what to do... :(
Thanks
Last edit: Juan Gonzalez 2023-06-24
Hi
The files are
firmware 328
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/ARDUINO%20FIRMWARE/Firmware_myFP2_328.zip/download
ascom 300
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/ASCOM%20DRIVERS/myFP2ASCOMSetup300.exe/download
windows 2505
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/WINDOWS/MainApp/myFocuserPro2_2_5_0_5.zip/download
Please note that Windows 2505 requires firmware 328
Firmware 328 requires you to first run ClearEEPROM in the tests folder before upgrading to firmware 328
Windows not connecting
Please update to firmweare 328
Remove existing windows app via control panel
Download windows 2505 app
Install 2505
Enable logging on Logging tab
Connect to focuser.
If fails to connect - exit the app and send me the errorlog generated.
If you do not know where the log file is, use settings menu
Settings-Logging-LogFilePath
regards
Robert
An ascom driver is stored in
C:\Program Files (x86)\Common Files\ASCOM\Focuser
Depending on your version of ascom driver, it may be in a sub folder myfp2
Delete all files for myfp2ascom, eg
for the 2nd ascom driver
ASCOM.myFP2ASCOM1.Focuser.dll
myFP2ASCOM1Language.txt
myFP2ASCOM1Readme.htm
ASCOM trace logs are stored in users documents folder
eg
Documents\ASCOM\Logs yyyy-mm-dd
and look like
ASCOM.myFP2ASCOM.0644.401580.txt
Stuffed Profiles.
If you know the current focuser settings are correct
Delete existing profiles.
Start windows app
Check OnConnectSend - click None
Connect to the focuser
Once connected go to the Profiles tab and save into a new profile.
If you are sure the corrent focuser settings are wrong.
Delete existing profiles.
Start windows app
Check OnConnectSend - click None
Connect to the focuser
Once connected go to the menu
Settings Set Default Settings
Controller will reboot
Exit Windows app, wait 5-10s
Start Windows app
Check OnConnectSend - click None
Connect to the focuser
Once connected go to the Profiles tab and save into a new profile.
Hello Robert, and thanks again for your detailed help. I am on my way to reset everything. I have cleared eeprom and after uploading 328 firmware it starts to buzz and turns the lights of buttons permanently. Does it mean I have configured something wrong?
Hi Juan
The controller uses a POST type code. On boot this code enables the buzzer and the leds, which are turned on.
The controller is then initialised and configured, and once ready, the leds and buzzer are turned off.
For a working controller, users would wee the leds go on, buzzer heard, then a second or two later, turned off. The turn off means the controller successfully booted.
If the LEDs and BUZZER remain on, then there is a problem.
In the file IMPORTANT-328-MAJOR-UPDATE.txt included with the firmware release, it states
myFP2 Firmware 328
This is a significant update with major code changes. It is important that before programming the controller with firmware 328 that the previous contents of EEPROM are cleared.
RUN ClearEEPROM BEFORE UPLOADING FIRMWARE 328
Please run ClearEEPROM again. The program writes to the serial port what it is doing. Wait till the program has finished.
Then reprogram the controller with firmware 328
If you still have issues after this, then please advise and I can work with you to resolve any issue.
Regards
Robert
Hello.
I had done everything as so said but I have gone through everything again using the win11 pc. I have had to install arduino and all the libraries (by the way, not only timerOne has to be downloaded from githup as you state in the "additional libraries to install" file, but onewire too)
Well, the problem persisted but then I realized the screen was off al the time... I have disabled the screen (oled 0.96'') in the config section and IT WORKS :) Maybe something is wrong with that screen and that causes the problem. As it is not critical for me, I will keep ir off for the moment.
I have tried to send different profiles and check if it changes what it should. Everything seem to work fine except the stepsize. It does not change it... Maybe because it is the only decimal number in the parameter set?? I will take some tests on the field as soon as I can.
THanks
Last edit: Juan Gonzalez 2023-06-26
Hi Juan
Please be aware that the
ASCOM driver v300
Windows app v2_5_0_5
only work with firmware v328
If the firmware is older, then the new versions of ASCOM driver and Windows app will not connect. And again if the windows app is older and used with firmware 328 that can also cause problems.
I have tried to send different profiles and check if it changes what it should. Everything seem to work fine except the stepsize. It does not change it... Maybe because it is the only decimal number in the parameter set?? I will take some tests on the field as soon as I can.
I would need to see the saved profile txt file and the Windows log file to be able to provide an answer about stepsize, but there was in fix in recent releases for step size.
regards
Robert
It is best not to reprogram the controller with another version or lower version in order to test something - I dont advise doing that - not saying that this has happened - just letting you know that users something try the latest version, have an issue, reprogram with a lower version, and next the controller won't respond.
Because there are often variations in the way that focuser settings are saved and restored, the order for settings changes from one version to another - so this is why it is best to stick with the one version 328 and get it working.
ok Robert. I have everything up to date and won't try to go back to earlier versions.
I have checked that the problem is when reading the profiles: stepsize is not updated (all the rest of parameters are read normally) The values are written in the profile file, but the value of stepsize is not updated with the value in the file when you read it...
Is you want I may send you profile files or logs, but I am pretty sure this is the problem. It is not big deal, I can just put it by hand...
All the best
Hi Juan
It now turns out that your report on "StepSize" not being restored was very useful.
Actually, on investigation today, the saving-restoring Profiles had some issues, and those issues also affected File Save/Restore focuser settings. I introduced that issue in the Windows App - not intentional, but my fault none-the-less
I have upload a new version of the Windows app today that addressed this.
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/WINDOWS/MainApp/
Regards
Robert
New version works nice. This has been sorted. Thanks. I have detected another issue, but will post it in different thread
Cheers