Difference between revisions of "626"
From Sensoray Technical Wiki
(building apps for 64-bit Windows) |
(→64-bit Windows: +new section: Encoder errors) |
||
| Line 1: | Line 1: | ||
==64-bit Windows== | ==64-bit Windows== | ||
| − | ''I successfully built a 626 program for my 64-bit Windows 7 system | + | :''I successfully built a 626 program for my 64-bit Windows 7 system but it crashes when it executes. What could be the problem?'' |
The 626 works with 64-bit Windows, but only with 32-bit applications. When building your application, make sure the CPU target is selected as 32-bit or Win32. | The 626 works with 64-bit Windows, but only with 32-bit applications. When building your application, make sure the CPU target is selected as 32-bit or Win32. | ||
| + | |||
| + | ==Encoder errors== | ||
| + | |||
| + | :''The encoder interface misses some encoder clocks, especially at higher rotation speeds.'' | ||
| + | |||
| + | This can be caused by slow slew rates on the encoder signals. Examine the encoder clock signals with an oscilloscope. If you don't see sharp, fast rise and fall times, you may need to add external termination or pull-up resistance to the clock lines to speed up the edges. | ||
Revision as of 09:14, 6 July 2016
64-bit Windows
- I successfully built a 626 program for my 64-bit Windows 7 system but it crashes when it executes. What could be the problem?
The 626 works with 64-bit Windows, but only with 32-bit applications. When building your application, make sure the CPU target is selected as 32-bit or Win32.
Encoder errors
- The encoder interface misses some encoder clocks, especially at higher rotation speeds.
This can be caused by slow slew rates on the encoder signals. Examine the encoder clock signals with an oscilloscope. If you don't see sharp, fast rise and fall times, you may need to add external termination or pull-up resistance to the clock lines to speed up the edges.