I am using this focuser for at least two and a half years and everything is awesome, but yesterday i have decided to upgrade to the latest version 306-07 with a clean install i have observed that the function "Coil Power Status OFF - Controller enables coil power, moves motor, after 30s elapsed releases power to motor " / "releasemotor" does not work as expected meaning the driverboard remains powered on all the time, even if the "Coil Power is enabled or disabled" so my motor gets very hot.
I want to mention that with the older version everything went well, but i don't remember the firmware version.
I am using DRVBRD: PRO2ESP32ULN2003 with stepper 28BYJ-48 bit the stepper controller board is ULN2003a (the blue one, not the green one if it matters).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am currently working on the next release, as time permits
ASCOM driver 303
Firmware 310-04
Windows app 3_0_0_5
which resolves a significant number of fixes etc, across all 3 of above
case 11: // get coil power enable
case 12: // set coil power enable
I mention this from the firmware file, in tcpip_server.cpp
To find out about coil power. you can use the Windows app,
start the windows app
enable logging
connect to the controller
on the Motor tab, click the get button (top right).
Click the Coil Power Enable chkbox once. This should change its state.
Now click the Set button which sends the command to the controller
After 30s of waiting once a control has changed state it will be saved
into non-volatile memory. What that means is that when a setting is changed the changed state for that control is saved ONCE 30s has elapsed. If power goes off to the controller,or a rest, then the value is not saved because 30s did not elapse between the state change the of power off/reboot and this was not saved.
Now close the application and please post the log file. All of it, please do not trim or truncate the log file.
If you forgot whare the log file was stored, use the settings menu (log files) to find the folder of the log files.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I want to mention that when the board started, the motor driver board was not energized and did not energize after enabling the CoilPower.
I also did a +500 steps from the windws app to enable the motor driver board and i have observed that the motor did not move it only buzzed a little. But from the push buttons everything went as expected, did i do something wrong?
Release coil power will only work if Park is enabled.
So enable park using the Management Server
from the firmware inside loop()
// park controls coil power off and display off after elapsed 30s following a move// if park is enabled, 30s after a move ends, coilpower(if enabled) and display get turned off// if park is not enabled, state of coilpower and display are not altered
Reading on. I have identifed the error you discovered. There is a fix in the next release. In the meantime if you enable Park then it should work for you as is.
The steps to do are, from Management Server
Enable Park
Disable Coil Power
Last edit: brownrb 2023-12-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The next release (all ascom, firmware, win app etc) has been released to the test group. Barring unforseen issues, this means when any issues are found, then it is likely that the public release is likely in a week or two.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thank you so much for such a fast support :) somehow i did not make a connection because i did not found all the comments you have provided above. I will follow the steps.
is there any way to lower the time ? last time i have found the parameter, but now i cannot pin point it. Somehow i find that 30s it is too much to keep the motor energized.
Last edit: Razvan 2023-12-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
// DELAY TIME BEFORE CHANGES ARE WRITTEN TO SPIFFS FILE
#defineDEFAULTSAVETIME600// 600 timeslices, 10 timeslices per second = 600 / 10 = 60 seconds
be careful making it too small. This saves the controller settings to flash memory, which has a limited write cycles, if too may then flash memory errors will begin to occur when writing to flash, and then one musy replace esp32 chip.
Consider when doing an auto focus, which starts, moves, stops - there are a few changes, but they add up. One cannot just save a setting setting, rather most settings are saved at every save (even for thos settings that have not changed - because flash is managed as blocks -
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
was this resolved in the 311 release as I am using 311 and my coil power will not release even if park is enabled. motor is the ULN2003 and gets quite warm
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
Thank you for this great project 🙂
I am using this focuser for at least two and a half years and everything is awesome, but yesterday i have decided to upgrade to the latest version 306-07 with a clean install i have observed that the function "Coil Power Status OFF - Controller enables coil power, moves motor, after 30s elapsed releases power to motor " / "releasemotor" does not work as expected meaning the driverboard remains powered on all the time, even if the "Coil Power is enabled or disabled" so my motor gets very hot.
I want to mention that with the older version everything went well, but i don't remember the firmware version.
I am using DRVBRD: PRO2ESP32ULN2003 with stepper 28BYJ-48 bit the stepper controller board is ULN2003a (the blue one, not the green one if it matters).
Hi Razvan
I am currently working on the next release, as time permits
ASCOM driver 303
Firmware 310-04
Windows app 3_0_0_5
which resolves a significant number of fixes etc, across all 3 of above
case 11: // get coil power enable
case 12: // set coil power enable
I mention this from the firmware file, in tcpip_server.cpp
To find out about coil power. you can use the Windows app,
start the windows app
enable logging
connect to the controller
on the Motor tab, click the get button (top right).
Click the Coil Power Enable chkbox once. This should change its state.
Now click the Set button which sends the command to the controller
After 30s of waiting once a control has changed state it will be saved
into non-volatile memory. What that means is that when a setting is changed the changed state for that control is saved ONCE 30s has elapsed. If power goes off to the controller,or a rest, then the value is not saved because 30s did not elapse between the state change the of power off/reboot and this was not saved.
Now close the application and please post the log file. All of it, please do not trim or truncate the log file.
If you forgot whare the log file was stored, use the settings menu (log files) to find the folder of the log files.
Regards
Robert
Hi Robert,
Followed your steps and attached the log file.
I want to mention that when the board started, the motor driver board was not energized and did not energize after enabling the CoilPower.
I also did a +500 steps from the windws app to enable the motor driver board and i have observed that the motor did not move it only buzzed a little. But from the push buttons everything went as expected, did i do something wrong?
Thank you,
Razvan
Nope, as I said the files are causing issues.
Hopefully I will complete the next update soon. There will be new "everything"
Release coil power will only work if Park is enabled.
So enable park using the Management Server
from the firmware inside loop()
Reading on. I have identifed the error you discovered. There is a fix in the next release. In the meantime if you enable Park then it should work for you as is.
The steps to do are, from Management Server
Enable Park
Disable Coil Power
Last edit: brownrb 2023-12-19
The next release (all ascom, firmware, win app etc) has been released to the test group. Barring unforseen issues, this means when any issues are found, then it is likely that the public release is likely in a week or two.
Regards
Robert
thank you so much for such a fast support :) somehow i did not make a connection because i did not found all the comments you have provided above. I will follow the steps.
is there any way to lower the time ? last time i have found the parameter, but now i cannot pin point it. Somehow i find that 30s it is too much to keep the motor energized.
Last edit: Razvan 2023-12-27
in controller_defines.h
be careful making it too small. This saves the controller settings to flash memory, which has a limited write cycles, if too may then flash memory errors will begin to occur when writing to flash, and then one musy replace esp32 chip.
Consider when doing an auto focus, which starts, moves, stops - there are a few changes, but they add up. One cannot just save a setting setting, rather most settings are saved at every save (even for thos settings that have not changed - because flash is managed as blocks -
Regards
Robert
was this resolved in the 311 release as I am using 311 and my coil power will not release even if park is enabled. motor is the ULN2003 and gets quite warm
No, 311 has that issue, and I am still making changes to 312.
In the meantime, for v311 you can make this change
file
myfp2esp32_311-02.ino
line
1750-1753
change
// handle coil-power
if (ControllerData->get_coilpower_enable() == V_NOTENABLED) {
driverboard->releasemotor();
}
to
// handle coil-power
//if (ControllerData->get_coilpower_enable() == V_NOTENABLED) {
driverboard->releasemotor();
//}
so that only the line driverboard line is left
thansk for the quick response Robert but it didnt make any difference. i have attached the log and my ino
logfile
This is what I get from the log file
OFF
10/06/2024 17:24:09: SetMotorSettingsbtn_Click Write Coil power
10/06/2024 17:24:09: Write_coilpower START
10/06/2024 17:24:09: Write_coilpower Connected
10/06/2024 17:24:09: SendString START
10/06/2024 17:24:09: SendString sending :120# to client
10/06/2024 17:24:09: SendString END
OFF
10/06/2024 17:24:14: Read_coilpower START
10/06/2024 17:24:14: Read_coilpower Connected
10/06/2024 17:24:14: SendString START
10/06/2024 17:24:14: SendString sending :11# to client
10/06/2024 17:24:14: SendString END
10/06/2024 17:24:14: ReceiveResponse START
10/06/2024 17:24:14: ReceiveResponse Check if client is connected
10/06/2024 17:24:14: ReceiveResponse Client is connected
10/06/2024 17:24:14: ReceiveResponse Check for incoming data
10/06/2024 17:24:14: ReceiveResponse Incoming data was:3
10/06/2024 17:24:14: Read_coilpower response = 0
OFF
10/06/2024 17:26:52: Getallvalues Get Coil power
10/06/2024 17:26:52: Read_coilpower START
10/06/2024 17:26:52: Read_coilpower Connected
10/06/2024 17:26:52: SendString START
10/06/2024 17:26:52: SendString sending :11# to client
10/06/2024 17:26:52: SendString END
10/06/2024 17:26:52: ReceiveResponse START
10/06/2024 17:26:52: ReceiveResponse Check if client is connected
10/06/2024 17:26:52: ReceiveResponse Client is connected
10/06/2024 17:26:52: ReceiveResponse Check for incoming data
10/06/2024 17:26:52: ReceiveResponse Incoming data was:3
10/06/2024 17:26:52: Read_coilpower response = 0
OFF
10/06/2024 17:26:52: Getstaticvalues Get Coil Power
10/06/2024 17:26:52: Read_coilpower START
10/06/2024 17:26:52: Read_coilpower Connected
10/06/2024 17:26:52: SendString START
10/06/2024 17:26:52: SendString sending :11# to client
10/06/2024 17:26:52: SendString END
10/06/2024 17:26:52: ReceiveResponse START
10/06/2024 17:26:52: ReceiveResponse Check if client is connected
10/06/2024 17:26:52: ReceiveResponse Client is connected
10/06/2024 17:26:52: ReceiveResponse Check for incoming data
10/06/2024 17:26:52: ReceiveResponse Incoming data was:3
10/06/2024 17:26:52: Read_coilpower response = 0
ON
10/06/2024 17:28:03: SetMotorSettingsbtn_Click Write Coil power
10/06/2024 17:28:03: Write_coilpower START
10/06/2024 17:28:03: Write_coilpower Connected
10/06/2024 17:28:03: SendString START
10/06/2024 17:28:03: SendString sending :121# to client
10/06/2024 17:28:03: SendString END
OFF
10/06/2024 17:28:50: Write_coilpower START
10/06/2024 17:28:50: Write_coilpower Connected
10/06/2024 17:28:50: SendString START
10/06/2024 17:28:50: SendString sending :120# to client
10/06/2024 17:28:50: SendString END
So the log is showing that the coil power is turning off
What are the indications as to why you think that coil power is on?
regards
Robert
no rush tbh i canwait until 312 is out, so much other stuff to do
"So the log is showing that the coil power is turning off
What are the indications as to why you think that coil power is on?"
the power leds on the board stay on and the motor gets V Hot