Hi Phil
I spent most of the day on this. But I do have some positive news for a change.
As of right now, I have not run exhaustive tests, but, tis a major step forward. I know you probably not interested in the details, so I will keep things brief.
I have
1. Rewritten most of the motor code and integrated things in the main loop as three states, but the code is significantly different, It is homing. Added safeguard check for Homing by sensor when sensor is not found.
2. Windows app re-written to take advantage of the new things added in the firmware
3. Updated PDF with screen shots
4. have not had time to check the ASCOM driver but it should work.
5. All this placed on a Shared Link - Please email me at gmail for the link details.
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Robert
I performed different tests that I describe below, each time creating a new log for more clarity
TEST 1
1- launch app
2- click on <connect> (without the option <home on="" connect="">
3- MAIN tab asks for a displacement of 40°. Click on <move>: displacement Ok. Current angle=40.
4- Click on <home>:
return of the rotator pos 0, but the current angle indicates 40.
5- I ask for 0°, click on <move> moving the rotator inversely to the needles by 40°
6- click on <home>: no movement
7- Disconnect as is and close the app</home></move></home></move></home></connect>
TEST 2
1- launch the app
2- click on <connect> (with <home on="" connect=""> checked. The position is unknown)
No rotator movement
3- MAIN tab, current angle is at 0, Click on <home>: no movement.
4- 40° movement request <move>: return to position 0.
5- click on <home>: return to the 40° position.
6- request for a 140° movement then <home>: return to position 0 (sensor detection)
7- disconnection as is.</home></home></move></home></home></connect>
TEST 3
1-App launch
2- click on connect (Home on connect ok)
no movement the sensor is already detected.
3- request for a 50° movement: OK.
4- click on <home>: return to 0, the current angle remains at 50.
5- disconnect as is and close the app.
6- launch the app and connect (Home on connect OK):
current angle is 0
7- disconnect and close the app.</home>
I hope my explanation is understandable.
English is not my mother tongue.
things are progressing, the sensor is now detected and the HOME function seems to work as long as there is no disconnection (the position is not memorized).
I did not have time to test the ascom driver
i will see it tomorrow
IMPORTANT
If doing any tests: Make sure that 60s has elapsed before reconnecting app or driver
Please send that to me via gmail,
the position is not memorized
Yes, it is.
When position is changed for example a move, when the move stop, a timer is invoked and saves the new position to eeprom. That timer runs for 30s (from memory), after expiry of the timer, the position is saved.
If you disconnect or do another move within that 30s, then it will not be saved. I think this is mentioned in the PDF.
Last edit: brownrb 2023-04-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi robert
I just tested the ASCOM driver
at the connection the rotator (in random position)
moves slightly but does not return to 0
I don't know where the logs are saved.
regards
Phil
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ASCOM Logs are stored in the Users Documents folder, in a sub folder called ASCOM
Posting the log is not required now, because that driver was broken, and instead of fixing it I have been busy rewritting the entire driver from scratch again. I did that because there are also some other things that do not work in the driver.
There was a timing issue in relation to the ASCOM driver and the firmware, and when it became ovious this was a significant error, modifying the driver code would have proved fruitless, so I rewrote the driver from scatch.
It cannot be released because the firmware also had an issue, and again, the firmware has undergone significant changes and whole sections of it rewritten. During that re-write (which is not yet completed) large sections of firmware code was changed to address the issues that the ASCOM driver and firmware 125_1 interaction were causing.
I have worked on that from early Oct, so its not gone unnoticed.
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, is there anyone who has home position working?
For me, the application shows that the engine is running and the engine is standing still.
Sorry for my English.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it is broken. In fact it is all broken (most things work but a few do not)
Current State:
The following have issues when some things do not work at all. Not all have the same issues, but the major sources are the fimware and ascom drivers not interacting correctly. This is what is on Source Forge
Firmware 125_1
ASCOM Driver 109
Windows App 2002
I do not have a time frame on when this will be fixed. But I can say that there has been massive work being done on the rotator.
The firmware, ASCOM driver and windows app (not yet released) have basically been rewritten. That required a significant amout of work. I am not getting younger.
Currently the Windows app is nearly complete (still waiting to firmware to be finished).
The ASCOM driver has had major changes but now waits for the firmware to be finished
The ASCOM App Tester is finished and uploaded
The Firmware is about 75% complete, the 25% still remaining is the move home using sensor.
i think you can probably understand that every single thing has to be re-tested now in firmware, app, drivers, every single choice, change in value, read/write values, every config selection, and so on for firmware, ASCOM, windows, linux app. Thats a lot.
The PDF still awaits the screenshots, but has had major significant additions.
The next release will NOT be compatible with current or older code/apps/drivers. No changes to hardware. I don't have a timeframe for release, I wish I did, but I don't. My estimate is probably around 120hrs + of work left. As one gets older one also slows down.
And I really do not want to post updates every week or so, the feedback just gets too overwhelming for me and slows everything down.
But I am working on it. This is the latest revision numbers I am working on. This shows how much has been done - every new addition, deletion, feature, bug fix etc bumps the revision number by 1, eg 127_00 to 127_01 to 127_99 to 128_00 etc etc
Current Work State
Firmware 128_22
Windows 2005_02
ASCOM 115
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Even without returning to zero, the software is sufficient for me and basically does what I need. Thank you for your work on the project. I do some programming myself and I know how many things need to be put together to make everything work.
Regards.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Phil
I spent most of the day on this. But I do have some positive news for a change.
As of right now, I have not run exhaustive tests, but, tis a major step forward. I know you probably not interested in the details, so I will keep things brief.
I have
1. Rewritten most of the motor code and integrated things in the main loop as three states, but the code is significantly different, It is homing. Added safeguard check for Homing by sensor when sensor is not found.
2. Windows app re-written to take advantage of the new things added in the firmware
3. Updated PDF with screen shots
4. have not had time to check the ASCOM driver but it should work.
5. All this placed on a Shared Link - Please email me at gmail for the link details.
regards
Robert
Hi Robert
I performed different tests that I describe below, each time creating a new log for more clarity
TEST 1
1- launch app
2- click on <connect> (without the option <home on="" connect="">
3- MAIN tab asks for a displacement of 40°. Click on <move>: displacement Ok. Current angle=40.
4- Click on <home>:
return of the rotator pos 0, but the current angle indicates 40.
5- I ask for 0°, click on <move> moving the rotator inversely to the needles by 40°
6- click on <home>: no movement
7- Disconnect as is and close the app</home></move></home></move></home></connect>
TEST 2
1- launch the app
2- click on <connect> (with <home on="" connect=""> checked. The position is unknown)
No rotator movement
3- MAIN tab, current angle is at 0, Click on <home>: no movement.
4- 40° movement request <move>: return to position 0.
5- click on <home>: return to the 40° position.
6- request for a 140° movement then <home>: return to position 0 (sensor detection)
7- disconnection as is.</home></home></move></home></home></connect>
3- request for a 50° movement: OK.
4- click on <home>: return to 0, the current angle remains at 50.
5- disconnect as is and close the app.
6- launch the app and connect (Home on connect OK):
current angle is 0
7- disconnect and close the app.</home>
I hope my explanation is understandable.
English is not my mother tongue.
things are progressing, the sensor is now detected and the HOME function seems to work as long as there is no disconnection (the position is not memorized).
I did not have time to test the ascom driver
i will see it tomorrow
IMPORTANT
If doing any tests: Make sure that 60s has elapsed before reconnecting app or driver
Please send that to me via gmail,
the position is not memorized
Yes, it is.
When position is changed for example a move, when the move stop, a timer is invoked and saves the new position to eeprom. That timer runs for 30s (from memory), after expiry of the timer, the position is saved.
If you disconnect or do another move within that 30s, then it will not be saved. I think this is mentioned in the PDF.
Last edit: brownrb 2023-04-13
hi robert
I just tested the ASCOM driver
at the connection the rotator (in random position)
moves slightly but does not return to 0
I don't know where the logs are saved.
regards
Phil
Hi
ASCOM Logs are stored in the Users Documents folder, in a sub folder called ASCOM
Posting the log is not required now, because that driver was broken, and instead of fixing it I have been busy rewritting the entire driver from scratch again. I did that because there are also some other things that do not work in the driver.
There was a timing issue in relation to the ASCOM driver and the firmware, and when it became ovious this was a significant error, modifying the driver code would have proved fruitless, so I rewrote the driver from scatch.
It cannot be released because the firmware also had an issue, and again, the firmware has undergone significant changes and whole sections of it rewritten. During that re-write (which is not yet completed) large sections of firmware code was changed to address the issues that the ASCOM driver and firmware 125_1 interaction were causing.
I have worked on that from early Oct, so its not gone unnoticed.
regards
Robert
Hi, is there anyone who has home position working?
For me, the application shows that the engine is running and the engine is standing still.
Sorry for my English.
Hi Sylwester
Yes, it is broken. In fact it is all broken (most things work but a few do not)
Current State:
The following have issues when some things do not work at all. Not all have the same issues, but the major sources are the fimware and ascom drivers not interacting correctly. This is what is on Source Forge
Firmware 125_1
ASCOM Driver 109
Windows App 2002
I do not have a time frame on when this will be fixed. But I can say that there has been massive work being done on the rotator.
The firmware, ASCOM driver and windows app (not yet released) have basically been rewritten. That required a significant amout of work. I am not getting younger.
Currently the Windows app is nearly complete (still waiting to firmware to be finished).
The ASCOM driver has had major changes but now waits for the firmware to be finished
The ASCOM App Tester is finished and uploaded
The Firmware is about 75% complete, the 25% still remaining is the move home using sensor.
i think you can probably understand that every single thing has to be re-tested now in firmware, app, drivers, every single choice, change in value, read/write values, every config selection, and so on for firmware, ASCOM, windows, linux app. Thats a lot.
The PDF still awaits the screenshots, but has had major significant additions.
The next release will NOT be compatible with current or older code/apps/drivers. No changes to hardware. I don't have a timeframe for release, I wish I did, but I don't. My estimate is probably around 120hrs + of work left. As one gets older one also slows down.
And I really do not want to post updates every week or so, the feedback just gets too overwhelming for me and slows everything down.
But I am working on it. This is the latest revision numbers I am working on. This shows how much has been done - every new addition, deletion, feature, bug fix etc bumps the revision number by 1, eg 127_00 to 127_01 to 127_99 to 128_00 etc etc
Current Work State
Firmware 128_22
Windows 2005_02
ASCOM 115
Regards
Robert
Hi,
Even without returning to zero, the software is sufficient for me and basically does what I need. Thank you for your work on the project. I do some programming myself and I know how many things need to be put together to make everything work.
Regards.
To all above
I am posting a new version which address a HOME using HPSW error.
Regards
Robert