505 is not the stable version. The one that works is. 505 is the new beta marlin builder version that is not ready for release yet. I have a list of things that need to still be fixed.
When I get my archim back I will start to trouble shoot that, for now I am working on the rambo, mini and skr. To be clear, 505 is most certainly beta for every board other than the SKR.
That stepper issue has happened before, and it was a processor timing issue. About a year back. Sounds like the same thing has popped back up. Something to do with them making changes to the Archim2 and also changing the Archim1’s for some reason.
@vicious1 any ideas about the crashing issues then with the stable firmware? See start of thread. I’ve tried a tonne of stuff and Jeff’s suggestion has been the only thing that’s sort of worked (in the sense that it doesnt seem to crash at least).
After a fresh flash it still crashed?
Interference is a common issue, we have compressors kicking on and garage refrigerators making enough line noise to reset boards. Bundling LCD cables with stepper lines or power cables can also do it. They should be run as far from the rest of the wires as possible.
Have you cleaned up your wiring since that first picture?
That is the firmware I would assume most archim users are running so you would be looking for something outside the firmware.
@vicious1 i will try again to minimize interference and use the old firmware and report back, but FYI it was crashing even with just LCD and power supply connected (so yes much cleaner wiring, what you are seeing in photo is product of days of debugging). I’m not aware of any sources of interference or anything turning on in the garage itself. Also doesn’t explain why 505 hasn’t crashed.
He only installed 505 because I asked him to. My thought was the next step would be reporting the errors up the chain to Marlin.
Matt, you shouldn’t he hot swapping the motors. It can hurt the drivers (I’ve heard, never broken one myself that way).
Reversing course and focusing on the allted version is good. But I’m not sure where else to go with it.
No worries. I am pretty sure the new versions do not work in either platform.io or arduino, two different issues. I have not passed it to ultimachine yet as I have not heard back about the PWM issue and it seemed more important, maybe that will get them to fix both at the same time by trying to use the most recent version. At the same time, I might not have heard back because they still have my archim board and know I can’t test it?
Can you test this with the LCD not plugged into the board. You can monitor the connection with repetier host.
This is not a problem I have heard of and the LCD is by far the Most questionable component in this chain.
Interesting you say there are no issues with 505, the only difference we have is some added LCD timing edits. So either those need to get transferred to your version of the current stable firmware, or you have a bad LCD or SD card.
Same dual firmware, LCD timing edits.
Thanks! I’m trying without the LCD right on the older firmware now per your suggestion. You are correct that this is a combo I haven’t tried. Agreed that the 505 working is weird. All I can say to that is that it was stable for the two days I tested it (just with steppers not working). That doesn’t guarantee 100% that it is stable because I’ve observed the old firmware crashing within seconds of startup, and after hours of running. But on average it seems to crash in less than an hour.
I have never inserted an SD card into it, haven’t tried cutting anything yet.
LCD being the bad component would be great news.
If it’s stable without the LCD I will try your timing edits zip.
@vicious1 I had the controller on connected to Repetier without the LCD for a day and a half on old firmware and it was stable. So seeing as an issue with the LCD is very possible I went to try to flash the firmware you attached and I get the following error in configuration.h:
unknown type name ‘opt_add’
Referring to this line:
opt_add ST7920_DELAY_2 “DELAY_NS(250)”
In the meantime I’m trying it with
#define ST7920_DELAY_3 DELAY_NS(250)
#define ST7920_DELAY_2 DELAY_NS(250)
Since that’s what 505 seems to do but I have no idea if this is going to have the desired effect. Please advise 
Yeah, shoot I copied the builder line instead of the output. your edit is correct.
Thanks… soo… bummer though… reattaching the LCD and running with the updating code didn’t work. Crashed at some point within about an hour of being connected and just sitting there.
I would appreciate if you have any other ideas on what to try.
Meanwhile I’m going to run again with LCD physically disconnected to keep verifying stability without LCD attached so that we at least know we are barking up the right tree.
Yes try without it plugged in.
If that works double the values 250-500
Still no luck with the 250 or the 500. Having LCD controller unplugged works - I’ve clocked a couple days worth of “on” time with no crashes. Adding LCD controller crashes. I’ve got a new LCD controller (still the reprap discount but different vendor) arriving tomorrow to try to rule out any issue with the LCD itself.
Hey @vicious1 so further to my last update, bad news. Replacing the LCD controller and LCD cables does not appear to have fixed the issue. It actually did stay on without crashing for most of yesterday, but today it crashed several times in short order including once directly on startup.
There is definitely nothing starting up in the garage at the same time since I witnessed a couple of the crashes first hand in short succession and know that nothing else was running.
The sheer unpredictability of the crashes is really frustrating both for trying to troubleshoot it and for what the heck it could be.
I’m all ears for other ideas.
power supply?
What are you using and how is it plugged in? You are not using the little green adapter are you?