bdring / FluidNC

The next generation of motion control firmware
Other
1.57k stars 379 forks source link

MKS DLC 32 #205

Closed Lazarus-Rising closed 2 years ago

Lazarus-Rising commented 2 years ago

Hi, I noticed somewhere a driver configured for the MKS DLC 32 board. is this only for the mk2 board or will it work with the mk1 board as well? many thanks.

bdring commented 2 years ago

Do you have a link to the board you are talking about?

MitchBradley commented 2 years ago

According to the changelog at https://github.com/makerbase-mks/MKS-DLC32/tree/main/hardware , they changed a few pins between V1.1_002 and V2.0_001, so it would be necessary to account for that in the FluidNC configuration file.

Lazarus-Rising commented 2 years ago

Yes this is the board https://images.app.goo.gl/Bk53asDkLV4PVkhi6

I bought version 1 which didn't work properly, then they deleted version 1 firmware when they released version 2. Not helpful as I had bought 6 version 1 boards which are now defunct!

Is it a big job to alter the fluid NC file? Thanks.

On Sat, 25 Dec 2021, 17:14 Mitch Bradley, @.***> wrote:

According to the changelog at https://github.com/makerbase-mks/MKS-DLC32/tree/main/hardware , they changed a few pins between V1.1_002 and V2.0_001, so it would be necessary to account for that in the FluidNC configuration file.

— Reply to this email directly, view it on GitHub https://github.com/bdring/FluidNC/issues/205#issuecomment-1001046685, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT77TGT76KU7B3RT7GYTYA3USX3YFANCNFSM5KX7M2MA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

MitchBradley commented 2 years ago

Is it a big job to alter the fluid NC file?

You just open it in a text editor and change the pin numbers.

Lazarus-Rising commented 2 years ago

Okay I've done simple bits like that before. Is it a matter of comparing pin diagrams for both boards and changing where necessary in a configuration file? Or would it be in the driver file?

On Sat, 25 Dec 2021, 18:30 Mitch Bradley, @.***> wrote:

Is it a big job to alter the fluid NC file?

You just open it in a text editor and change the pin numbers.

— Reply to this email directly, view it on GitHub https://github.com/bdring/FluidNC/issues/205#issuecomment-1001058283, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT77TGQDJUYI2IPAIARE5RLUSYETBANCNFSM5KX7M2MA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

MitchBradley commented 2 years ago

Is it a matter of comparing pin diagrams for both boards and changing where necessary in a configuration file?

Yes. The config file has lines like

direction_pin: gpio.22:low

You just change that in a text editor and upload the new version of the file. You do not have to recompile anything.

MitchBradley commented 2 years ago

Read the wiki

Lazarus-Rising commented 2 years ago

Thanks for your help so far. I may have to shout up later though 👍

On Sat, 25 Dec 2021, 18:37 Mitch Bradley, @.***> wrote:

Is it a matter of comparing pin diagrams for both boards and changing where necessary in a configuration file?

Yes. The config file has lines like

direction_pin: gpio.22:low

You just change that in a text editor and upload the new version of the file. You do not have to recompile anything.

— Reply to this email directly, view it on GitHub https://github.com/bdring/FluidNC/issues/205#issuecomment-1001058931, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT77TGQQSG2IUE452LEKW23USYFPVANCNFSM5KX7M2MA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

Lazarus-Rising commented 2 years ago

👍

On Sat, 25 Dec 2021, 18:39 Mitch Bradley, @.***> wrote:

Read the wiki

— Reply to this email directly, view it on GitHub https://github.com/bdring/FluidNC/issues/205#issuecomment-1001059164, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT77TGW4GLTCE4VUQJJOJUDUSYFXVANCNFSM5KX7M2MA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

Lazarus-Rising commented 2 years ago

Rather than starting a new thread I wondered if you could confirm that your basic 3 axis code would run on this screw terminal breakout board and an esp32 dev kit c? https://www.amazon.com/Screw-Terminal-Breakout-Module-ESP32-DevKitC/dp/B08LGFRT87/ref=pd_sbs_3/134-7356419-5189004?pd_rd_w=ODlVS&pf_rd_p=3676f086-9496-4fd7-8490-77cf7f43f846&pf_rd_r=3A8KMZ83W4WC6YFS65T9&pd_rd_r=8af16a5d-a27e-4755-a16e-0aa38414ffc5&pd_rd_wg=7xO4p&pd_rd_i=B08LGFRT87&psc=1 I'm happy to go down a modular route with stepper driver expansion boards etc as I intend to use this for diode lasers, Co2 lasers and plasma cutters with code mods as required. many thanks.

bdring commented 2 years ago

Some output pins will work, but some input pins should have pull up resistors and filtering .

We would not help with support on that.

Lazarus-Rising commented 2 years ago

fair enough, I'll have to have a scoot round and see what I can find in addition to the MKS. I was following a tutorial on using an espduino, actually a Wemos D1 R32 with cnc shield and something went wrong and it fried 2 laptops, so I'm loathe to go down that route again even though I now use a USB isolator. Suggestions welcome, and many thanks for help so far.

bdring commented 2 years ago

Here is a link to all the hardware I know about.

https://github.com/bdring/FluidNC/wiki/Hardware-that-Runs-FluidNC

CBDesignS commented 2 years ago

@Lazarus-Rising MKS is still supporting v1 hardware on the mks dlc32 ! they released firmware on 7th dec. the 13th dec and the most recent released just a few days ago on the 22nd december. I know their support is shit but they are trying more than they used to. the v2 boards are just because they ran out of hardware and to keep ripping .. sorry making money they had to change hardware and make a new revision of the boards.

Lazarus-Rising commented 2 years ago

Hi my friend thanks for that I'll have alook at it, I still have a 'few' of them laying around. In the first version of the board the Z axis didn't work and I experienced some worrying signs when engraving on my laser with text going misaligned yet not when I swapped the control board over to an 8 bit Cronos. Thanks anyway I'll certainly have a look and a play.

On Tue, 28 Dec 2021 at 22:36, CBDesignS @.***> wrote:

@Lazarus-Rising https://github.com/Lazarus-Rising MKS is still supporting v1 hardware on the mks dlc32 ! they released firmware on 7th dec. the 13th dec and the most recent released just a few days ago on the 22nd december. I know their support is shit but they are trying more than they used to. the v2 boards are just because they ran out of hardware and to keep ripping .. sorry making money they had to change hardware and make a new revision of the boards.

— Reply to this email directly, view it on GitHub https://github.com/bdring/FluidNC/issues/205#issuecomment-1002308089, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT77TGXEIAEUEQ6TWD5XRKLUTI3V3ANCNFSM5KX7M2MA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

mhtngrbfe commented 2 years ago

Hello. In the latest firmware (V2.0.8_H24_20220108_N_CNC), a lot has been fixed (and on the Z axis) except for parking! To fix parking, you need to register (like any other settings): $ HOMING / CYCLE0 = Z $ HOMING / CYCLE1 = XY