Advanced Search

yes, that is the "spindle-released" sensor. As mentioned above I have to convert it to a binary value as the 14V is below the (60% of 24V) digital threshold of my 7i76e.

I can see the "spindle-released" going high when the drawbar is pulled (so, no error when releasing the tool) but get the error when clamping the tool.

Are you using a sensor for the drawbar?

There is a working branch but I haven't had time to work on the macros. All the UI work is done though.

Hi,

I am currently integrating my ATC. However, I get the Error "Failed to release Tool" message when I clamp the tool.

My HAL looks like the following. I get a 0-14V Signal which is converted into a HIGH LOW for the Motion controller.

That sounds great! Is there a release candidate / date already on the horizon? Im really interested in the rack implementation.

I've done some more parts on the mill and it's working great apart from the slow spindle speeds I have to run.

Here is a short video of two aluminum mounting brackets that I designed for the rear sway bar of my race car.



The mounting brackets came out really nice but I can't wait until I have a new spindle so that I can increase the speeds and feeds a bit.

I'm also considering expanding my enclosure a bit as the one I have at the moment allows a bit too many chips too escape during some operations.

 

Thanks - is there any way to recognize this from the specs, or are you aware of a list of screens that provide this?

Hey guys, I'm trying to put my previous PC to use on my PCNC1100 S3 - pathpilot - 7i92t.  I get through the installation and it does freeze after I select my machine.  I have verified that the 7i92t does work as I borrowed another PC to test the 7i92t + PCNC1100 for functionality.  So I think it's some issue with my PC setup.

I get these errors during startup after the BIOS and before pathpilot:

Mother Board:  Asus a520M 
CPU: AMD 5600gt

core perfctr but no constraints; unknown hardware
kobject: can not set name properly!

Any recommendations on bios settings or something to clear this?

thanks
 

Remora is still in active development but support for the LPC1768 is now legacy only. STM32 and RT1052 MCUs are now the go to with more boards available.

The serial steppers are nice because they are easy to setup and they are also very quiet. I dont know if there is an fpga firmware for it thought. The SPI ones, someone has done a custom firmware to work with those.

What is W13 doing? Is it just for swapping between the usb or the green connector?
Consider adding a jumper that can disconnect power to the FPGA or separate the 5v rail between FPGA and RPi5. I found it convenient having a separate jumper for that, incase you needed to either separate the power between the 2, or if you need to reset the MCU/FPGA, you dont need to turn off the RPi

When you are done will you post the design on that easyeda website so I can clone it to modify it? Im also hesitant about a 1 board thing, but I wanted to make something with a swappable MCU/FPGA , and the formfactor looks pretty decent sized.

Can you reduce the encoder scale? If not, probably best long term solution
would be for  the encoder driver to use 64 bit intermediate calculations.
I can take a look at this.

nice! please post up when its done, that is an interesting machine, look robust for a bench mill/

Thank you guys for the interest and the suggestions! I will try to respond to a few of them here:

"I have occasionally thought that there should be a niche for a similar board, but with on-board stepper drivers (Trinamic or some other serially-controlled driver)
That would, of course, need a dedicated HAL driver, but those can be surprisingly straightforward."

I was actually planing on designing a seperate IO Board featuring the Trinamic 5160 Drivers, as they would allow me to run high current stepper motors. They come with UART and SPI interface functionality but I haven't really seen an advantage in interfacing them serially. Maybe someone has a good argument as to why it would be worth it to go through the integration troubles?

"I like having the boards seperate, just in case my butter fingers cause one the voltage translation chips to blow a smoke valve and damage the PCB."

That was my thought process as well. I'm a little hesitant to put everything on one big PCB, as i feel like that would make errors more catastrophic. I also like the modularity of having seperate PCBs, especially in these early prototyping stages. I did actually bring the JTAG out, but realize that better labeling was neccesary, which I've since added.

"I am liking the look of this board. Did you do this in easyeda?
Suggestion, add the rpi 40pin header. Aside from being able to add stuff rpi side, I find it valuable for debugging the MCU/FPGA side of the board using a regular rpi without having to keep removing a cm module and you can use it as a backup incase you damage the 100pin hirose connectors or theres another RPi/chip shortage"

Yes, I did do this in EasyEDA. I started the project with EasyEDA becuase I foud the integration with the JLCPCB services appealing.
Including the 40pin Header is a great idea, which I will definitly add. Unfortunatly that will require major rerouting. Before rerouting everything I will continue collecting and thinking about additions/optimizations. That way I'll hopefully save money on design itereations.


I'd love to here if you guys have any other sugestions. The design philosophy behind this board is to make it the Compute Module 5 version of the Mesa Electronics 7c81, and I will probably finish this project making exactly that but I'm also open to brainstorming other ideas for potential future projects.

Thank you everybody!

Die Siemens und Heidenhain Steuerungen basieren auf Werkstatt orientierter Programmierung (WOP), im Gegensatz dazu die PAL-Programmierung.
LinuxCNC basiert auch auf PAL und hat sehr viel gemein mit Fanuc, aber eben nicht alles. Heidenhain oder Siemens Code kann man überhaupt nicht unter LinuxCNC laufen lassen.

"Pal ist die Sprache die in de rAusbildung gelehrt wird und die auch die Basis für die Sinumeric ist."
Ja, die ganz alten Siemens Steuerungen, aber die neueren (auch schon relativ lange) nicht.

I'm also designed a mesa clone for a Raspberry Pi, currently in the process of testing everything.
Except for the reversed Sserial Pinout it looks like I got everything right.
You can take a look at my schematic for reference: github.com/jstjst/stmbl-fpga-master/blob...tmbl-fpga-master.pdf
Be careful the SPI In Out labels in the 7c81 schematic are reversed compared to the ucf file. Luckily I could fix that in the ucf file.
I routed some signals under the fpga, I see no problem with it. But try to have no completely hidden tracks so you can fix them if you got some connections wrong. In my opinion one of the more important things is the placement of the decoupling caps.

There are some pitfalls with the whole (fpga) programming (especially when using the Ethernet host interface). But with some reading through the forum I got everything pieced together, including recompiling mesaflash and linuxcnc. So it is totally doable (for reference, this is my first deep dive into linuxcnc and mesa/hostmot2, only used the RPi GPIO interface before, didn't use/own a mesa card).

Big thanks to Peter for providing the schematics and all the information that is on the forum!