Advanced Search

If you have the SyilX3 parallel port hal file, that can be used to figured out the pinout

In any case the pinout will be needed to determine which firmware to use.
 

Pictures?

tar_san wrote:

Hello.
I had to recreate LC10 homing code from zero reading manual designated for a driver with a motor with incremental encoder . ( I thought original code was difficult to fix )

If you still have some problems, I consider to open my codes...( I have something to do for some improvement )
 

@tar_san - I very much would like to see your code.  I am not happy with my fixes to the original code.  Thank you!

-- Ralph

I'm not sure who makes the drives on them I bought them already made. I had them working with mach3 but lost the recipe. I got the syilx3 machine running ok with linuxcnc but I would like to get the mesa board working. They both have proprietary break out boards on them.

Moved to "Driver Boards"
-
What drives do those machines use?
Are they parallel port controlled?
Do they have some kind of BOB or controller?
Or, how are those machines connected to PC now?

HI, I bought a 5i25t board and no daughter card. I want to run my existing hardware, a syilX3 mill and a plasma cutter. Is there a provided firmware that will run these machines or do I have to create a new one? If I have to create a new one what is the best tool to use for this? These are both basic stepper machines with 4 axis for the syil and 3 for plasma cutter.
Thanks in advance for you answers.

Also you may do better performance wise by using 2 windings in series for all drives
so 57V rather than 28.5V (assuming the drive is OK with 57VAC, )

28.5V is roughly equal to 40 VDC  and 57V is roughly equal to 80VDC

You would get better high speed performance with the 57VAC

To each it's own.
-
There in no difference either way will work, but i like to keep things compartmentalized.

I gave this little project a try as can be seen in the forum post linked below:

forum.linuxcnc.org/12-milling/50559-opti...sion?start=90#334591

I'm using two rotary encoders on a Arduino Micro clone and everything worked on the first attempt. However I found a bug in the python code for the encoder handling  when using them mode 1 (send up or down signal).

The implementation of that functionality relies on this code which is a bit flawed.

 

It triggers the HAL pin waits for a very short period and the untriggers the HAL pin again. This would only sporadically work when I tested in on the PC I'm using for LinuxCNC.

Instead of doing the wait approach I think it would be simpler and more fool proof to have the Arduino code send two events when using mode 1. One event to trigger and another event to cancel the trigger a short while later (just like it does for the normal push buttons) so no waiting is required in the Python code.

With all the milling down I turned my attention to the electronics, consisting of a small Arduino micro clone and two rotary encoders with built in push buttons.

 

 

Here is how the complete assembly looks.

 

 

Here it is installed on the side of the control panel.

 

And here is a short video showing how the two rotary encoders work in LinuxCNC with the Probe Basic user interface.



The LinuxCNC ArduinoConnector by Alexander Richter worked surprisingly smoothly. However I did find a bug in the Python code when it came to using the encoders in up/down mode instead of counter mode. I'm going to report that bug in the forum thread for the Arduino connector, however it was not a show stopper as I simply switched to counter mode instead.
 

OK next is to test the FPGA interface

Can you power down the system, unplug the flat cable from the 7I33
power up and without launching LinuxCNC, a report the results of this
command:


mesaflash --device Ethernet --addr [your_cards_IP_address] --rpo 0x1000

[your_cards_IP_address]  is likely 10.10.10.10 or 192.168.1.121

 

I wanted to add, I downloaded linuxcnc from the official website, installed the system several times, the problem remained. If I understood correctly, gmoccapy intercepts some mdi commands, this is somehow connected with the probe screen, accordingly, when I open the file with g-code, an error occurs. I would like to make a video describing the problem, but my knowledge of English is very poor.

I spent the last week with a really bad cold and while being bored by the need to rest and stay calm I decided to design a small addon for the control panel on the mill.

When I first designed the control panel I had never touched a CNC mill so I had no real idea which physical buttons that I would need.

After using the machine for a while I have realized that having rotary encoders for controlling feed and speed override would be very useful as it would mean that they could be operated while wearing gloves which does not work very well with the touch screen.

As I had plenty of time to kill this addon might have gone a bit over the top but it's very sturdy and works really well.

I started by milling the body out of some 6082 aluminum.

 

 

 

 

I then milled a face plate from a 2 mm thick scrap piece of stainless plate that I had laying around.

 

 

 

 

Good to see you have comp working.
The raw error looks very linear, are you sure about your Exp coeff value?

The card is a 7i80HD-25 with the 7i80hd_25_sv12.bit on it, addr 10.10.10.10
I am sorry if my answers don´t get in in time, but the forum cuts out frequently so I do not always have access.

If this is of any importance:
System Debian GNU/Linux 12 bookworm X86-64
Linuxcnc 2.9.0