Filament run out detection is mostly useless unless you are there when it happen, I doubt anyone would miss it.
Power outage resume is equally useless unless the power resume like immediately, once the bed get cold the print will pop up and you have to start it over. I would not waste time on it.
BTW, one of the A5S I upgrade the firmware is having the LCD screen issue, I am waiting for the foil tape to arrive so I can do the trick on your video to fix this issue.
Why didn't the stock firmware has any problem with the touch screen?
I agree with your assessment - that's why they haven't been a priority. Filament run out can be a useful hack as an easy code-free-way to allow changing colour etc, but still low on the priority list.
Sorry, I really don't know why the stock firmware doesn't have problems - it could be a different SPI speed, or perhaps just a marginal signal. I tried a few things, but had no luck until I added the foil tape.
From what I can see the problem with the touch screen is only happen when the print starts, once the print is finish the touch screen return to normal. So far only one the A5S is having this problem, there is still one more A5S still in stock firmware, I shall see what happen with the last one after I upgrade the firmware.
I tried to compile the firmware myself on Windows with VSC but it fails.
In file included from c:\users\thomas\.platformio\packages\toolchain-gccarmnoneeabi\arm-none-eabi\include\stdlib.h:19,
from c:\users\thomas\.platformio\packages\toolchain-gccarmnoneeabi\arm-none-eabi\include\c++\8.2.1\cstdlib:75,
from c:\users\thomas\.platformio\packages\toolchain-gccarmnoneeabi\arm-none-eabi\include\c++\8.2.1\stdlib.h:36,
from C:\users\thomas\.platformio\packages\framework-arduinoststm32\STM32F1\cores\maple/wirish.h:41,
from C:\users\thomas\.platformio\packages\framework-arduinoststm32\STM32F1\cores\maple/Arduino.h:30,
from Marlin\src\HAL\HAL_STM32F1\HAL_sdio_STM32F1.h:28,
from Marlin\src\HAL\HAL_STM32F1\HAL_sdio_STM32F1.cpp:26:
C:\users\thomas\.platformio\packages\framework-arduinoststm32\STM32F1\system\libmaple/stm32f1/include/series/gpio.h:489:15: error: duplicate 'inline'
static inline __always_inline void afio_exti_select(exti_num exti, exti_cfg port) {
^~~~~~~~~~~~~~~
C:\users\thomas\.platformio\packages\framework-arduinoststm32\STM32F1\system\libmaple\include/libmaple/nvic.h:112:15: error: duplicate 'inline'
static inline __always_inline void nvic_globalirq_enable() {
^~~~~~~~~~~~~~~
C:\users\thomas\.platformio\packages\framework-arduinoststm32\STM32F1\system\libmaple\include/libmaple/nvic.h:119:15: error: duplicate 'inline'
static inline __always_inline void nvic_globalirq_disable() {
^~~~~~~~~~~~~~~
In file included from c:\users\thomas\.platformio\packages\toolchain-gccarmnoneeabi\arm-none-eabi\include\stdlib.h:19,
from c:\users\thomas\.platformio\packages\toolchain-gccarmnoneeabi\arm-none-eabi\include\c++\8.2.1\cstdlib:75,
from c:\users\thomas\.platformio\packages\toolchain-gccarmnoneeabi\arm-none-eabi\include\c++\8.2.1\stdlib.h:36,
from C:\users\thomas\.platformio\packages\framework-arduinoststm32\STM32F1\cores\maple/wirish.h:41,
from C:\users\thomas\.platformio\packages\framework-arduinoststm32\STM32F1\cores\maple/Arduino.h:30,
from Marlin\src\HAL\HAL_STM32F1\../../inc/../HAL/HAL_STM32F1/HAL.h:41,
from Marlin\src\HAL\HAL_STM32F1\../../inc/MarlinConfig.h:30,
from Marlin\src\HAL\HAL_STM32F1\HAL_Servo_STM32F1.cpp:26:
C:\users\thomas\.platformio\packages\framework-arduinoststm32\STM32F1\system\libmaple/stm32f1/include/series/gpio.h:489:15: error: duplicate 'inline'
static inline __always_inline void afio_exti_select(exti_num exti, exti_cfg port) {
And many more of these error messages. Maybe you have an idea.
Thank you for pointing this out - it looks like some changes in some of the libraries have broken things recently. You can download a working build here - with libraries included - that you can compile in VSC.
I am short on time, but my next plan is to create a new A5S/A1 build from the latest Marlin 2.0 build, but I haven't been able to get around to that.
There's been some layer shifting problems that people have reported, and from what I have been following on the Marlin github it sounds like there may be some timing issues in 32bit that need to be fixed.
Sadly this did not work. I think the archive is missing all the libraries from your "platform" library and uses the automatically installed ones.
I also tried to uninstall all VSC and PlatformIO stuff (including manually deleting leftovers from my profile folder) and reinstall VSC + PIO again. No luck.
No problem. It was just a try, because I wanted to persist some stepper settings in firmware, instead of eeprom and rising the nozzle temperature a bit. I can only reach 235C and hoped to get up to 240 maybe 245C.
@Simulanon - once I get the filament run out sensor working, that is a feature I definitely plan to add. However, for now you'll have to do it manually unfortunately. Thanks for the suggestion.
New beta firmware for test - the goal of this one is to fix the layer shifting problems that have been occurring. After this is stable I'll be adding the new features like filament change, and filament run out sensor.
Hi, here my results. First I’ve tried with the previous firmware and I got layer shifting. Today I’ve updated the firmware and I reprint the file, please take a look on the pictures below
As you can see the problem has been solved in this update
The challenging thing is, that there are many factors that can cause layer shifting. For example, the stock bearings that come with the A5S are 💩. I replaced mine with these, and my printer moves more smoothly now. I have a little more testing to do, but at least seeing some improvement is very encouraging.
I had the layer shift around 12mm height and only on the Y axis. I also replaced the bearings because the noise was just horrible, so my X and Y bearings aren't the originals.
This firmware update is an improvement so yes is very encouraging.
@Samuel Pinches during my test I've noticed that when you stop/pause your print, the nozzle stay at the same position. On the stock firmware, after stopping the print the nozzle lift and move to X home. Is it possible to modify the firmware to change that thing?
Hey guys. Just joined the forum after having received my first 3D printer (an A5S).
After doing lots of research, i definitely want use OctoPi to run the printer which was a nightmare with the stock firmware. I was getting difficulty connecting, and all kinds of weirdness going on that never allowed me to even start a print. Upgrading to the latest stock firmware resolved connectivity problems, but still no print.
That's when I started looking around for firmware and found this thread. I flashed the Beta 5 bin, did the multi point bed leveling, and was able to connect and print with OctoPi with no hiccups in connectivity or starting a print.
I did have pretty severe layer shifting during the print, so it ultimately failed, but I have not tried any of the aforementioned tweaks yet. Would the ribbon shielding help with that at all? Or should I try the firmware from Samuel's post on May 19th? (I can't tell if that's a newer build than Beta 5)
Please do try that may 19th firmware - it is newer. I haven’t yet had time (I have no spare time at the moment) to make a proper new build for A1 either, but I do recommend try that quick-and-dirty build on the A5S, as it seems to have managed to fix the layer shift issue for some people.
The ribbon shielding will only help with LCD problems, will not affect printing.
Yep I’ve been following along with this work, very grateful for those who found the cause. I patched the code with an earlier version of their fix, but I need to redo with a fresh marlin 2.0 build.
@Spark - yes, There was a bug in the firmware that was causing shifting. While layer shifting is still a possibility for many reasons, at least that major bug was fixed definitively.
Comments
Sorry, I really don't know why the stock firmware doesn't have problems - it could be a different SPI speed, or perhaps just a marginal signal. I tried a few things, but had no luck until I added the foil tape.
I tried to compile the firmware myself on Windows with VSC but it fails.
There's been some layer shifting problems that people have reported, and from what I have been following on the Marlin github it sounds like there may be some timing issues in 32bit that need to be fixed.
I also tried to uninstall all VSC and PlatformIO stuff (including manually deleting leftovers from my profile folder) and
reinstall VSC + PIO again. No luck.
As you can see the problem has been solved in this update
as shown with the photo, I still have layer shifting with the newest firmware update @aestrems
This firmware update is an improvement so yes is very encouraging.
@Samuel Pinches during my test I've noticed that when you stop/pause your print, the nozzle stay at the same position. On the stock firmware, after stopping the print the nozzle lift and move to X home. Is it possible to modify the firmware to change that thing?
Thank you for all
After doing lots of research, i definitely want use OctoPi to run the printer which was a nightmare with the stock firmware. I was getting difficulty connecting, and all kinds of weirdness going on that never allowed me to even start a print. Upgrading to the latest stock firmware resolved connectivity problems, but still no print.
That's when I started looking around for firmware and found this thread. I flashed the Beta 5 bin, did the multi point bed leveling, and was able to connect and print with OctoPi with no hiccups in connectivity or starting a print.
I did have pretty severe layer shifting during the print, so it ultimately failed, but I have not tried any of the aforementioned tweaks yet. Would the ribbon shielding help with that at all? Or should I try the firmware from Samuel's post on May 19th? (I can't tell if that's a newer build than Beta 5)
The ribbon shielding will only help with LCD problems, will not affect printing.
- Should fix layer shifting problems.
- More responsive touch screen.
- Entire new build of Marlin!
- Hidden easter eggs too
Download hereHowdy, Stranger!
RegisterIt looks like you've been lurking for a while.
If you register, we will remember what you have read and notify you about new comments. You will also be able to participate in discussions.
So if you'd like to get involved, register for an account, it'll only take you a minute!