The replacement controller board and motor lasted a hour or two. @darrent did some testing again, and it looks good from the laser side thru the cable to the attachment.
I’m in discussions with Thunder’s tech support. Current stage:
Tech: please try x, and verify y.
me: Please refer to my first email, where i stated we tried x and verified y. But I did test it again, and had others verify it.
Tech: please send pic of item
Me: Please look at the order of what you sent us 2 weeks ago. OR look at the pic I sent 8/xx/2017 of the same item.
… more of this.
I certainly don’t know enough off the top of my head to convert the direction and pulse signals from the Thunder to the proper signaling that this motor requires. But that is, in fact, all that is needed: convert the two 5V referenced signals from the Thunder (one of which says ‘clockwise’ or ‘counterclockwise’ and the other which says ‘on’ or ‘off’) to the language of the rotary motor. The Thunder provides the 5V reference, the direction and pulse signals, a ground reference, and 36V to the rotary controller.
I have no idea on how to get the Thunder to generate a single pulse to make such a measurement on the motor.
However, there does, in fact, appear to be a direct relationship between between the length of the pulse and the time the motor is turning. Additionally it is very clear that RD Works is doing all of the processing / math necessary for the rotary tool prior to sending the dir/pulse signals - thus the controller itself does not buy us anything more than that of a typical controller.
So as Walter noted, we could just go buy a generic controller. In fact, we very likely could use the exact same ones found inside the Thunder for the x- and y- axes (although that controller is larger than the one found on the rotary tool).
Also, I spoke with John yesterday, and he believes the motor is a Nema 23.