[FluidNC Issue#1414] Problem: two boards are gone, there is no more any output to the A4988

#1 – SirGit1646 于 2024-12-28

I do not understand why reinstalling GBRL32 or FLUIDNC 3.8.0 the boards are no more working , two brand new boards tested with the original GBRL32 before installing FLUIDNC

#2 – bdring 于 2024-12-28

You need to create a config file for you controller and machine. See the wiki

#3 – SirGit1646 于 2024-12-28

Thanks for your answer,I use the config file from a running dlc32 with
fluidnc 3.8.0, but also no success.
regards
Sigi

bdring @.*> schrieb am Sa., 28. Dez. 2024, 15:17:

> You need to create a config file for you controller and machine. See the
> wiki
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564335769>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIF4FH2QM33SM5P4KVOD2H2XJDAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGMZTKNZWHE>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#4 – breiler 于 2024-12-28

It is impossible to debug with this little information.

Share the configuration that you think is supposed to work. Share the the startup log when trying to boot the controller with that configuration. Take a picture of your controller setup.

#5 – SirGit1646 于 2024-12-28

thanks I will do so, and mail it to you

Joacim Breiler @.*> schrieb am Sa., 28. Dez. 2024,
15:52:

> It is impossible to debug with this little information.
>
> Share the configuration that you think is supposed to work. Share the the
> startup log when trying to boot the controller with that configuration.
> Take a picture of your controller setup.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564342232>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIF6SE3HEQAWJVUIFAOD2H23JHAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM2DEMRTGI>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#6 – breiler 于 2024-12-28

Mail will not work, you will have to attach them to this GitHub issue from the web page.

#7 – SirGit1646 于 2024-12-28

thanks

Joacim Breiler @.*> schrieb am Sa., 28. Dez. 2024,
16:02:

> Mail will not work, you will have to attach them to this GitHub issue from
> the web page.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564348567>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIFZO5EFZJINNS5GU2OD2H24OVAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM2DQNJWG4>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#8 – bdring 于 2024-12-28

Did you set the new config as the active config with the Installer or via $Config/Filename=yourfile ?

#9 – SirGit1646 于 2024-12-28

yeah I did, I simply overwrite the existing with the config of the working
one

bdring @.*> schrieb am Sa., 28. Dez. 2024, 16:08:

> Did you set the new config as the active config with the Installer or via
> $Config/Filename=yourfile ?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564356102>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIF4M5ECGFWGFFOPJTB32H25GFAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM2TMMJQGI>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#10 – SirGit1646 于 2024-12-28

the funny thing is I can install I can change the config but no success at
all, Wifi is working usb connection is working, non of my dlc32 , tinybee
ever gave me trouble

S. Repolust @.*> schrieb am Sa., 28. Dez. 2024, 16:10:

> yeah I did, I simply overwrite the existing with the config of the working
> one
>
> bdring @.*> schrieb am Sa., 28. Dez. 2024, 16:08:
>
>> Did you set the new config as the active config with the Installer or via
>> $Config/Filename=yourfile ?
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564356102>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/ASVRIF4M5ECGFWGFFOPJTB32H25GFAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM2TMMJQGI>
>> .
>> You are receiving this because you authored the thread.Message ID:
>> @.*>
>>
>

#11 – bdring 于 2024-12-28

This is wrong in your startup messages.

“
[MSG:INFO: Configuration file:config.yaml]
[MSG:INFO: Machine Default (Test Drive no I/O)]
“

You need to post startup messages that are correct.

#12 – SirGit1646 于 2024-12-28

temporär.txt

“
[MSG:INFO: FluidNC v3.8.0 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is spiffs]
[MSG:INFO: Configuration file:config.yaml]
[MSG:INFO: Machine MKS DLC32 XYZ]
[MSG:INFO: Board MKS DLC32 2.0]
[MSG:INFO: I2SO BCK:gpio.16 WS:gpio.17 DATA:gpio.21]
[MSG:INFO: SPI SCK:gpio.14 MOSI:gpio.13 MISO:gpio.12]
[MSG:INFO: SD Card cspin:gpio.15 detect:NOPIN freq:8000000]
[MSG:INFO: Stepping:I2S_stream Pulse:4us Dsbl Delay:0us Dir Delay:1us Idle Delay:250ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Shared stepper disable I2SO.0]
[MSG:INFO: Axis X (0.000,100.000)]
[MSG:INFO: Motor0]
[MSG:INFO: stepstick Step:I2SO.1 Dir:I2SO.2 Disable:NO_PIN]
[MSG:INFO: X Neg Limit gpio.36]
[MSG:INFO: Axis Y (-150.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: stepstick Step:I2SO.5 Dir:I2SO.6:low Disable:NO_PIN]
[MSG:INFO: Y Neg Limit gpio.35]
[MSG:INFO: Axis Z (-40.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: stepstick Step:I2SO.3 Dir:I2SO.4:low Disable:NO_PIN]
[MSG:INFO: Z Neg Limit gpio.34:low]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: PWM Spindle Ena:NOPIN Out:gpio.32 Dir:NOPIN Freq:5000Hz Period:8191]
[MSG:INFO: Using spindle PWM]
[MSG:INFO: Probe gpio.22:low]
[MSG:INFO: AP SSID unimat3 IP 192.168.0.254 mask 255.255.255.0 channel 1]
[MSG:INFO: AP started]
[MSG:INFO: WiFi on]
[MSG:INFO: Captive Portal Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
“

#13 – bdring 于 2024-12-28

I made your post readable.

It looks like FluidNC is working fine. If your motors are not moving, you have a hardware problem.

#14 – SirGit1646 于 2024-12-28

no , I don’t have, I just started my Mill with the setup I did mail to you

bdring @.*> schrieb am Sa., 28. Dez. 2024, 16:35:

> I made your post readable.
>
> It looks like FluidNC is working fine. If your motors are not moving, you
> have a hardware problem.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564363583>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIF3CINSCPHWVAWLVWJL2H3ALVAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM3DGNJYGM>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#15 – bdring 于 2024-12-28

It works now?

#16 – SirGit1646 于 2024-12-28

no it ist the board with fluidnc 3.8.0

bdring @.*> schrieb am Sa., 28. Dez. 2024, 16:39:

> It works now?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564364335>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIFYFTKSC5KAT5NKFSLT2H3A2ZAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM3DIMZTGU>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#17 – bdring 于 2024-12-28

Please do not use email to respond to Github issues.

Use the latest version of FluidNC, v3.9.3.

We are currently not supporting MKS DLC32 because it uses non compliant I2S chips. We might have a solution with this branch, but we are awaiting users to test it. That may take a few more weeks.

#18 – SirGit1646 于 2024-12-28

yeah but I installed 3.8.0 and can not get it back to work, is it possible
3.9.3 messed up the Board, then even installing back GRBL32 got the board
never to work

bdring @.*> schrieb am Sa., 28. Dez. 2024, 16:48:

> Please do not use email to respond to Github issues.
>
> Use the latest version of FluidNC, v3.9.3.
>
> We are currently not supporting MKS DLC32 because it uses non compliant
> I2S chips. We might have a solution with this branch
> <https://github.com/bdring/FluidNC/tree/BetterI2SClocking>, but we are
> awaiting users to test it. That may take a few more weeks.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564366228>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIF36KVZIBKPG5P3PXDD2H3B4FAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM3DMMRSHA>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#19 – bdring 于 2024-12-28

The only startup messages from 3.9.3 we have seen show user errors with the config file.

#20 – SirGit1646 于 2024-12-28

yeah I changed back to 3.8.0 with the working .yaml but also no success

bdring @.*> schrieb am Sa., 28. Dez. 2024, 16:58:

> The only startup messages from 3.9.3 we have seen show user errors with
> the config file.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564368197>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIF6G3VOPE5HILZPLXO32H3DDBAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM3DQMJZG4>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#21 – bdring 于 2024-12-28

The only way FluidNC can break a controller is with a bad config file. For example, you create an output on a shorted pin.

Ask MKS what the problem is.

#22 – SirGit1646 于 2024-12-28

as did say I installed back v3.8.0 with the exact same config.yaml but
still not working

bdring @.*> schrieb am Sa., 28. Dez. 2024, 17:05:

> The only way FluidNC can break a controller is with a bad config file. For
> example, you create an output on a shorted pin.
>
> Ask MKS what the problem is.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564369689>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIF6EHELE7OUB5RNRSOL2H3D47AVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM3DSNRYHE>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#23 – bdring 于 2024-12-28

OK, I will wait for MKS or other MKS users to respond.

#24 – SirGit1646 于 2024-12-28

ok please let me know if get any info, for the moment I would not install
fluidnc…is too scary 😂

bdring @.*> schrieb am Sa., 28. Dez. 2024, 17:32:

> OK, I will wait for MKS or other MKS users to respond.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564374979>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIF7SU7QMM672Y2WIVEL2H3HBZAVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGM3TIOJXHE>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>

#25 – bdring 于 2024-12-28

Just watch for new releases and read the release notes.

#26 – SirGit1646 于 2024-12-28

thanks, I’m soo sorry until now fluidnc did work perfectly

bdring @.*> schrieb am Sa., 28. Dez. 2024, 20:02:

> Just watch for new releases and read the release notes.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/bdring/FluidNC/issues/1414#issuecomment-2564404825>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ASVRIFZBFCFF2KJWFUEVFGD2H3YV5AVCNFSM6AAAAABUJ2UPGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGQYDIOBSGU>
> .
> You are receiving this because you authored the thread.Message ID:
> @.*>
>