Advanced Search

Testing max motion.digital-out-NN via control with M64 / M65

www.youtube.com/shorts/eS7oG1WSP3c

Pictures of the electronics box?

viesturs.lacis wrote:

AFAIK with parallel port breakout, you will be able to do only step/dir signals - if those servodrives do accept step/dir then you definitely can reuse them. The problem will be the parallel port. It is slow and limits your I/O and also has become ancient relic in PCs. That is why most of folks are using Mesa boards. But for that we need to know more about the drivesaa
 

The parallel port is not slow, but generating steps by software on the main CPU IS slow.  It is possible to generate roughly 20,000 steps/second on good CPUs, far less on some that don't have good real time performance.  There are various external hardware step generators available.  Mesa and Pico Systems (that's me) can provide these.  Our Universal Stepper Controller can easily do 300,000 steps/second with very good step timing.
Jon
 

Initially, do as I suggested in the mailing list and try to drive the motor from the command-line. Take the rest of LinuxCNC out of the picture.

I would call that an 8 pole motor

If I understand correctly then the machine moves are correct but the tool path inserts the angled move. I'm not sure what you are using the 'U' axis for but you may want to remove that from the plotter and see if that fixes the issue:

Change this line
GEOMETRY = XYZ-ACU

to
GEOMETRY = XYZ-AC

1) No, I did not try magnetic homing
Are there any specifics to be included in HAL file for that? Or just comment out index related stuff?
2) Yes, I did turn the motor one full turn and observe the change in rawcounts value
3) Yes I did apply small current to motor and turn it by hand and count 4 positions more or less 90 degrees apart where motor tries to snap

 

yes, but may I ask what you intend to do with so many IOs?

example via shiftreg:
forum.linuxcnc.org/18-computer/49142-lin...ecp5?start=30#274910

or if you have a bigger FPGA with enough PIN's,
or ....

Hi,

Greetings to all.

My 5-axis machines was running fine with the same INI, But as my Motherboard died and I changed my System and I also shifted my machines to other location.
Now my 5-axis TCP is not working properly as I can see a small jump simulation of Linuxcnc but in Machine there is no jump and because of this it derails from the actual path as you can see in Image. 



Now I am not able to figure out why it is doing so..

I have attached my INI and HAL file.

 
 

Regards
Abhishek  

I may require a minimum of 16 input and 16 output pins, is it available in linuxcnc-rio?

Have you tried magnetic homing (q instead of qi)

Have you verified the encoder counts per turn?

Have you verified the number of poles?

You can do this by supplying an small current and finding the number of null positions
The number of poles is twice the number of null positions.

Have you tried with a drive offset of 90 degrees?

If you get jerky motion with a commanded move its most likely the scaling or direction
are wrong so the drive phase does not match the rotor angle


 

we got a w5500 thing on remora also,
this is the cheapest i could build something probably

github.com/cakeslob/RRW_LAB

serial will not work with LinuxCNC.

www.cnczone.com/forums/mach-mill/362276-...3020-conversion.html

I was planning to gut a Techno CPM 3020 and save only the servos but with a little experimenting yesterday, I was able to get the machine to work with the demo version of the original software (Galaad Kay). Support at Galaad seems to be so so and I'd rather use LinuxCNC if it's practical.

Would LinuxCNC have the ability to replace the original software? It seems all the existing hardware is in good working order so I hate to pitch it.

I am late to the party but would like to add some of my experience if it helps.

Typically, you would want to have some means to store the values of the current pocket ready, the tool number in that pocket, and whether the tool in the spindle is equal to the first 2 if power is lost. You would do this via some parameter that is written on LCNC exit and read into memory at startup. In LCNC, these parameters are stored in the var file. User assigned variables in RS274 GCODE are 31-5000 in LCNC. Typically in most controls outside the LCNC world 30-100 are volatile, while 500-999 are non-volatile. Meaning they are persistent.

With that, I would create a set of variables in the ATC routine that stores the tool numbers by pocket numbers in the drum, and also the value of the tool loaded in the spindle in thses variables. Given LCNC allows up to 5000, I would use(assuming a 12 station drum) 4000 ~4014. 4000 is the current tool in the spindle. 4001 is the current tool in the slot facing the spindle. 4002 is the current slot number/pocket number. The balance would be the slots.

Once the tool is loaded in the spindle, the value for the pocket it came from should become 0. If I have tool 1 in the spindle 4000 = 1. If it came from slot 6 and it is facing the spindle or tool arm, then 4001 = 0. 4008 = 0. If I call tool 3 and it is in slot 9 and tool 6 was in the spindle, then the drum should rotate to pocket 9, see that tool 3 is there via 4011 = 3, swap tools, 4011 = 6, 4000 = 3, 4001 = 6.

This method allows for one to assign the correct values via MDI in the event the coordination of the tools and pockets is lost because power was lost before the file was written. You can also call a python sub routine that once the tool change cycle completes writes the file but this is difficult and must be very precise.

Example:
(Assign the tool number of the spindle)
#4000 = 1

(Assign the tool number in the slot at the ready)
#4001 = 3

etc....

You can test this by assigning the values in MDI. Power of LCNC. Open the var file for your profile. Check to see the var number to the left and the value stored on the right. It should be what you assigned in MDI in the file. ex... #4004 = 10. Slot 2 has tool 10 in the slot will appear as:

~ other vars...
4000 10
~other vars

in the var file.

Hope that helps.