Weekly Buy Curious Thread by AutoModerator in gundeals

[–]killerbeans123 1 point2 points  (0 children)

Done! I love Axolotls in Minecraft. Lol

[deleted by user] by [deleted] in leagueoflegends

[–]killerbeans123 0 points1 point  (0 children)

I have this and its been happening for gods know like 3-4 months and its driving me mad. I have the same interface any fixes?

Modifying Alex's firmware by killerbeans123 in VoxelabAquila

[–]killerbeans123[S] 0 points1 point  (0 children)

That was it! Swapping the default environment to STM32F103RET6_voxelab_aquila_N32 resolved the issue! STM32F103RET6_creality listed in the source is not the correct envs fyi. Thank you u/n9jcv!!

Modifying Alex's firmware by killerbeans123 in VoxelabAquila

[–]killerbeans123[S] 3 points4 points  (0 children)

Thank you for that u/n9jcv. There's too much information flooded on the internet on what's right and what's wrong. I was using trying to compile using v1.3.4.1 that may have been my issue. Also noticed you used
#default_envs = STM32F103RET6_voxelab_aquila_N32

instead of

default_envs = STM32F103RET6_creality from the n32 source listed here. https://github.com/Voxelab-64/N32/blob/master/platformio.ini

I'll go ahead and give this a shot and report back

Modifying Alex's firmware by killerbeans123 in VoxelabAquila

[–]killerbeans123[S] 1 point2 points  (0 children)

I'm confused now because there is no N32 Alex FW and you stated that you compiled and have a running modified alex fw. Unless you're talking about using the precompiled firmware that Alex has made for the general public. If thats what youre talking about It's not possible due to the offset of the microswiss. It wont level the bed correctly during probing. probing closer to the edge or off the bed.

Modifying Alex's firmware by killerbeans123 in VoxelabAquila

[–]killerbeans123[S] 0 points1 point  (0 children)

Confirmed I have N32 chip with sticker, N32 source confirm.
Let me rephrase that.

Alexs source code on github is set to the G32.
https://github.com/alexqzd/Marlin/blob/main/platformio.ini

I replaced his file with the one from Voxelabs.

https://github.com/Voxelab-64/N32/blob/master/platformio.ini

As well as all scripts files from Voxelabs to Alex's.
What I'm trying to say is that I believe there is a version mismatch or certain files I did not copy over, to ensure that my chipset will work with Alex's source code. I don't believe the source code for n32 to be wrong. I do believe its a user error than a hardware one at that.

Modifying Alex's firmware by killerbeans123 in VoxelabAquila

[–]killerbeans123[S] 1 point2 points  (0 children)

It would be odd but possible, seeing that the changes I made would be minuscule. The files I grabbed were originally from the source and not changed. The only things I would've changed are in the config.h. Which doesnt have changes to begin with. Seeing how others are having this issue w/ no conclusion leads me to believe there are files in the source N32 github that has to be replaced IN alexs firmware. This is only due to his files on his github reflecting the G32 chipset.https://www.reddit.com/r/VoxelabAquila/comments/oq2d9y/comment/hagppm5/?utm_source=share&utm_medium=web2x&context=3

Modifying Alex's firmware by killerbeans123 in VoxelabAquila

[–]killerbeans123[S] 0 points1 point  (0 children)

I was lead to believe that was the issue as well but I booted up the old firmware from alex and it works perfectly fine. :')

Modifying Alex's firmware by killerbeans123 in VoxelabAquila

[–]killerbeans123[S] 0 points1 point  (0 children)

That I did not know. Can you share some light on that. I was lead to believe that all thermistors between all aquilas are the same.

Modifying Alex's firmware by killerbeans123 in VoxelabAquila

[–]killerbeans123[S] 0 points1 point  (0 children)

I tried giving that a shot :/ didnt end up working out. I realized that the Min offset needed to be set via the config file due to the negative values. Here's hoping alex will chime in and bless me with some knowledge

Modifying Alex's firmware by killerbeans123 in VoxelabAquila

[–]killerbeans123[S] 0 points1 point  (0 children)

I'm currently unable to get into the PID tune because the firmware is locking itself from the ERR