Hi all,
I found, that in recent firmware versions (1.31) of the MAXv cards the
command to set
negative encoder resolutions (e.g. "AX ER-2,3") as used by the MAXv driver
does not work any more.
Instead a command error is returned and the encoder resolution will remain
unchanged.
I couldn't find this "new feature" documented anywhere.
For the MAXp-card I verified, that this behaviour was introduced between
firmware versions 1.29 and 1.31.
The workaround is to not use negative encoder resolution, instead reverse
the encoder direction
with the new EDI command in the init-string.
-------
If using RTEMS the ioc crashes, when calling sprintf in interrupt context
(motorIsr() in drvMAXv.cc) .
I assume, calling sprintf() in interrupt context is not allowed in RTEMS?
Jens
- Replies:
- Re: 2 MAXv problems Ron Sluiter
- Re: 2 MAXv problems Joachim Rahn
- Navigate by Date:
- Prev:
Re: compile error with medm 3.1.3 on fedora 10 Robert Soliday
- Next:
Re: MBBO update Hinko Kocevar
- 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:
Re: ChannelArchiver on Solaris? Matthias Clausen
- Next:
Re: 2 MAXv problems Ron Sluiter
- 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
|