Advanced Search

I think 6.5A peak is correct.

4.6 times the sqare root of 2 is a tiny bit over 6.5.

Which of these is the best?

www.stepperonline.ca/y-series-digital-st...er-motor-dm556y.html

www.stepperonline.ca/y-series-digital-st...34-motor-dm860y.html

www.walmart.ca/en/ip/DM556-2-phase-Stepp...4V-50V-DC/6CZOWS35V8

www.aliexpress.com/item/33014449403.html


The motors are all 4.6A steppers

These drivers are only 4A RMS. Do I need 4.6A RMS?

I have two physical hosts to run iGH separately.
I want to implement the redundant function? Can it be achieved? What to do?

Cant do this anymore bye all wrote:

.... that's right ndiswrapper.

Oh how i hated that, to the point of buying Senao access points and using the internal PCMCIA cards as they used Atheros chipset that worked properly.

Hello my guys, I am very surprised of how much conversation I have missed, somehow I was not notified of new posts in this thread.
@cornholio and @blazini36 honestly between your "discussion" I was not able to understand what exactly you suggest.
I have been in several discussions in the direction "USB -> bad " where we explored other connection possibilitys, for example Ethernet TCP and UDP connections.

Personally I feel like USB offers a good ratio between ease of use and speed good enough.
However I do see the benefit of offering a faster Option for those that need it. But at the end we have to see that Arduino-connector offers a cheap alternative to Mesa Cards, but it will always have its limits and at some point the user should consider just using a Mesa card instead.
As I am not a very experienced Programmer I am always very happy for advice, so please continue to share your knowledge.

Currently I am reworking the Codebase to implement 2 basic but drastic changes.
1. The Configuration will change to a single YAML Config file, inspired by Klipper and ESPHome. This will allow to copy/ paste Feature specific configs more easily. Also a lot of Emails I get are related to little configuration mistakes. I hope this change will help people get it right more easily. 

2. The old Serial connection sends Pin states encoded in a string. The new version will send everything directly in a bitstream, so for example 8 Input Pins can be transferred in a single byte. The cost of that change is that the user looses the possibility to communicate with the Arduino manually for testing. I expect the communcation to speed up quite a bit from this change - pun intended.

Additionally I have collected a lot of feature requests to support more Hardware and offer more logic for existing features, which if i find the time i am willing to implement in the future.
Hopefully I will be notified again in the future so I can answer more quickly in this thread.

Cheers from Germany!
Alex

Dear linuxcnc users,

There is developped a new trajectory planner with help of several forum members over the past weeks.

- Credits : Joco, Lcevette, Turboss, Linuxcnc8, connor, Grotius, and more.

The new planner is called tpmod_scurve.so

This new planner can be installed alongside the original trajectory planner tpmod.so
by specifying the used planner in the config .ini file.

Existing linuxcnc (RIP) installations can be patched using a small script that replaces a few files.
There is no .deb package patch available.

This codebase uses miminal source code to achieve an S-curve motion profile. No heavy dependencies are required.
Note there are several HAL pins and parameters that must be set at runtime to tune a specific machine to its inertia limits.

Important: Alway's exersise caution using new software, especially on high-speed machining operations.

repository
readme
licence  
disclaimer

Automated installation example:

github.com/ozzyrob/Linuxcnc-FPGA/tree/main

Spartan 6 based project.
Supports Linuxcnc-RIO either with direct spi connection or with the UDP Bridge.

Based on a common Spartan 6 dev board available via aliexpress.
Easily assembled, mostly through hole components only SMD parts are a couple of chips.
Modified 7c81 firmware spi mode
EPP interface also can be implemented.
Have experimented with firmware that supports upto 60 i/o (compared to 57 with the 7c81) requires a dedicated driver, easy enough to implement based on the 7i90 driver for EPP interface.
Easily interfaces to your basic Parallel Port breakout board, up to 3.
using a Aliexpress RS-422 interface baords allows SSerial connection, tested with a 7i73 device.

If anyone in Australia is interested I have a few unpopulated pcbs available.

Read the whole, if you haven't, have a look through the github repository. Be prepared to get your soldering iron out. I guess you didn't come across the DIY 7c81 clones or other FPAG dev boards running Mesa firmware.

Linuxcnc wont work in a VM, you have to install on some actual hardware.

In all honesty think how you want to use your lathe, if you haven't had a lot of exposure of using a lathe I'd spend some time (12 months) learning how to use a lathe.

If you are a machinist, you know what you're doing.

我使用的是sv660n

Might be best to raise the issue on github, more devs there.

Yes I agree that this will put radial load on the ballscrew, I didn't think of that. Ok, I'm open to other ideas please do let me know.

minimal changes allow spiral interpolation with large radius differences
 

Hello everyone! I bought myself a lathe, decided to convert it into a CNC machine! While searching for a control board, I came across this forum topic! Guys, can you advise or somehow give me more detailed tips! Since I'm not particularly friendly with Linux! I can install Linux for debugging on a virtual machine! And then it's not entirely clear what to do. I read the forums, it says that you first need to flash the board! But maybe someone will give me links for a more understandable course of action! I'll be grateful!

Hi, I'm building a high speed rDelta robot arm.
I have a test program that just repeats a circle move twice at nearly 2m/s.
This works great except i noticed a weird deceleration artifact. It stops slowing down for a moment, speeds up and then decelerates into its last point.
This is also visible on the robot itself.
The blue line in the plot I attached is velocity from the hal pin motion.current-vel.


As I've been playing with accelerations and velocities in the .ini file I suspect something in there might be the cause. Any ideas?
I also attached my .ini file  

ps I'm building some custom plotting software but the same thing is visible in hal-scope

Thank you cornholio. As a matter of fact, they did run with:

--enable-non-distributable=yes