1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
|
= Pluto P Driver
[[cha:pluto-p-driver]] (((Pluto P Driver)))
////
ATTENTION TRANSLATORS before translating this document copy the base document
into this copy to get the latest version. Untranslated documents are not kept
up to date with the English documents.
Do not translate anchors or links, translate only the text of a link after the
comma.
Anchor [[anchor-name]]
Link <<anchor-name,text after the comma can be translated>>
Make sure the documents build after translating.
////
== General Info
The Pluto-P is a FPGA board featuring the
ACEX1K(((ACEX1K))) chip from Altera.
=== Requirements
. A Pluto-P board
. An EPP-compatible parallel port, configured for EPP mode in the system BIOS
or a PCI EPP compatible parallel port card.
[NOTE]
The Pluto P board requires EPP mode. Netmos98xx chips do not work in EPP mode.
The Pluto P board will work on some computers and not on others.
There is no known pattern to which computers work and which don't work.
For more information on PCI EPP compatible parallel port cards see the
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?LinuxCNC_Supported_Hardware[LinuxCNC
Supported Hardware] page on the wiki.
=== Connectors
* The Pluto-P board is shipped with the left connector presoldered, with
the key in the indicated position. The other connectors are
unpopulated. There does not seem to be a standard 12-pin IDC connector,
but some of the pins of a 16P connector can hang off the board next to
QA3/QZ3.
* The bottom and right connectors are on the same .1" grid, but the left
connector is not. If OUT2…OUT9 are not required, a single IDC connector
can span the bottom connector and the bottom two rows of the right
connector.
=== Physical Pins
* Read the ACEX1K datasheet for information about input and output
voltage thresholds. The pins are all configured in 'LVTTL/LVCMOS' mode
and are generally compatible with 5V TTL logic.
* Before configuration and after properly exiting LinuxCNC, all Pluto-P pins
are tristated with weak pull-ups (20k-ohms min, 50k-ohms max). If the
watchdog timer is enabled (the default),
these pins are also tristated after an interruption of communication
between LinuxCNC and the board. The watchdog timer takes approximately
6.5ms to activate. However, software bugs in the pluto_servo firmware
or LinuxCNC can leave the Pluto-P pins in an undefined state.
* In pwm+dir mode, by default dir is HIGH for negative values and LOW
for positive values. To select HIGH for positive values and LOW for
negative values, set the corresponding dout-NN-invert parameter TRUE to
invert the signal.
* The index input is triggered on the rising edge. Initial testing has
shown that the QZx inputs are particularly noise sensitive, due to
being polled every 25ns. Digital filtering has been added to filter
pulses shorter than 175ns (seven polling times). Additional external
filtering on all input pins, such as a Schmitt buffer or inverter, RC
filter, or differential receiver (if applicable) is recommended.
* The IN1…IN7 pins have 22-ohm series resistors to their associated FPGA
pins. No other pins have any sort of protection for out-of-spec
voltages or currents. It is up to the integrator to add appropriate
isolation and protection. Traditional parallel port optoisolator boards
do not work with pluto_servo due to the bidirectional nature of the EPP
protocol.
=== LED
* When the device is unprogrammed, the LED glows faintly. When the
device is programmed, the LED glows according to the duty cycle of PWM0
('LED' = 'UP0' 'xor' 'DOWN0') or STEPGEN0 ('LED' = 'STEP0' 'xor'
'DIR0').
=== Power
* A small amount of current may be drawn from VCC. The available current
depends on the unregulated DC input to the board. Alternately,
regulated +3.3VDC may be supplied to the FPGA through these VCC pins.
The required current is not yet known, but is probably around 50mA plus
I/O current.
* The regulator on the Pluto-P board is a low-dropout type. Supplying 5V
at the power jack will allow the regulator to work properly.
=== PC interface
* Only a single pluto_servo or pluto_step board is supported.
=== Rebuilding the FPGA firmware
The 'src/hal/drivers/pluto_servo_firmware/' and
'src/hal/drivers/pluto_step_firmware/' subdirectories contain the
Verilog source code plus additional files
used by Quartus for the FPGA firmwares. Altera's Quartus II software is
required to rebuild the FPGA firmware. To rebuild the firmware from the
.hdl and other source files, open the '.qpf' file and press CTRL-L.
Then, recompile LinuxCNC.
Like the HAL hardware driver, the FPGA firmware is licensed under the
terms of the GNU General Public License.
The gratis version of Quartus II runs only on Microsoft Windows,
although there is apparently a paid version that runs on Linux.
=== For more information
Some additional information about it is available from
http://www.knjn.com/FPGA-Parallel.html[KNJC LLC]
and from http://emergent.unpy.net/01165081407[the developer's blog].
== Pluto Servo[[sec:pluto-servo]](((pluto-servo)))
The pluto_servo system is suitable for control of a 4-axis CNC mill
with servo motors, a 3-axis mill with PWM spindle control, a lathe with
spindle encoder, etc. The large number of inputs allows a full set of
limit switches.
This driver features:
* 4 quadrature channels with 40MHz sample rate. The counters operate in
'4x' mode. The maximum useful quadrature rate is 8191 counts per LinuxCNC
servo cycle, or about 8MHz for LinuxCNC's default 1ms servo rate.
* 4 PWM channels, 'up/down' or 'pwm+dir' style. 4095 duty cycles from
-100% to +100%, including 0%. The PWM period is approximately 19.5kHz
(40MHz / 2047). A PDM-like mode is also available.
* 18 digital outputs: 10 dedicated, 8 shared with PWM functions.
(Example: A lathe with unidirectional PWM spindle control may use 13
total digital outputs)
* 20 digital inputs: 8 dedicated, 12 shared with Quadrature functions.
(Example: A lathe with index pulse only on the spindle may use 13 total
digital inputs)
* EPP communication with the PC. The EPP communication typically takes
around 100 us on machines tested so far, enabling servo rates above
1kHz.
=== Pinout
* 'UPx' - The 'up' (up/down mode) or 'pwm' (pwm+direction mode) signal from PWM
generator X. May be used as a digital output if the corresponding PWM
channel is unused, or the output on the channel is always negative. The
corresponding digital output invert may be set to TRUE to make UPx
active low rather than active high.
* 'DNx' - The 'down' (up/down mode) or 'direction' (pwm+direction mode) signal
from PWM generator X. May be used as a digital output if the
corresponding PWM channel is unused, or the output on the channel is
never negative. The corresponding digital ouput invert may be set to
TRUE to make DNx active low rather than active high.
* 'QAx, QBx' - The A and B signals for Quadrature counter X. May be used as a digital
input if the corresponding quadrature channel is unused.
* 'QZx' - The Z (index) signal for quadrature counter X. May be used as a
digital input if the index feature of the corresponding quadrature
channel is unused.
* 'INx' - Dedicated digital input #x
* 'OUTx' - Dedicated digital output #x
* 'GND' - Ground
* 'VCC' - +3.3V regulated DC
.Pluto-Servo Pinout(((pluto-servo pinout)))[[fig:Pluto-Servo-Pinout]]
image::images/pluto-pinout.png[align="center"]
.Pluto-Servo Alternate Pin Functions[[table:Pluto-Servo-Alternate-Pin]](((pluto-servo alternate pin functions)))
[width="90%", options="header"]
|========================================
|Primary function | Alternate Function | Behavior if both functions used
|*UP0* | PWM0 | When pwm-0-pwmdir is TRUE, this pin is the PWM output
| | OUT10 | XOR'd with UP0 or PWM0
|*UP1* | PWM1 | When pwm-1-pwmdir is TRUE, this pin is the PWM output
| | OUT12 | XOR'd with UP1 or PWM1
|*UP2* | PWM2 | When pwm-2-pwmdir is TRUE, this pin is the PWM output
| | OUT14 | XOR'd with UP2 or PWM2
|*UP3* | PWM3 | When pwm-3-pwmdir is TRUE, this pin is the PWM output
| | OUT16 | XOR'd with UP3 or PWM3
|*DN0* | DIR0 | When pwm-0-pwmdir is TRUE, this pin is the DIR output
| | OUT11 | XOR'd with DN0 or DIR0
|*DN1* | DIR1 | When pwm-1-pwmdir is TRUE, this pin is the DIR output
| | OUT13 | XOR'd with DN1 or DIR1
|*DN2* | DIR2 | When pwm-2-pwmdir is TRUE, this pin is the DIR output
| | OUT15 | XOR'd with DN2 or DIR2
|*DN3* | DIR3 | When pwm-3-pwmdir is TRUE, this pin is the DIR output
| | OUT17 | XOR'd with DN3 or DIR3
|*QZ0* | IN8 | Read same value
|*QZ1* | IN9 | Read same value
|*QZ2* | IN10 | Read same value
|*QZ3* | IN11 | Read same value
|*QA0* | IN12 | Read same value
|*QA1* | IN13 | Read same value
|*QA2* | IN14 | Read same value
|*QA3* | IN15 | Read same value
|*QB0* | IN16 | Read same value
|*QB1* | IN17 | Read same value
|*QB2* | IN18 | Read same value
|*QB3* | IN19 | Read same value
|========================================
=== Input latching and output updating
* PWM duty cycles for each channel are updated at different times.
* Digital outputs OUT0 through OUT9 are all updated at the same time.
Digital outputs OUT10 through OUT17 are updated at the same time as the
pwm function they are shared with.
* Digital inputs IN0 through IN19 are all latched at the same time.
* Quadrature positions for each channel are latched at different times.
=== HAL Functions, Pins and Parameters
A list of all 'loadrt' arguments, HAL function names, pin names and
parameter names is in the manual page, 'pluto_servo.9'.
=== Compatible driver hardware
A schematic for a 2A, 2-axis PWM servo amplifier board is available from the
(http://emergent.unpy.net/projects/01148303608[the software developer]).
The L298 H-Bridge can be used for motors up to 4A (one motor per
L298) or up to 2A (two motors per L298) with the supply voltage up to
46V. However, the L298 does not have built-in current limiting, a
problem for motors with high stall currents. For higher currents and
voltages, some users have reported success with International
Rectifier's integrated high-side/low-side drivers.
== Pluto Step[[sec:Pluto-step:-Hardware-step]](((pluto-step)))
Pluto-step is suitable for control of a 3- or 4-axis CNC mill with
stepper motors. The large number of inputs allows for a full set of
limit switches.
The board features:
* 4 'step+direction' channels with 312.5kHz maximum step rate,
programmable step length, space, and direction change times
* 14 dedicated digital outputs
* 16 dedicated digital inputs
* EPP communication with the PC
=== Pinout
* 'STEPx' - The 'step' (clock) output of stepgen channel 'x'
* 'DIRx' - The 'direction' output of stepgen channel 'x'
* 'INx' - Dedicated digital input #x
* 'OUTx' - Dedicated digital output #x
* 'GND' - Ground
* 'VCC' - +3.3V regulated DC
While the 'extended main connector' has a superset of signals usually
found on a Step & Direction DB25 connector--4 step generators, 9
inputs, and 6 general-purpose outputs--the layout on this header is
different than the layout of a standard 26-pin ribbon cable to DB25
connector.
.Pluto-Step Pinout[[fig:Pluto-Step-Pinout]](((pluto-step pinout)))
image::images/pluto-step-pinout.png[align="center"]
=== Input latching and output updating
* Step frequencies for each channel are updated at different times.
* Digital outputs are all updated at the same time.
* Digital inputs are all latched at the same time.
* Feedback positions for each channel are latched at different times.
=== Step Waveform Timings
The firmware and driver enforce step length, space, and direction
change times. Timings are rounded up to the next multiple of
1.6μs, with a maximum of 49.6μs. The timings
are the same as for the software stepgen component, except that
'dirhold' and 'dirsetup' have been merged into a single parameter
'dirtime' which should be the maximum of the two, and that the same
step timings are always applied to all channels.
.Pluto-Step Timings[[fig:Pluto-Step-Timings]](((pluto-step timings)))
image::images/pluto_step_waveform.png[align="center"]
=== HAL Functions, Pins and Parameters
A list of all 'loadrt' arguments, HAL function names, pin names and
parameter names is in the manual page, 'pluto_step.9'.
|