Those using Aquila X3

[classicrocker883]

Please share any information which may help others use this firmware.

For instance, I am wondering what chips are on the mainboards. One user said theirs is an N32, specifically N32G455REL7

If anyone finds they have like a GD32 or STM32 or other on their mainboard please let me know here. I will update the release builds to include those capabilities.

edit:

if you have information regarding configurations (like in Configuration.h + _adv.h) you can post it here.

Any other features or options you think would help or should be changed too.

[Smite0WPI]

So - i saw there's the X3 firmware in the current build, is there a chance you could include the X3 Max (400x400x400 build volume version of X3) at some point?

i'm using a mix of this and the older Alex firmware on my Aquila's (i have a collection of STM32, GD32, N32, and H32's across normal Aquila's and X2's), but just picked up the X3 Max.

I'm going to be setting it up after Christmas, and plan on opening it up to do ferrule's on the power wiring as well, so i am more than happy to gather any information you might want in the process, as well as testing things etc.

[Smite0WPI]

i can give this a try at some point... i picked up 4 more returned Aquila X2's that need to be built... at least 2 or 3 of them are H32's...

looking at the Marlin Flash dump thing, do i need to compile my own version of the firmware per that first step? or is that modified M300.cpp file already included in the latest H32 firmware? It's been a decade or more since i've worked with compiling stuff, so i might struggle a bit there...

Not sure if it's the same issue i was having, but i would start the H32 printers with the SD card installed, and it could get an hour or more into the print before the printer would lock up and restart.

[classicrocker883]

with the more recent firmware, there is that issue of it restarting with the SD card. but there is a previous release I think in NOVEMBER which doesn't have that issue, but the other previous issues are there like with it not saving, or at least if u tried to save it would restart.

the workaround for this issue is to print using a USB, like through a computer or octoprint. its no problem if you cant compile your own, but yes you would need to use that modified M300.cpp, however I would be able to compile it for you.

but thats great you found some returned printers, I actually found an X2 as well that looks like it was never put together. still havent built it either. hopefully this issue is the last thing that needs to be fixed with those darn H32 boards.... the black sheep.

recently the chips source code was added to Marlin's main repo, so thats a step forward.

[Jlsmith97]

@classicrocker883 By any chance were you able to make a version for the Aquila X3 Max? I downloaded the N32 ProUI and went to configure the Physical Settings but the max size I can input is 230 rather than 400. Any chance you'd be able to help me out with getting a version configured to the 400x400x400 build size?

[saggevlad]

Hello. I have aquila x3, the regular version of N32. I uploaded the firmware Aquila_X3_N32_UBL-ProUI.bin and decided to test it.
I discovered a strange bug - when you heat the head to 235 degrees to print ABS, the printer sometimes heats it up to 227, then drops it to 225 and lower, and then gets the error: “Killing heater switch off printer!”
Sometimes it heats up normally. I uploaded the stock firmware - everything became normal. I also noticed that the board blower fan does not turn on during warm-up, but in my native case it starts blowing stronger.
Also, while loading filament, it is impossible to stop the process of feeder movement with an encoder; probably adjustment is by timer. The head temperature is still too low - 180 degrees for loading plastic.

[classicrocker883]

@saggevlad you may need to do a PID tune.

when you start heating go to Prepare and Hotend Temp Graph, how does that look? it should not be up and down but steady. when it's first near the temp it might go up and down a couple times that's normal, but the remaining time should be flat.

if a PID tune does not help, try resetting the PID values to 0.

[classicrocker883]

@Jlsmith97 are you sure the max size you and put is 230? that is for the Bed size. but there are other values below that which should say Max X Pos or like that. those you should be able to increase

[Jlsmith97]

@classicrocker883 this is what I have the values changed to currently

W_SAFETY_STOP

// @section geometry

// The size of the printable area
#define X_BED_SIZE 390 // MRiscoC Max usable bed size
#define Y_BED_SIZE 390 // MRiscoC Max usable bed size

// Travel limits (linear=mm, rotational=°) after homing, corresponding to endstop positions.
#define X_MIN_POS 0 // MRiscoC Stock physical limit
#define Y_MIN_POS 0 // MRiscoC Stock physical limit
#define Z_MIN_POS 0
#define X_MAX_POS 400 // MRiscoC Stock physical limit
#define Y_MAX_POS 400 // MRiscoC Stock physical limit
#define Z_MAX_POS 400 // Ender Configs

[classicrocker883]

ok those values should work for your setup right? the MESH_INSET values should automatically adjust for the bed size, so if you look in the mesh settings menu where the mesh inset - min/max | x/y - is by default the values are Y_BED_SIZE - MESH_INSET in your case Max: (390 - 10), Min: 10.

originally I was asking when using the precompiled firmware, in physical settings menu where the bed size is 230, you should be able to change the max pos to 400. and then change the bed size to 390. after that, go to the mesh settings menu where the mesh inset is, select maximize area to reset to the new values. after that, you can adjust the inset accordingly, probably set that to 380 (390 - 10), and 10.

[Jlsmith97]

Ah yes I have tried both compiling myself and editing the precompiled but no changes I’ve made have expanded where the auto mesh level checks. Everything respects the bed size except the leveling menu

[saggevlad]

Good day. And if I replace the induction sensor to a 3DTouch with a hall sensor, will it work on the Aquila_X3_N32_UBL-ProUI.bin firmware?
The inductive sensor is connected to the GVI pins and the BlTouch is connected to the GO pins and the sensor servo is connected to the GVI pins. How to connect it correctly to work with this firmware?

[saggevlad]

don't work. change firmware.

[classicrocker883]

I'm not sure, I'm not familiar with these types of probes. is there another type of firmware or source code which can be referenced which uses this probe type?

[saggevlad]

I checked, the native one for X3 definitely doesn’t work. I removed the induction sensor, and connected the 3DTouch according to the GVI standard - servo, GO - z pos. I uploaded the firmware from the X2 series - Aquila_N32_BLT-ProUI.bin, everything works fine.

[dbhosttexas]

Mine is an N32, have not put this firmware on it yet. Trying to get my G32 Aquila happy first, Then get my X3 Max out of warranty then I will play with the firmware. It would be nice to have the capabilities of this firmware on this machine....

[dbhosttexas]

@classicrocker883 The fans were recommendations from 3DPrintSOS, my OE fans were getting LOUD, as in early 2000s Dell rack mount servers loud.

Curious about the CRC, how are you getting it to where it needs to go? Noisy fans is someething I just can't deal with, especially at that level. The WinSinn fans are nice and quiet. I really wasn't going for the LED looks, but at least it kind of goes with my gaming laptop and mouse though :-)... Anyway I am assuming just kind of squirt it up in the gap between the fan blade and motor?

[classicrocker883]

Anyway I am assuming just kind of squirt it up in the gap between the fan blade and motor?

yep exactly right. just a small squirt right in the gap, I would say do this every couple months or maybe depends how much you actually print too. if you look through the transparent fan you can see the hydraulic sleeve bearing and the ever so tiny dab of grease. that grease they use is cheap chinese might as well be Vaseline than anything meant for machines/moving parts.

the CRC lube can rejuvenate a bad/dying fan, at least cut down on the noise, but its better to use before that happens. I experimented drilling a small hole and trying it that way... was a mistake because it threw off the balance. so right into the gap is best, may need a paper towel ready when it gets turned on. I dont believe ball bearing or the Sunon Mag-Lev (great fan type) need that, but i guess it wouldn't hurt.

some people complain about the LED fans not putting out enough air. yeah they are much quieter, but they dont push as much air. which is fine, because it does the job anyway.

[yrabbit]

Dual Balls in the Chinese version may have cubic balls, so the noise will still be the same regardless of the degree of blurring.
Sunon Mag-Lev on the other hand... hmm... this magnetic thing may well depend on gravity and work only in one specific position relative to the horizon, no?

[classicrocker883]

I'm not sure if the Mag-Lev work only in one position or doesn't matter. I just know I replaced the mainboard fan with one of the sleeve bearing LED fans the same time I swapped the hotend fan, and the one laying horizontal underneath started with a terrible noise first.

so it seems the sleeve types are best in on position, and dual ball bearing could go any direction.

I've swapped the power supply 60mm with a Mag-Lev in both my Aquila and Aries, and it's gotta be one of the best - quiet, and long lasting. I would replace all the fans with that type if I could. went for dual ball for the part cooling fan because they should last longer, and kept the LED for hotend because A. it looks cool. B. it is a sign that the machine is ON. C. so far with lubrication they keep going.

There is documentation somewhere about the differences between the fan bearing types and how would they last longer (as well as noise).

[yrabbit]

Yeah, I'm thinking of following your example and installing MagLev in the power supply - it's currently the noisiest of all in Aquila 😞
I think it would be appropriate here to quote what I read in the Sunon documentation - the letter X in the place of the speed designation means a very fast fan and it will definitely be very loud. In fact, every swearing in the comments on aliexpress about noise is due to the fact that the buyer did not pay attention to the fact that he was offered the VX model - yes, a magnet suspension, but very high speeds. 😉

[zwt1997]

Hello, my machine is the Aquila standard version and the screen is horizontal. Does the latest firmware support him, can you switch to Chinese display? Thank you

[zwt1997]

Oh yes, my controller model is STM32F103RET6

[yrabbit]

After replacing the display firmware, it will be vertical and the latest release will work. But I don’t think you’ll be able to switch to Chinese. I could be wrong.

[zwt1997]

Yes, I've updated to the latest firmware, it's in portrait mode, and the print quality is good. I couldn't find the Chinese switch option, I changed the language from marlin, but the screen was garbled

[classicrocker883]

in this file, Marlin\src\core\language.h

it may be possible to use zh_CN or zh_TW

#define LCD_LANGUAGE zh_CN
// zh_CN      Chinese (Simplified)
// zh_TW      Chinese (Traditional)

otherwise MarlinFirmware/Marlin has the option to choose between English and Chinese., however, this doesn't have the same features or all the features as this repo MRiscoCProUI repo.

[PINK688]

Hi, I just signed up as I need help, I hope it's the right place, homuna voxelab x3 max, I downloaded the modified firmware in this link, after installing it I noticed that the Z axis, when homing, didn't work, in no way, I wonder how I could solve this problem, thanks. https://github.com/classicrocker883/Marlin-Alex/releases/tag/v2.0.1 (voxelab aquila ULB 15X15 400x500 N32 bin.)

[Mik-S-UMS]

You need to use one that has IND for in the filename for the sensor to work, like Aquila_N32_IND_UBL-ProUI-EX-11-03.bin.

I can't remember if the Max needs a separate version or if you can set the bed size in the options.

[classicrocker883]

youre using an old outdated repo, try this:
https://classicrocker883.netlify.app/firmware-selector