Hi,
I finally managed to get the resolution down into my my motor driver. It was an interesting
experience. It was NOT enough to implement writeFloat64(). The resolution did not arrive.
I had it print to me what it was doing and this was interesting:
- On initialization I got a code motorEncResolution_ with infinity value. Obviously not yet initialized.
- No motorResolution_
- When I tried to manually set MRES, I received motorPosition_ function codes with a newly calculated
position. No motorResolution_.
I had to use Giles Knap suggestion with the additional DB field too in order to achieve success. And even
there: MOTOR_REC_RESOLUTION was unknown, I had to change it to MOTOR_RESOLUTION in
the OUT field. Probably a version issue.
This exhibited some surprising (to me) features. Or shall I call it bugs?
Thanks and Best Regards,
Mark Koennecke
- Replies:
- RE: asynMotorAxis Mark Rivers via Tech-talk
- Navigate by Date:
- Prev:
Re: Standard RTEMS NFSv3 client Heinz Junkes via Tech-talk
- Next:
RE: asynMotorAxis Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
asynMotorAxis Koennecke Mark (PSI) via Tech-talk
- Next:
RE: asynMotorAxis Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|