hello'
I connect my simple auto focuser with a stepper motor . driver TMC2209, arduino nano/
it works fine but the speed of the motor is very slow
how can I make it go faster?
the configuration set to FAST/
the file is :
// myFOCUSERPRO2 OFFICIAL FIRMWARE RELEASE 305
// TMC2225 DRIVER CHIP RUNNING ON DRV8825-HW203 BOARD
// (c) Copyright Robert Brown 2014-2021. All Rights Reserved.
// (c) Copyright Holger, 2019-2021. All Rights Reserved.
// (c) Copyright Paul Porters, 2020-2021. All rights reserved.
thank you very much
Ziv Arazi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
We are currently updating the TMC2225 and TMC2209 firmware for myFocuserPro2
You should be using the TMC2225 (tmc2xxx) firmware v330 for tmc 2205 chips
and
myFP2_TMC2209SG-330 for tmc2209 chips
Please email me at my account on yahoo or gmail for the latest firmware to try
The firmware file for tmc2xxxx has errors in it related to a number of things
see pdf Fine tuning the motorspeed
In the meantime
in file myBoards.h
the line
#defineDRVFAST6000//delaysformotorspeed
controls the main speed value.
Load windows app
connect to controller
set stepmode to full
set speed to fast
access Settings-Motorspeed-Set motorspeed value?
to make it go faster use a smaller number
so it it says 5000 change it to 4000 then click Set?
now test speed
If still too slow repeat above
When you have a good value then replace the value in the myBoards.h with the new value
make DRVMED twice that value
make DRVSLOW three times that value
Then please email me with your speed settings and the type/make/model of the stepper motor you have - I am trying to build up a database of steppers and speed setting so that in future firmware releases the values will be correct for most users.
Regards
Robert
Last edit: brownrb 2024-02-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good morning.
I have a similar problem. I have installed firmware version 330 for a TMC2209 and the ASCOM drivers for windows are not modified for fast speed. Yes, the Windows application does it (Not ASCOM).
Even if you modify the ASCOM driver configuration, it is always set to "slow".
I have the focuser connected to the fine adjustment of the telescope, so it is so slow that it is not operational.
Thanks and greetings
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are two things that can happen - where set on connect is used, or another reason
Make sure the send on connect tabs for windows and ascom driver are disabled and nothing is send when connecting. For Windows app - found on Connect tab. For ASCOM driver found on the Update-On-Connect tab
Run the Windows app. Enable messages on the Logging tab.
Connect to the controller.
On the Motor tab click on the Fast radio button, then click the Set button on top left of the form.
On the focuser tab, move 500 steps using the +500 or -500 buttons. Determine how fast the stepper is moving
Next, go back to the Motor tab and click the Slow radio button, then click the Set button on top left of the form.
On the focuser tab, move 500 steps using the +500 or -500 buttons. Is the motor running at a slower speed?
Next, go back the Motor tab click on the Fast radio button, then click the Set button on top left of the form.
Close the Windows app. Please send me the Messages log.
Another reason.
When a setting is changed, the focuser waits between 30 to 180 seconds before the change is saved in EEPROM.
If you make a change, then you need to wait till the settings are saved before the ccontroller is powered off, otherwise the settings will not be saved.
ASCOM DRIVER
The version should be v301. Settings can only sent when a connection is first made.
Start your client app like NINA, Select the ASCOM driver and click Properties
1. On the Connection tab click Trace On so it it checked
2. On the motor tab click Fast
3. On the Update On Connect tab click Motor
4. Go to the Connection tab and click Connect
Proceed to connect to the focuser and when connected in the application (like Nina), then disconnect and send me the trace file (will be in users document folder under ASCOM\Logs
Good morning.
I have a similar problem. I have installed firmware version 330 for a TMC2209 and the ASCOM drivers for windows are not modified for fast speed. Yes, the Windows application does it (Not ASCOM).
Even if you modify the ASCOM driver configuration, it is always set to "slow".
I have the focuser connected to the fine adjustment of the telescope, so it is so slow that it is not operational.
Thanks and greetings
Good afternoon.
I don't know why the fast function works now in the ASCOM 300 driver. This morning I did 1000 tests. I am sending you the log of version 300 and 290. The next thing is to see what happens with the mircosteps and autohoming, which does not work. It only works at 1/8 steps.
All the best
290 was deprecated, and only the latest versions on this site are supported, which at this time for the ASCOM driver is v301. Some older versions are on this site, because sometimes users want to use an older version, and I generally remove the older ones after a few months go by.
Any reports for versions less than the latest I will not assist with, because the later versions probably have already fixed the issue you may be experiencing.
The next thing is to see what happens with the mircosteps and autohoming, which does not work. It only works at 1/8 steps.
Not much I can say about. We all have different configurations and boards etc. Unless I can create the same environment as you, it will be sheer luck in finding the issue. I have a large collection of focuser types using different driver chips, displays etc. These help me in testing.
When reporting an issue, please consider that I need as much information as you can give me in order to find the needle in the haystack.
Information about what steps were done to create the problem, what app you were using at the time (ASCOM driver or Windows or INDI driver or Linus Application etc. And versions of all those. And the Board type DRVBRD type eg, DRV8825HW203KEYPAD as well as what are the enabled info from "focuserconfig.h"
I need that information so I can create a test bed to tryand replicate what you have.
So in terms of microstepping, a typical test goes like this
1. Start Windows App (2512), (screenshot of connection tab)
2. Click Logging tab and check Messages
3. Connect
4. Click on motor tab and click get button
5. take screenshot motor tab,
6. Select stepmode 1/4 stepping from dropdown list
7. Click Set button
8. Click get to determine if stepmode was changed
9. screenshot motor tab
10. Close connection and exit windows
11. Send me the screen shots, the Windows app log, focuserconfig.h file
I am more than happy to resolve your issues, and its best to give me 1 fault at a time, happyfor you to report more than 1 issue, but I will only work on 1 at a time, and move to the next issue only when the current (1st) is fixed. That is my preference (I am not good at multi-tasking - age deprives me of that now).
So I would like for you to first update eveything to the latest versions, including the Arduino IDE to 2.3,2
After updating try the microstepping mode using the Windows application with the test listed above. If the issue disappears because of the up to date version, then no need to report it, and then you can move on to the next issue of home.
For Home I would require much more info, are you using a home position switch, if that is tue, then have you tested the switch using the Windows application and what were the reported results - again enable messages logging, run the test, exit windows, send me the message log and screenshots (connection, motor, and focuser tabs)
Oh, I forgot to mention that there is a firmware update to v334 (probably next month) and a Windows application update, but lets focus on the latest versions availab;e on this site.
I will wait on your report back and I have slotted some time availability to look at the reported issues from you. I am happy if you would prefer to use email, you will find my gmai l or yah oo address in ascom driver, pdf, etc
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
290 was deprecated, and only the latest versions on this site are
supported, which at this time for the ASCOM driver is v301. Some older
versions are on this site, because sometimes users want to use an older
version, and I generally remove the older ones after a few months go by.
Any reports for versions less than the latest I will not assist with,
because the later versions probably have already fixed the issue you may be
experiencing.
The next thing is to see what happens with the mircosteps and autohoming,
which does not work. It only works at 1/8 steps.
Not much I can say about. We all have different configurations and boards
etc. Unless I can create the same environment as you, it will be sheer luck
in finding the issue. I have a large collection of focuser types using
different driver chips, displays etc. These help me in testing.
When reporting an issue, please consider that I need as much information
as you can give me in order to find the needle in the haystack.
Information about what steps were done to create the problem, what app you
were using at the time (ASCOM driver or Windows or INDI driver or Linus
Application etc. And versions of all those. And the Board type DRVBRD type
eg, DRV8825HW203KEYPAD as well as what are the enabled info from
"focuserconfig.h"
I need that information so I can create a test bed to tryand replicate
what you have.
So in terms of microstepping, a typical test goes like this
1. Start Windows App (2512), (screenshot of connection tab)
2. Click Logging tab and check Messages
3. Connect
4. Click on motor tab and click get button
5. take screenshot motor tab,
6. Select stepmode 1/4 stepping from dropdown list
7. Click Set button
8. Click get to determine if stepmode was changed
9. screenshot motor tab
10. Close connection and exit windows
11. Send me the screen shots, the Windows app log, focuserconfig.h file
I am more than happy to resolve your issues, and its best to give me 1
fault at a time, happyfor you to report more than 1 issue, but I will only
work on 1 at a time, and move to the next issue only when the current (1st)
is fixed. That is my preference (I am not good at multi-tasking - age
deprives me of that now).
So I would like for you to first update eveything to the latest versions,
including the Arduino IDE to 2.3,2
After updating try the microstepping mode using the Windows application
with the test listed above. If the issue disappears because of the up to
date version, then no need to report it, and then you can move on to the
next issue of home.
For Home I would require much more info, are you using a home position
switch, if that is tue, then have you tested the switch using the Windows
application and what were the reported results - again enable messages
logging, run the test, exit windows, send me the message log and
screenshots (connection, motor, and focuser tabs)
Oh, I forgot to mention that there is a firmware update to v334 (probably
next month) and a Windows application update, but lets focus on the latest
versions availab;e on this site.
I will wait on your report back and I have slotted some time availability
to look at the reported issues from you. I am happy if you would prefer to
use email, you will find my gmai l or yah oo address in ascom driver, pdf,
etc
Hi
Thank you for the info.
I have download the files and will look over them.
Briefly, the ASCOM log file says this
15:49:13.248 DriverInfo Get myFP2 ASCOM driver, R Brown
15:49:13.248 DriverVersion Get 3.0.0
which is incorrect. It should say
15:49:13.248 DriverInfo Get myFP2 ASCOM driver, R Brown
15:49:13.248 DriverVersion Get 3.0.1
Sometimes this can happen in Windows, where drivers are not deleted at the install or upgrade,
Please use control panel to delete the ASCOM myFP2ASCOM Driver 300
Open explorer and navigate to C:\Program Files (x86)\Common Files\ASCOM\Focuser
Delete any file or folder for myFP2, such as
ASCOM.myFP2ASCOM.Focuser.dll
folder myFP2
Next run the installer
myFP2ASCOMSetup301.exe
I see a few more things in the ascom log, but they might disappear when v301 is updated.
You will need to rerun the tests for the ascom driver to generate a new log file.
I will take a look at the other files as time permits.
What I noticed is that you have created a version that does not exist or supported in myFP2- merged a micro with tmc2209, then I guess you modified a firmware file to to try and make it go. Is my understanding correct?
Without looking at the firmwarem the pin connections do not correlate to the Nano-TMC2209
Without delving into the firmware, i would only assume that you have changed the
firmware of the TMC2209 to match your changes to the wiring, as the code from the Arduino files would not work otherwise. And since you are not using DIAG that means some things will not work.
i think that I have posted and written many times that I cannot support "changes to firmware made by others" (I am not talking changing pin numbers). I am happy to support the lastest firmware and apps posted by me. But it is not realistic to extend that to trying to support a new user board config that connects a tmc2209 and the micro.
Please let me know if you can resolve the ASCOM driver issues as outlined above.
Also, another suggestion
What version of TimerOne are you using?
it is found in the library.properties file
There are some versions that do not work - currently 1.1.1 works
Good afternoon.
First of all, I want to apologize because it is not my intention to waste your time.
In the firmware, I have only added a few lines, included in the DRV8825 version, so that the focuser with Micro can be connected to NINA and the pins, to reduce the size of the equipment (see photo).
One thing that interests me is what you mentioned about not using DIAG.
My knowledge is very limited (in my work I calculate metal structures...).
That said, if you see that I am very far from it working well, don't waste your time.
All the best
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
DIAG is the line which supports Home Position or Home Position using Stall guard.
In terms of complexity, using TMC2209 is probably the hardest and longest to get working.
The lines that I am more concerned with is UART on the left side. if you are using the code with little or no modifications, it will not work until (motor moving) until you get the wiring correct.
the firmware expects to communicate with the TMC2209 via UART (actually the PDN)
the chip has EN, MS1, MS2, and then PDN, so it is the PDN pin below MS2 (I believe you wired it using the pin below that)
reading your connection
A3=EN
A2=MS1
A1=MS2
but you have nothing on the next pin PDN
To make things confusing some diagrams show two pins as PDN
Your wiring from D15 to pin below is incorrect. it needs to be moved up 1 pin to
the PDN pin above.
It looks like you are trying to connect A0 and D15 to communicate with the TMC2209
I do not know if that will work . I do not have enough knowledge about the micro chip to say.
A0 - 1K resistor 1/4 watt - then to PDN
D15 - wired directly to PDN
infilemyBoardDefs.haddthefollowing(orreplaceifalreadythere)// TMC22xx definitions#defineTMCRX15// tmc2209 interface#defineTMCTXA0// tmc2209 interface#defineSTALL_VALUE40// [0... 255]#defineTMC2209CURRENT1000// 600mA for 8HS15-0604S NEMA8 stepper motor#defineTMC2209PORTSPEED57600// define tmc2209 serial speed, DO NOT CHANGE#defineTOFF_VALUE4// [1... 15]#defineDRIVER_ADDRESS0b00// TMC2209 Driver address according to MS1 and MS2#defineR_SENSE0.11f// Match to your driver// SilentStepStick series use 0.11// UltiMachine Einsy and Archim2 boards use 0.2// Panucatt BSD2660 uses 0.1// Watterott TMC5160 uses 0.075andinmyBoards.cppvoidDriverBoard::init_TMC2209(void){mystepper=newTMC2209Stepper(TMCRX,TMCTX,R_SENSE,DRIVER_ADDRESS);// Specify the serial interface to the tmc2209mystepper->beginSerial(TMC2209PORTSPEED);
The DIAG pin can be left off at this time. When u have it working then that is the time to revisit DIAG. This pin is used in two ways - to support Home Position Switch using a physical switch OT using Stall Guard. I would disable HOMEPOSITIONSWITCH in the focuserconfig.h file.
That should be enough to start/ The simpler method would be use the uln2003-28BYJ48 motor.
The TMC only has the quiet advantage and having build so many focusers over the years, it is not worth all the effort and cost.
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good morning
With the modification that you indicated in the code, the micro steps work perfectly!!!!!
Thank you so much!!!!
Having autohoming active is secondary, but it would be nice hahaha
Greetings and thanks for your time!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Carlos
Congratulations.
Stall guard is not easy and can take a week or more to get right. Using a scope is good, and the serial plotter - I think there is info on that in the zip file.
I think it is better to use a physical switch. Stall quard often needs adjustment when the weight of the imaging train changes.
And this has some info about using the spreadsheets and finding values for r_sense etc. A lot of proto code re stall guard
I would point out that the major portions of code was done by Paul Portes, and I have moved past the TMC chips so its probably not a good idea to ask me how it works as most of the info is no longer in my head.
Good morning.
I think I'm going to stay as I am, since my knowledge does not extend to understanding the spreadsheet.
Thanks again for your time
Greetings
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah, I did say that these tmc chips is probably the toughest to do.
If its running fine, I would advise to leave it as is for the time being.
If you start playing around with values it can suddenly stop working and try as one may try, its hard to get back to working again.
I know this from personal experience, many many times. It is easy to fall into the "what if I change" and then admit defeat before coming back to it a week or so later.
I do not know what stepper motor you are using.
That is essential to tune the driver to the stepper motor current
Most of these settings are in the tmcstepper_defines.h file, where they are copied into the controllerData settings so they can be altered later without repeogramming the controller/
// ----------------------------------------------------------------------// TMCxxxx DEFINES// ----------------------------------------------------------------------// These values are held in ControllerData and are managed using /admin7 HPSW page#defineSTALL_VALUE100// [0... 255]#defineTMC2209CURRENT600// 600mA for 8HS15-0604S NEMA8 stepper motor with tmc2209#defineTMC2225CURRENT300// 300mA for recommended stepper NEMA motor - you can change this - with tmc2225// These values do not change#defineTMC2225SPEED57600#defineTMC2209SPEED57600#defineTOFF_VALUE4// [1... 15]#defineR_SENSE0.11f// Match to your driver#defineDRIVER_ADDRESS0b00// TMC2209 Driver address according to MS1 and MS2#defineDRIVER_ADDRESSLGTM0b11// TMC2209 Driver address for LilyGo TM Motor#defineLGTM_SW_RX26// LiLyGo T-Motor SoftwareSerial receive pin#defineLGTM_SW_TX27// LiLyGo T-Motor SoftwareSerial transmit pin
These are the important ones
#define STALL_VALUE 100 // [0... 255]
#define TMC2209CURRENT 600 // 600mA for 8HS15-0604S NEMA8 stepper motor with tmc2209
#define TOFF_VALUE 4 // [1... 15]
#define R_SENSE 0.11f // Match to your driver
TMC2209CURRENT you can get from the stepper motor sheet that comes with the stepper motor.
R_SENSE and TOFF_VALUE come from the spreadsheet
STALL_VALUE you can only determine when the stepper is running, trial and error to set the STALL value. If you do not use STALL GUARD then this value can be anything 0-255
regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good afternoon
This is the engine I am using.
As you say, for now I'll leave it as it is, but if I know myself... it
won't take me long to change things hahaha
I'm going to look at the excel file and see if I can understand it.
All the best
Yeah, I did say that these tmc chips is probably the toughest to do.
If its running fine, I would advise to leave it as is for the time being.
If you start playing around with values it can suddenly stop working and
try as one may try, its hard to get back to working again.
I know this from personal experience, many many times. It is easy to fall
into the "what if I change" and then admit defeat before coming back to it
a week or so later.
I do not know what stepper motor you are using.
That is essential to tune the driver to the stepper motor current
Most of these settings are in the tmcstepper_defines.h file, where they
are copied into the controllerData settings so they can be altered later
without repeogramming the controller/
// ----------------------------------------------------------------------// TMCxxxx DEFINES// ----------------------------------------------------------------------// These values are held in ControllerData and are managed using /admin7 HPSW page#define STALL_VALUE 100 // [0... 255]
define TMC2209CURRENT 600 // 600mA for 8HS15-0604S NEMA8 stepper motor with tmc2209#define TMC2225CURRENT 300 // 300mA for recommended stepper NEMA motor - you can change this - with tmc2225
// These values do not change#define TMC2225SPEED 57600#define TMC2209SPEED 57600
define TOFF_VALUE 4 // [1... 15]#define R_SENSE 0.11f // Match to your driver#define DRIVER_ADDRESS 0b00 // TMC2209 Driver address according to MS1 and MS2#define DRIVER_ADDRESSLGTM 0b11 // TMC2209 Driver address for LilyGo TM Motor#define LGTM_SW_RX 26 // LiLyGo T-Motor SoftwareSerial receive pin#define LGTM_SW_TX 27 // LiLyGo T-Motor SoftwareSerial transmit pin
These are the important ones
define STALL_VALUE 100 // [0... 255]#define TMC2209CURRENT 600 // 600mA for 8HS15-0604S NEMA8 stepper motor with tmc2209#define TOFF_VALUE 4 // [1... 15]#define R_SENSE 0.11f // Match to your driver
TMC2209CURRENT you can get from the stepper motor sheet that comes with
the stepper motor.
R_SENSE and TOFF_VALUE come from the spreadsheet
STALL_VALUE you can only determine when the stepper is running, trial and
error to set the STALL value. If you do not use STALL GUARD then this value
can be anything 0-255
hello'
I connect my simple auto focuser with a stepper motor . driver TMC2209, arduino nano/
it works fine but the speed of the motor is very slow
how can I make it go faster?
the configuration set to FAST/
the file is :
// myFOCUSERPRO2 OFFICIAL FIRMWARE RELEASE 305
// TMC2225 DRIVER CHIP RUNNING ON DRV8825-HW203 BOARD
// (c) Copyright Robert Brown 2014-2021. All Rights Reserved.
// (c) Copyright Holger, 2019-2021. All Rights Reserved.
// (c) Copyright Paul Porters, 2020-2021. All rights reserved.
thank you very much
Ziv Arazi
Hi
For firmware, as above, myFOCUSERPRO2 OFFICIAL FIRMWARE RELEASE 305
is not supported.
Latest version is 330
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/ARDUINO%20FIRMWARE/myFP2-Firmware-330.zip/download
Regards
Robert
Hi
We are currently updating the TMC2225 and TMC2209 firmware for myFocuserPro2
You should be using the TMC2225 (tmc2xxx) firmware v330 for tmc 2205 chips
and
myFP2_TMC2209SG-330 for tmc2209 chips
Please email me at my account on yahoo or gmail for the latest firmware to try
The firmware file for tmc2xxxx has errors in it related to a number of things
see pdf Fine tuning the motorspeed
In the meantime
in file myBoards.h
the line
controls the main speed value.
Load windows app
connect to controller
set stepmode to full
set speed to fast
access Settings-Motorspeed-Set motorspeed value?
to make it go faster use a smaller number
so it it says 5000 change it to 4000 then click Set?
now test speed
If still too slow repeat above
When you have a good value then replace the value in the myBoards.h with the new value
make DRVMED twice that value
make DRVSLOW three times that value
Then please email me with your speed settings and the type/make/model of the stepper motor you have - I am trying to build up a database of steppers and speed setting so that in future firmware releases the values will be correct for most users.
Regards
Robert
Last edit: brownrb 2024-02-28
Good morning.
I have a similar problem. I have installed firmware version 330 for a TMC2209 and the ASCOM drivers for windows are not modified for fast speed. Yes, the Windows application does it (Not ASCOM).
Even if you modify the ASCOM driver configuration, it is always set to "slow".
I have the focuser connected to the fine adjustment of the telescope, so it is so slow that it is not operational.
Thanks and greetings
Hi
There are two things that can happen - where set on connect is used, or another reason
Make sure the send on connect tabs for windows and ascom driver are disabled and nothing is send when connecting. For Windows app - found on Connect tab. For ASCOM driver found on the Update-On-Connect tab
Run the Windows app. Enable messages on the Logging tab.
Connect to the controller.
On the Motor tab click on the Fast radio button, then click the Set button on top left of the form.
On the focuser tab, move 500 steps using the +500 or -500 buttons. Determine how fast the stepper is moving
Next, go back to the Motor tab and click the Slow radio button, then click the Set button on top left of the form.
On the focuser tab, move 500 steps using the +500 or -500 buttons. Is the motor running at a slower speed?
Next, go back the Motor tab click on the Fast radio button, then click the Set button on top left of the form.
Close the Windows app. Please send me the Messages log.
Another reason.
When a setting is changed, the focuser waits between 30 to 180 seconds before the change is saved in EEPROM.
If you make a change, then you need to wait till the settings are saved before the ccontroller is powered off, otherwise the settings will not be saved.
ASCOM DRIVER
The version should be v301. Settings can only sent when a connection is first made.
Start your client app like NINA, Select the ASCOM driver and click Properties
1. On the Connection tab click Trace On so it it checked
2. On the motor tab click Fast
3. On the Update On Connect tab click Motor
4. Go to the Connection tab and click Connect
Proceed to connect to the focuser and when connected in the application (like Nina), then disconnect and send me the trace file (will be in users document folder under ASCOM\Logs
and send me the trace log also.
regards
Robert
On Wednesday, February 21, 2024 at 10:53:31 PM GMT+13, Carlos Izquierdo Vázquez carlosizquierdo@users.sourceforge.net wrote:
Good morning.
I have a similar problem. I have installed firmware version 330 for a TMC2209 and the ASCOM drivers for windows are not modified for fast speed. Yes, the Windows application does it (Not ASCOM).
Even if you modify the ASCOM driver configuration, it is always set to "slow".
I have the focuser connected to the fine adjustment of the telescope, so it is so slow that it is not operational.
Thanks and greetings
TMC 2209 motor spees
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/arduinoascomfocuserpro2diy/discussion/general/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Good afternoon.
I don't know why the fast function works now in the ASCOM 300 driver. This morning I did 1000 tests. I am sending you the log of version 300 and 290. The next thing is to see what happens with the mircosteps and autohoming, which does not work. It only works at 1/8 steps.
All the best
Hi Carlos
290 was deprecated, and only the latest versions on this site are supported, which at this time for the ASCOM driver is v301. Some older versions are on this site, because sometimes users want to use an older version, and I generally remove the older ones after a few months go by.
Any reports for versions less than the latest I will not assist with, because the later versions probably have already fixed the issue you may be experiencing.
Please update using the following links
ASCOM DRIVER 301
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/ASCOM%20DRIVERS/1st%20Driver/myFP2ASCOMSetup301.exe/download
FIRMWARE 330
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/ARDUINO%20FIRMWARE/myFP2-Firmware-330.zip/download
WINDOWS 2551
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/WINDOWS/MainApp/
Not much I can say about. We all have different configurations and boards etc. Unless I can create the same environment as you, it will be sheer luck in finding the issue. I have a large collection of focuser types using different driver chips, displays etc. These help me in testing.
When reporting an issue, please consider that I need as much information as you can give me in order to find the needle in the haystack.
Information about what steps were done to create the problem, what app you were using at the time (ASCOM driver or Windows or INDI driver or Linus Application etc. And versions of all those. And the Board type DRVBRD type eg, DRV8825HW203KEYPAD as well as what are the enabled info from "focuserconfig.h"
I need that information so I can create a test bed to tryand replicate what you have.
So in terms of microstepping, a typical test goes like this
1. Start Windows App (2512), (screenshot of connection tab)
2. Click Logging tab and check Messages
3. Connect
4. Click on motor tab and click get button
5. take screenshot motor tab,
6. Select stepmode 1/4 stepping from dropdown list
7. Click Set button
8. Click get to determine if stepmode was changed
9. screenshot motor tab
10. Close connection and exit windows
11. Send me the screen shots, the Windows app log, focuserconfig.h file
I am more than happy to resolve your issues, and its best to give me 1 fault at a time, happyfor you to report more than 1 issue, but I will only work on 1 at a time, and move to the next issue only when the current (1st) is fixed. That is my preference (I am not good at multi-tasking - age deprives me of that now).
So I would like for you to first update eveything to the latest versions, including the Arduino IDE to 2.3,2
After updating try the microstepping mode using the Windows application with the test listed above. If the issue disappears because of the up to date version, then no need to report it, and then you can move on to the next issue of home.
For Home I would require much more info, are you using a home position switch, if that is tue, then have you tested the switch using the Windows application and what were the reported results - again enable messages logging, run the test, exit windows, send me the message log and screenshots (connection, motor, and focuser tabs)
Oh, I forgot to mention that there is a firmware update to v334 (probably next month) and a Windows application update, but lets focus on the latest versions availab;e on this site.
I will wait on your report back and I have slotted some time availability to look at the reported issues from you. I am happy if you would prefer to use email, you will find my gmai l or yah oo address in ascom driver, pdf, etc
regards
Robert
Good afternoon.
I send you the following information:
Connection diagram
Photo of the assembly
Modified firmware
log and screenshots
Photo of the set
I hope it helps you
Greetings
El vie, 23 feb 2024 a las 5:29, brownrb (brownrb@users.sourceforge.net)
escribió:
Hi
Thank you for the info.
I have download the files and will look over them.
Briefly, the ASCOM log file says this
15:49:13.248 DriverInfo Get myFP2 ASCOM driver, R Brown
15:49:13.248 DriverVersion Get 3.0.0
which is incorrect. It should say
15:49:13.248 DriverInfo Get myFP2 ASCOM driver, R Brown
15:49:13.248 DriverVersion Get 3.0.1
Sometimes this can happen in Windows, where drivers are not deleted at the install or upgrade,
ASCOM.myFP2ASCOM.Focuser.dll
folder myFP2
Next run the installer
myFP2ASCOMSetup301.exe
I see a few more things in the ascom log, but they might disappear when v301 is updated.
You will need to rerun the tests for the ascom driver to generate a new log file.
I will take a look at the other files as time permits.
What I noticed is that you have created a version that does not exist or supported in myFP2- merged a micro with tmc2209, then I guess you modified a firmware file to to try and make it go. Is my understanding correct?
Without looking at the firmwarem the pin connections do not correlate to the Nano-TMC2209
This is what I see
Without delving into the firmware, i would only assume that you have changed the
firmware of the TMC2209 to match your changes to the wiring, as the code from the Arduino files would not work otherwise. And since you are not using DIAG that means some things will not work.
i think that I have posted and written many times that I cannot support "changes to firmware made by others" (I am not talking changing pin numbers). I am happy to support the lastest firmware and apps posted by me. But it is not realistic to extend that to trying to support a new user board config that connects a tmc2209 and the micro.
Please let me know if you can resolve the ASCOM driver issues as outlined above.
Also, another suggestion
What version of TimerOne are you using?
it is found in the library.properties file
There are some versions that do not work - currently 1.1.1 works
regards
Robert
Good afternoon.
First of all, I want to apologize because it is not my intention to waste your time.
In the firmware, I have only added a few lines, included in the DRV8825 version, so that the focuser with Micro can be connected to NINA and the pins, to reduce the size of the equipment (see photo).
One thing that interests me is what you mentioned about not using DIAG.
My knowledge is very limited (in my work I calculate metal structures...).
That said, if you see that I am very far from it working well, don't waste your time.
All the best
Hi
DIAG is the line which supports Home Position or Home Position using Stall guard.
In terms of complexity, using TMC2209 is probably the hardest and longest to get working.
The lines that I am more concerned with is UART on the left side. if you are using the code with little or no modifications, it will not work until (motor moving) until you get the wiring correct.
the firmware expects to communicate with the TMC2209 via UART (actually the PDN)
the chip has EN, MS1, MS2, and then PDN, so it is the PDN pin below MS2 (I believe you wired it using the pin below that)
reading your connection
A3=EN
A2=MS1
A1=MS2
but you have nothing on the next pin PDN
To make things confusing some diagrams show two pins as PDN
Your wiring from D15 to pin below is incorrect. it needs to be moved up 1 pin to
the PDN pin above.
It looks like you are trying to connect A0 and D15 to communicate with the TMC2209
I do not know if that will work . I do not have enough knowledge about the micro chip to say.
A0 - 1K resistor 1/4 watt - then to PDN
D15 - wired directly to PDN
The DIAG pin can be left off at this time. When u have it working then that is the time to revisit DIAG. This pin is used in two ways - to support Home Position Switch using a physical switch OT using Stall Guard. I would disable HOMEPOSITIONSWITCH in the focuserconfig.h file.
That should be enough to start/ The simpler method would be use the uln2003-28BYJ48 motor.
The TMC only has the quiet advantage and having build so many focusers over the years, it is not worth all the effort and cost.
regards
Robert
Good morning
With the modification that you indicated in the code, the micro steps work perfectly!!!!!
Thank you so much!!!!
Having autohoming active is secondary, but it would be nice hahaha
Greetings and thanks for your time!
Hi Carlos
Congratulations.
Stall guard is not easy and can take a week or more to get right. Using a scope is good, and the serial plotter - I think there is info on that in the zip file.
I think it is better to use a physical switch. Stall quard often needs adjustment when the weight of the imaging train changes.
These links may be of use for future.
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/Documentation/myFP2-TRINAMIC-09-4.pdf/download
And this has some info about using the spreadsheets and finding values for r_sense etc. A lot of proto code re stall guard
I would point out that the major portions of code was done by Paul Portes, and I have moved past the TMC chips so its probably not a good idea to ask me how it works as most of the info is no longer in my head.
Regards
Robert
https://drive.google.com/file/d/19xoqGwpSGroUisFtbL7L1nfSREVIGDwt/view?usp=drive_link
Good morning.
I think I'm going to stay as I am, since my knowledge does not extend to understanding the spreadsheet.
Thanks again for your time
Greetings
Yeah, I did say that these tmc chips is probably the toughest to do.
If its running fine, I would advise to leave it as is for the time being.
If you start playing around with values it can suddenly stop working and try as one may try, its hard to get back to working again.
I know this from personal experience, many many times. It is easy to fall into the "what if I change" and then admit defeat before coming back to it a week or so later.
I do not know what stepper motor you are using.
That is essential to tune the driver to the stepper motor current
Most of these settings are in the tmcstepper_defines.h file, where they are copied into the controllerData settings so they can be altered later without repeogramming the controller/
These are the important ones
TMC2209CURRENT you can get from the stepper motor sheet that comes with the stepper motor.
R_SENSE and TOFF_VALUE come from the spreadsheet
STALL_VALUE you can only determine when the stepper is running, trial and error to set the STALL value. If you do not use STALL GUARD then this value can be anything 0-255
regards
Robert
[image: image.png]
Good afternoon
This is the engine I am using.
As you say, for now I'll leave it as it is, but if I know myself... it
won't take me long to change things hahaha
I'm going to look at the excel file and see if I can understand it.
All the best
El mar, 5 mar 2024 a las 14:13, brownrb (brownrb@users.sourceforge.net)
escribió: