Hi there,
I just downloaded the new v314 firmware and I'm having some issues.
First of all, it should be noted that the TimerOne library is missing from the package.
I was able to download and install it to resolve the missing library error during program integrity check.
I activated the option define PB_STEPS with a value of 200. Value that I had forced directly in the lines of code of the buttons of the old firmware and which works very well.
But now, with firmware v314 the buttons no longer have any effect and I don't see where the problem comes from.
I have tried other values but without result.
Does anyone have the solution.
Thanks in advance,
patrick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Patrick
The folder
Additional library to install
in the zip has the info re timer library, yes, I could have mentioned it, should have, in the post. Apologies.
Did you first clear the eeprom before reprogramming the new firmware 314?
regards robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Patrick
The reason why the push buttons were not moving is probably that pbsteps was 0.
If target + steps then means target does not change if steps is 0
I have done a minor change related to the initial value of pbsteps. Firmware 314 was setting pbsteps to 0.
I have added the ability to change pbsteps using the Windows application on the motor settings tab, which means it can monitor.change the value at amy time. Since the value of pbsteps is part of the focuser configuration, it is remembered by the controller and saved in eeprom.
This change also means it is no longer necessary to define pbsteps in focuserconfig.h
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for all these explanations.
I didn't erase the eprom before reprogramming, an unforgivable mistake on my part.
I will try again with the new version to see.
I'll let you know.
Thanks again.
patrick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert.
I'm back.
This time I erased the eeprom before installing the new Firmware.
So I used the V315 directly.
Now the buttons work again but for some unknown reason the controller freezes from time to time. I have to disconnect the power supply and the USB port to make it functional again.
It's quite tedious to the point of going back to my old Firmware V312 that I had personally modified to increase the speed of the push buttons.
I will wait for the return of other users, there may still be a bug in the programming, it happens quite often when new functions are added.
I think I'm going to build a new controller that will be used for testing so as not to take the risk of finding myself without a focuser.
patrick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Patrick
I did upload an update 315-1 for that board, in addition to a update of the Windows application where pbsteps can be changed at any time.
Reboots
If you were using windows or ascom to control the focuser, these can generate an error log (windows) or trave log(ascom) which might give some feedback of the focuser operation and what was going on.
It is really hard to find these causes - because we cannot write out error messages to the serial port (because these would cause the windows app/ascom driver to fail) and the Serial port is "protected" as a device.
If you can notice what was going on just before the crash this would be extremely helpful.
When it is a bug, it is usually repeatable, do this, then do this, then do this and boom away it crashed,
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert.
I just received all the components to assemble the electronic card.
I will use this card to do all my tests without touching the functional cards.
I will come back to you to provide you with more information if I find the same malfunctions.
Cordially,
patrick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert,
I'm coming back to you because I've finished the electronic card and I'm finishing the first tests.
As a precaution I ran the program to erase the eeprom before programming the firmware V315
The problems are the same, if not worse.
I cannot create an event log file because if I check the "Log Errors" box in the "Logging" tab of the Windows application, I get an error message each time I click on one of the buttons +500, +100,…..-100, -500.
Same result with push buttons.
The map bug also occurs when clicking on the buttons of the application and not only with the push buttons.
I also noticed that the LED did not light up during motor movements. However, they do light up during initialization or programming. The LED option is enabled in the firmware.
I tested my card with old firmware V312 and windows application 2.4.8.8, everything works fine.
Sorry for not being able to help more in understanding the problem.
If I could create the log file I could send it to you for analysis but we would have to find out why the "Log errors" option does not work.
I am French so I hope the translation is comprehensive.
Looking forward to meeting you,
Cordially,
patrick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Patrick
What is the name of the firmware file you were using, the full name, eg myFP2_DRV8825HW203_315
If you are getting errors in the Windows App, that seems to indicate that something else is writing to the serial port by the controller.
Any Serial.print statements will do this.
The only exception is the 1 serial.print statement in serialcomms.h which writes reponses to commands received by the controller.
I cannot create an event log file because if I check the "Log Errors" box in the "Logging" tab of the Windows application, I get an error message each time I click on one of the buttons +500, +100,…..-100, -500.
Can you connect to the controller using the windows app?
Enable the log errors.
Connect to the controller.
If it fails to connect or fails when you click +500
The rrror log still contains information.
The error messages each time you click - is this in Windows? Is this a pop-up? How about capturing a copy, so I can see what the error messages are.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert.
I come back to you because I managed to recover the error log and cause the bug.
My focuser started from the “0” position.
I made a "+500" request with the Windows application.
The motor has turned well up to the "500" position
So far everything is OK
I made a "+100" request with the Windows application.
This time the motor has not turned and the application seems to indicate that the focuser is moving but it does not increment the steps.
From this moment everything is blocked, I have no choice but to quit the application and disconnect the USB cable and the power cable to be able to use the focuser again.
This incident also occurs with my astro APT application.
The use of push buttons also causes the same blockage.
It is however random, sometimes it takes more maneuvers to block the system but in general no more than 10 movements.
It seems to me that in the log the application loops endlessly. I think your more expert experience will give you a better understanding.
Waiting for your return,
Cordially,
After much testing I could occassionally get what you described.
I have some test firmware if you want to try the new code.
Email me at gmail.com if interested.
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 told you last week in a private message that the TMC2225-315.1 firmware was working fine with my controller. But since that time, I did new tests and could reproduce the freezing default when moving the focuser, by relative moving or with the push buttons as well. To recover, it is needed to reset both 12V and serial.
Best regards,
Pierre-Yves
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Patrick,
Yes I do experience the same problem.
I updated the controller installed on my setup with the 315.1. It works fine up to now. But the one I use for testing is systematically freezing after the first moving. Same hardware, same firmware, same config...
A suivre...
PY
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I stated, firmware 315 is broken. In fact, earlier versions below 315 are also broken but might appear not to, but given the correct sequences, they also break.
I have put together 316 update. Those that want to test it should drop me an email (not a PM on Sourceforge as I will not answer those).
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert,
I sent you an email to get the Firmware V316 to test it.
In your message you tell us that Firmware V315 is broken and that earlier versions are too.
However, I have been using Firmware V312 for months and I have never encountered the slightest problem, strange.
I therefore look forward to Firmware V316.
And congratulations again for this remarkable focuser which has everything if not more than commercial ones at an exorbitant price.
Cordially,
patrick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I went back as far as 270, and it would also fail. At that point it wasnt worth finding out when things changed, but I figure its been present in every file till now.
I did not get your email.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Robert,
I have received Firmware v316 for testing.
Unfortunately I still have the same problem.
At the first or second move the controller freezes.
I attach the log file for analysis.
Cordially,
patrick
Hello Pierre-Yves
Have you tried Firmware V316 from Robert?
As you can see it didn't change anything for me.
During a first movement request, the controller works well but it freezes on the next request.
I have to disconnect the power supply and the USB cable to be able to reset it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Pierre-Yves
We are exactly in the same situation.
To be able to use the push buttons with a faster displacement I modified the value "1" in "80" for my setup in the PUSHBUTTONS section of Firmware V312. See attached file.
The disadvantage is that to modify the speed of movement of the push buttons it is necessary to modify this value which implies a reprogramming of the firmware.
However, since I'm using one controller per gear, I no longer have to change this value once it's set.
Currently Firmware V312 is the most stable of the series, it has never crashed in my case.
Let's hope that Robert finds the anomaly in order to be able to use the option allowing to modify this value directly from the Windows application, it's still more pleasant.
Patrick
For information, I am testing a limited version of Firmware V317 sent to me by Robert.
The results are very promising. After more than an hour of testing, I failed to crash the controller. Everything worked perfectly.
Let's be patient, Robert is doing a great job and we will soon have a fully functional new Firmware.
Patrick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there,
I just downloaded the new v314 firmware and I'm having some issues.
First of all, it should be noted that the TimerOne library is missing from the package.
I was able to download and install it to resolve the missing library error during program integrity check.
I activated the option define PB_STEPS with a value of 200. Value that I had forced directly in the lines of code of the buttons of the old firmware and which works very well.
But now, with firmware v314 the buttons no longer have any effect and I don't see where the problem comes from.
I have tried other values but without result.
Does anyone have the solution.
Thanks in advance,
patrick
Hi Patrick
The folder
Additional library to install
in the zip has the info re timer library, yes, I could have mentioned it, should have, in the post. Apologies.
Did you first clear the eeprom before reprogramming the new firmware 314?
regards robert
I will upload today Firmware 315, and the Windows app which supports changing the pb step value.
Regards
Robert
Hi Patrick
The reason why the push buttons were not moving is probably that pbsteps was 0.
If target + steps then means target does not change if steps is 0
I have done a minor change related to the initial value of pbsteps. Firmware 314 was setting pbsteps to 0.
I have added the ability to change pbsteps using the Windows application on the motor settings tab, which means it can monitor.change the value at amy time. Since the value of pbsteps is part of the focuser configuration, it is remembered by the controller and saved in eeprom.
This change also means it is no longer necessary to define pbsteps in focuserconfig.h
Regards
Robert
Hello Robert,
Thank you for all these explanations.
I didn't erase the eprom before reprogramming, an unforgivable mistake on my part.
I will try again with the new version to see.
I'll let you know.
Thanks again.
patrick
Hello Robert.
I'm back.
This time I erased the eeprom before installing the new Firmware.
So I used the V315 directly.
Now the buttons work again but for some unknown reason the controller freezes from time to time. I have to disconnect the power supply and the USB port to make it functional again.
It's quite tedious to the point of going back to my old Firmware V312 that I had personally modified to increase the speed of the push buttons.
I will wait for the return of other users, there may still be a bug in the programming, it happens quite often when new functions are added.
I think I'm going to build a new controller that will be used for testing so as not to take the risk of finding myself without a focuser.
patrick
Hi Patrick
I did upload an update 315-1 for that board, in addition to a update of the Windows application where pbsteps can be changed at any time.
Reboots
If you were using windows or ascom to control the focuser, these can generate an error log (windows) or trave log(ascom) which might give some feedback of the focuser operation and what was going on.
It is really hard to find these causes - because we cannot write out error messages to the serial port (because these would cause the windows app/ascom driver to fail) and the Serial port is "protected" as a device.
If you can notice what was going on just before the crash this would be extremely helpful.
When it is a bug, it is usually repeatable, do this, then do this, then do this and boom away it crashed,
Regards
Robert
Hello Robert.
I just received all the components to assemble the electronic card.
I will use this card to do all my tests without touching the functional cards.
I will come back to you to provide you with more information if I find the same malfunctions.
Cordially,
patrick
Hello Robert,
I'm coming back to you because I've finished the electronic card and I'm finishing the first tests.
As a precaution I ran the program to erase the eeprom before programming the firmware V315
The problems are the same, if not worse.
I cannot create an event log file because if I check the "Log Errors" box in the "Logging" tab of the Windows application, I get an error message each time I click on one of the buttons +500, +100,…..-100, -500.
Same result with push buttons.
The map bug also occurs when clicking on the buttons of the application and not only with the push buttons.
I also noticed that the LED did not light up during motor movements. However, they do light up during initialization or programming. The LED option is enabled in the firmware.
I tested my card with old firmware V312 and windows application 2.4.8.8, everything works fine.
Sorry for not being able to help more in understanding the problem.
If I could create the log file I could send it to you for analysis but we would have to find out why the "Log errors" option does not work.
I am French so I hope the translation is comprehensive.
Looking forward to meeting you,
Cordially,
patrick
Hi Patrick
What is the name of the firmware file you were using, the full name, eg myFP2_DRV8825HW203_315
If you are getting errors in the Windows App, that seems to indicate that something else is writing to the serial port by the controller.
Any Serial.print statements will do this.
The only exception is the 1 serial.print statement in serialcomms.h which writes reponses to commands received by the controller.
I cannot create an event log file because if I check the "Log Errors" box in the "Logging" tab of the Windows application, I get an error message each time I click on one of the buttons +500, +100,…..-100, -500.
Can you connect to the controller using the windows app?
Enable the log errors.
Connect to the controller.
If it fails to connect or fails when you click +500
The rrror log still contains information.
The error messages each time you click - is this in Windows? Is this a pop-up? How about capturing a copy, so I can see what the error messages are.
Regards
Robert
Hello Robert.
I come back to you because I managed to recover the error log and cause the bug.
My focuser started from the “0” position.
I made a "+500" request with the Windows application.
The motor has turned well up to the "500" position
So far everything is OK
I made a "+100" request with the Windows application.
This time the motor has not turned and the application seems to indicate that the focuser is moving but it does not increment the steps.
From this moment everything is blocked, I have no choice but to quit the application and disconnect the USB cable and the power cable to be able to use the focuser again.
This incident also occurs with my astro APT application.
The use of push buttons also causes the same blockage.
It is however random, sometimes it takes more maneuvers to block the system but in general no more than 10 movements.
It seems to me that in the log the application loops endlessly. I think your more expert experience will give you a better understanding.
Waiting for your return,
Cordially,
patrick
After much testing I could occassionally get what you described.
I have some test firmware if you want to try the new code.
Email me at gmail.com if interested.
regards
Robert
Hi Robert,
I told you last week in a private message that the TMC2225-315.1 firmware was working fine with my controller. But since that time, I did new tests and could reproduce the freezing default when moving the focuser, by relative moving or with the push buttons as well. To recover, it is needed to reset both 12V and serial.
Best regards,
Pierre-Yves
Hello Robert.
Yes I would like to try the new firmware.
I send you an email
Thanks
Hi Pierre-Yves
I see we have the same problem.
Hi Patrick,
Yes I do experience the same problem.
I updated the controller installed on my setup with the 315.1. It works fine up to now. But the one I use for testing is systematically freezing after the first moving. Same hardware, same firmware, same config...
A suivre...
PY
As I stated, firmware 315 is broken. In fact, earlier versions below 315 are also broken but might appear not to, but given the correct sequences, they also break.
I have put together 316 update. Those that want to test it should drop me an email (not a PM on Sourceforge as I will not answer those).
regards
Robert
Hello Robert,
I sent you an email to get the Firmware V316 to test it.
In your message you tell us that Firmware V315 is broken and that earlier versions are too.
However, I have been using Firmware V312 for months and I have never encountered the slightest problem, strange.
I therefore look forward to Firmware V316.
And congratulations again for this remarkable focuser which has everything if not more than commercial ones at an exorbitant price.
Cordially,
patrick
I went back as far as 270, and it would also fail. At that point it wasnt worth finding out when things changed, but I figure its been present in every file till now.
I did not get your email.
Regards
Robert
Hello Robert,
I just realized that I made a mistake in your email address.
I sent you a new email.
Thanks
patrick
Last edit: Patrick PASC 2022-09-23
Hello Robert,
I have received Firmware v316 for testing.
Unfortunately I still have the same problem.
At the first or second move the controller freezes.
I attach the log file for analysis.
Cordially,
patrick
Hello Pierre-Yves
Have you tried Firmware V316 from Robert?
As you can see it didn't change anything for me.
During a first movement request, the controller works well but it freezes on the next request.
I have to disconnect the power supply and the USB cable to be able to reset it.
Hi Patrick,
Yes, still the same behaviour as the V315.1. I uploaded the V312 to check the controller, it works quite well...
Pierre-Yves
Hi Pierre-Yves
We are exactly in the same situation.
To be able to use the push buttons with a faster displacement I modified the value "1" in "80" for my setup in the PUSHBUTTONS section of Firmware V312. See attached file.
The disadvantage is that to modify the speed of movement of the push buttons it is necessary to modify this value which implies a reprogramming of the firmware.
However, since I'm using one controller per gear, I no longer have to change this value once it's set.
Currently Firmware V312 is the most stable of the series, it has never crashed in my case.
Let's hope that Robert finds the anomaly in order to be able to use the option allowing to modify this value directly from the Windows application, it's still more pleasant.
Patrick
For information, I am testing a limited version of Firmware V317 sent to me by Robert.
The results are very promising. After more than an hour of testing, I failed to crash the controller. Everything worked perfectly.
Let's be patient, Robert is doing a great job and we will soon have a fully functional new Firmware.
Patrick