Trouble with moving Voxelab X3 Max over to Marlin.

[ssullivansr]

Good morning.
I have a stock X3 Max that started to have issues with the inductive sensor drawing up before printing so I decided to move it over to Marlin using Using MRIscoCProUI Aquila_N32_IND_UBL-ProUI-EX-10-01.bin I did the DWIN update first and got the blue to orange screen as I was supposed to. But no matter how many times I upload the file under different file names it is always the same result. It is like it is running two different processes at the same time. I would like to get this board fixed before investing in a new one.
Is there a file that I could run first to wipe out the .BIN file instructions?

Here is a link of what I am seeing on the screen.

https://drive.google.com/file/d/1Q_bJiNaM_7g9hAr9jTDs9l1sfuIaA3g5/view?usp=sharing

Any help is greatly appreciated.

[Mik-S-UMS]

If the Z axis is only moving up when homing this is a problem with the sensor itself not the firmware.
(assuming you are using the one with IND in the filename)
The exact cause is not known but could be the cable is too tight so there is a poor connection on one of the wires inside the sensor so the signal is not getting to the motherboard. You can see more here.

The problem with your display is that it's FW did not install. The screens are very picky and need the SDcard to be properly prepared.
They have to be formatted to FAT32 4096 block size, the card needs to be at least less than 32GB, and don't use a Mac to prepare it as it leaves hidden files that will make it fail.
If it flashes blue than orange it has failed. It should stay blue for a second or so first before orange if successful.

[Mik-S-UMS]

OK we can focus on getting the display working properly first.
It looks like it did partially install and that may be why it stayed blue a little longer.

Are you using a Mac? What size SDcard are you using?
Try re-fomatting the SDcard or even better using another one.

Voxelab customer support was declining these past few years but is now non-existent as they have shut down.

[classicrocker883]

if its not something with the SD card (just a bad cheap one, or formatted wrong) then it could be the following:

the firmware looks like its using a different .ICO than installed. double check the DWIN_SET folder used to install, make sure it has a file 9.ICO

flash the most recent display assets here - i would use any of them except (Voxelab Original Light)

Also double check you DO have an N32 board. and if all else, unplug some things from the board like the Z probe sensor and then reflash.

[ssullivansr]

I have tried all of that and it is definitely an N32 as i have had issues with it from the beginning with the bed heating etc.
I am thinking of just replacing the board with a BigTreeTech SKR board and touch screen. Just be done with the voxelab specific parts

if I resolved it in this manner would this be an acceptable replacement. The only plans i have for it in the future is to increase the build height to 600mm or 1000mm

[classicrocker883]

if you go that route, you wont be able to change the build volume unless you either compile the firmware yourself, find files already made, or continue with ProUI. which it does have support of this board, just not touchscreen.

if you wanted to keep things as original as possible, I would get either the E3 Freeruns board or Creality 4.2.7, which are probably not as expensive as the BTT SKR Mini

another thing is did you rename the firmware file you are trying to install?
that it will not take being the same name. not to mention the .bin file must be in a folder called firmware. if that doesn't work put it in the root.

[ssullivansr]

I ordered the creality board and will reach out when i have it installed.
thank you so far

[classicrocker883]

if its printing like 25mm up higher, then it can be the Z offset. change the value to -25 or whatever how much higher it is.

[ssullivansr]

I have installed the new motherboard and ia am now experiencing this when i turn it on. Do I need a different controller or a different dwin file

https://drive.google.com/file/d/1Q_bJiNaM_7g9hAr9jTDs9l1sfuIaA3g5/view?usp=drivesdk

[Mik-S-UMS]

This is the exact same problem as before, your screen FW did not install. (or you posted the same link as in your first post)
Try a different SDcard.

[classicrocker883]

https://www.youtube.com/watch?v=fl5rRF7hlUg&t=117s

here is how to do it. rename to just DWIN_SET

[ssullivansr]

https://drive.google.com/file/d/1ZkHdIBsswais7taLANS-Iabme7XK3rfR/view?usp=drivesdk

[Mik-S-UMS]

What FW (full filename) did you install on it. The screen still has not been updated.

[classicrocker883]

you're using the original DWIN_SET that was installed from stock.

you must rename to DWIN_SET
see the Wiki on how to install on the display. or the readme

the Voxelab Red DWIN_SET should look like this

[ssullivansr]

Is it looking for a z stop? There isn’t one on the x3 max but i can throw one on it

[Mik-S-UMS]

It depends on what FW you installed

[ssullivansr]

I have done the original And the red.
I have a second screen that I can use.
what file should I use and for which board

[Mik-S-UMS]

For the new board you have to install the suitable FW. Which one have you used?
You will also need to install the screen FW, if you are still seeing it as white and the voxelab logo then the install failed.