Advanced Search

Hallo,

ja, hier laufen ein AX5106 und ein AX5203.

What version of linuxcnc are you running. We noticed the python broke on atc between 2.9.4 and 2.10 master.

If you're running master, check the updated python file from the latest develop version of probe basic. Run a meld file comparison to see if the latest edit is in your current python file.

Beyond that, just come through your subroutines. Check pocket counts to make sure your not dropping an index signal for some reason.

As debug everywhere to see everything is doing what you expect.

Yes, I did.
After I applied the lines that DMNZ suggested, xfce started again automatically

all valid points. I have Mesa myself. I was just going through a number of threads here converting other boards like colorlight, nvem, even stm32 some of which require a lot of work and pcb mods and yet here is a board that you can get cheaper with more power, all peripherals, jtag ready, full xilinx support and no interest at all. btw this is just one of many, there are other boards from Ebang Ebits like ebaz4303, ebaz4332, ebaz4051 which are very similar.

i thought may be there is something wrong with it as i am not a fpga guru myself   I am thinking about ordering one just to learn a bit more about fpga toolchain, looks like great learning platform.

I don't think you need Litex for Zynq as it has all those modules cpu cores, ethernet, ram, rom hard wired in the chip plus fairly large fpga part to build anything else like steppers or encoders.

PS. i am actually even further down under in New Zealand   i use parcel forwarding companies from US so it is not too bad, just the shipping


 

Try this.
extract the files.
The images folder goes in  YOUR_CONFIGURATION_FOLDER/qtvcp
The qtdragon_lathe_handler.py file goes in YOUR_CONFIGURATION_FOLDER/qtvcp/screens/qtdragon_lathe/

github.com/ddjmechservices/MAZAK-VTC16B.git

We are working off of the Probe-Basic-Staging branch proofing everything out before we merge it with the main branch.

Any ideas ? No one has bothered.
Might be supported by the Litex infrastructure. The ethernet chip of that board is different to the one Mesa uses, so a driver would be at least one of the tasks.

Plenty of Spartan 6 Dev boards that are easier to use Hostmot2 (mesa fpga firmware sources) firmware with. I've had success with 7c81 setup, both SPI & SPP (parallel port) interfaces. Now experimenting with Ethernet.

Ok once you have the firmware going, the next step is designing & building the I\O, translation from 3.3v to 5v and then whatever your field voltage maybe.

At the end of the day it's just a little under what a Mesa board may cost, unless of course you're Down Under and shipping can almost double the cost of a 7i92.

SebastianM wrote:

No idea if I did anything wrong, but after I applied that line from above and rebooted, Debian won’t launch the desktop environment anymore. I can manually start xfce. Never mind 

Did you get xfce to start automatically at boot again?  If so what did you need to do?
below is what my Grub file looks like, if there is something in here i can change, please let me know:
GRUB_CMDLINE_LINUX_DEFAULT="quiet isolcpus= 3 pcie.aspm=0 r8125.eee_enable=0  modprobe.blacklist=r8169 pcie_aspm=off idle=poll"
GRUB_CMDLINE_LINUX=""

These changes worked great by the way.  I can't thank everyone enough. I went from 10ms max ping down to 0.105ms

Hi All,

i can see there are many different FPGA boards has been adopted for LinuxCNC but for some reason no one is using this one (or similar) - EBAZ4205

This is Xilinx Zynq 7010 fpga pcb mass produced for crypto mining which makes them very cheap (under 20usd) and readily available (even at amazon).

 

Looks like it has all that is needed -  2 cores, decent fpga fabric, accessible jtag, uart, sdcard, 100mb Ethernet, lots of IO pins and even schematics are available:

github.com/xjtuecho/EBAZ4205/blob/master...205/EBAZ4205-SCH.pdf

any ideas why it has not been adopted for CNC?

for a commercial work i would still most probably prefer MESA due to its quality and support, but for cheap home automation it looks like much better fit than LED control cards or STM32 boards.

Have you added the appropriate parameters in the car file for pockets and atc parameter function storing? Have you adjusted the macros for your atc pocket count for the calculations? What version of probe basic are you using?

Do you have a GitHub with your files where I can review them all?

hi all 
im new here and i'm currently in school (mechanical engineering), we're making an plasma table for this semester project. as of right now we're almost done and during some test on it tho we cant figure out how to disable the probe when we start an test, we have made our setup so that it hits the material on the table and makes that the home, and then in the materials we have told it what hights it should cut it, so we dont need the probe, also atm. we dont have the waterbed on the table yet so we're trying to make the test up in the air.

 

We are just finishing up our linuxcnc retrofit with Probe Basic on our Mazak VTC16B. Everything seems to work just fine, except we are having an issue with the controller not keeping track of the current pocket number (Parameter #3990). The machine has a 24 position index style carousel ATC. It indexes correctly and on the first try after indexing, it will grab or store the appropriate tool in the appropriate pocket using M6 commands. After the first toolchange though, it's almost as if the controller resets itself as starting from Pocket 1. The GUI shows the correct pocket that is supposed to be used. 

For example, if we start with Tool 3 in our spindle, Pocket 3 empty, Tools 2 & 3 in pockets 2&3; just after indexing if we store Tool 3 in carousel, it will rotate to pocket 3 and store the tool. If we then run a M6 T2, instead of rotating -1 pocket to grab T2, it will rotate +1 pocket, as if it were starting back at pocket 1. When doing this, the GUI shows pocket 3 being the active pocket and rotating +1 to pocket 4.

I'm assuming it has something to do with parameter 3990 not being updated or called out properly. We had to make some changes to the default config to make it all work with our machine. I've attached some of the proper config files, would somebody be able to provide any insight on where to start diagnosing this?

Okay, well I don't _completely_ understand, but...

There's a competition going on between the M6 command, and the M3 that happens just before it. If I reverse the order, to "M6 M3", then all is fine.

And the answer probably lies in my quirky handling of M3.

I run my machine from an RPi. As I've written elsewhere, spindle_enable is connected to a Pi GPIO output pin. That output pin is connected directly to a Pi input pin. I have a script in which gpiomon watches that pin, and starts and stops the spindle based on its transitions. It handles stop pretty directly. But when starting, it first drops the atspeed signal, then puts up a dialog asking me if it's okay to start the spindle. If I cancel, it runs "halcmd setp halui.machine.off false" to shut things off. If I hit okay, it activates the smart plug, and a couple of seconds later enables at-speed, using "halcmd sets spindle-at-speed true". I know that all sounds like a lot of chewing gum and string, but I like being explicitly asked whether I want the spindle that's about a foot away from my face to start up. (I also like it turning off automatically at the end of the job.)

Anyway... somewhere in there, if the M6 follows the M3, the spindle goes off after being turned on. It's complicated further because at-speed doesn't fully pause the program -- it will keep running until it hits a G1. So the M6 happens while at-speed is low.

It's now making my brain hurt a little. I'll just be sure there are no M6 commands in my g-code from now on.

I started github.com/JTrantow/LightBurn_to_LinuxCNC. Currently it just sketches out the idea. No code added yet.
I can add you as a Github collaborator.
 

Oh! (replying to myself)

Reading the source for hal_manualtoolchange, I see that it's also his window is part of the AXIS manual toolchanger.the program responsible for the "This window is part of the AXIS manual toolchanger." window that shows up when I start Axis. I hadn't made the connection before. Lately that window has been appearing mostly off-screen, in a way that I can't read it. Since I always ignore it, I didn't worry about it. But now I wonder if whatever is causing that is also messing with the confirmation dialog somehow.

Clearly something to investigate.

paul