Rod said:
We are flooding the port with calls and responses. Our programmer can't find it, Acroloop can't find it and I am unwilling to give AL our source code.
Why all the calls? You shouldn't need to get the status any faster than the HMI needs it unless the PC needs the info for control.
Rod said:
They probably don't have the time to wade through 100,000 lines of our code and I can't afford to send our programmer there for the time it would take. We/I am STUCK!
THAT IS A LOT OF CODE. WHAT ARE YOU DOING? We can do a flying shear in less than 20 steps ( commands ). An injection molding machine may take 50.
Rod said:
We only buy about 3 motion control units per month, so we are too small to be of concern.
That enough to get some attention. We have plenty of customers that buy only 10 a year. They add up after a while.
Rod said:
On your hydraulic servo valve controls do you incorporate a 'dithering frequency/voltage' to prevent stiction in the valve spool? If so, what freq do you find to be the best? I've always used about 400Hz.
Thanks,
Rod
We did in our first generation product. We didn't on our second generation product. Dither wasn't necessary with the newer proportional and servo valves. Some valve drivers have the ability to add dither to the controller signal. 400 Hz should be just find for bigger systems with time constants in the 20 millisecond range. If your system is faster then you may want to go without the dither.
The frequency is really dependent on the update time of the controller. If the controller updates every millisecond then the frequency will be 500Hz. The dither period must be some even integer number times the the controller update period.
I have seen system with time constants as low as 2.2 milliseconds. A 400HZ dither would make the system vibrate at that rate. You really need to know the response of the system.
I don't like to use dither. It only keeps the valve spool from sticking which it shouldn't anyway with a newer better quality valve.
You mentioned PowerPC. You use a MAC for the front end?
No, it cost too much to develope the front end code to do it for a handleful of macs. I have a Mini Mac. I have used that to do assembly language and C programming for our product. Most gets done on a PC using Metrowerks.
To me that would imply using USB or Firewire ports and a stand alone motion control box.
The PowerPC version of our products supports Ethernet and USB.
I love my MACs but wouldn't base an industrial machine system on them. I've only seen two.
Macs aren't designed for industrial control. However, Darwin ( a Apple version of BSD unix ) is far superior to Windows. Even though the Mac hardware is not as fast as the PC hardware the Mac still perform better. Darwin multitask a lot more smoothly than windows. The windows message queue really slows it down.
I just about have the .pdf done that shows the need for a jerk feed forward and a higher order feed forward.