No I didn’t try, though I should, as the second printer doesn’t seem to have those issues. Both are runnin 1.1.4. But I’ve linked a simple exemple of a needed fix that is included in marlin 1.1.7
I should have mentioned that on my K8200 I did hack it some (love this machine).
Not so much on my K8400.
The K8800 I don’t see anyplace to hack I mean there’s not a lot to do to it.
1 Like
There’s a lot to do…
- Realign the steppers, as they are not properly aligned, leading to a belt missalignement
- Belt tensionner for uniform belt tensions
- Fix filament detection problems on some printers (other have been whining about it, the guide says: disconnect the sensor…)
- Guide for the filament spool if you keep it on top. If not, the spool emptying, ther filament is scratching on the top plate. Ok with normal PLA, brakes wood PLA in some cases (a good start: A Filament Return pulley for Vertex Delta)
- Move screen to top (optional, depends how/where you place your printers)
- Belt guides for upper bearings
I think I forget some, should write them down
1 Like
I agree about the filament detection but I checked my filament and it is the filament not the printer. moving the screen… have no problem with it being on the bottom however it would be nice if it was on the top but I can live with that. I will probably end up running it on a PI with Octoprint like I do with my other 2. Filament guide once you get it done please share it once you are done.
1 Like
Have you seen my post about it? There’s accablant images of cold solder… No Velleman reaction…
Look at this:
This is flat… There’s no update, ever, on any firmware…
First, I personally resent your statement about the community here and users hacking and improving. I refer you to one of my earliest posts here in the Delta forum, or any of the half-dozen modifications I documented in the K8200 section. I am only one of many customers who contribute to the discussion here.
Second, I am not disagreeing with the need for bug fixes for the Delta, nor am I arguing against doing so if you wish to. I have noticed one or two anomalies that I suspect may be Marlin bugs. But I am not just going to blindly apply new firmware versions, hoping that they will magically cure my woes.
None of the flaws you have listed in the Delta are firmware issues. If you are asking Velleman why they haven’t yet updated to a new Marlin, I am asking you what value, specifically, you expect the new Marlin to deliver?
Yeah, that’s one upgrade. You can look down on my feelings, but this is the way I feel it here
Magic has nothing to do when reading changelogs… I have given one simple exemple of something that needs to be fixed and that is present in Marlin 1.1.7. But as the screenshot I linked shows that there’s absolutely no life in the git repositories once they have pushed a blinded initial commit, I’m not waiting on an update either
Can you please explain what that revision actually does? It doesn’t appear to be very well documented.
I certainly understand what you are saying about the value of using git, but nobody here can help you unless you say what it is you are trying to do.
I am not asking for help anymore, it’s not our job to upgrade a firmware where we don’t even have the changelogs.
The git link seems pretty self explanatory? It adds software safeties so the printer won’t exceed axes limits.
See how concerned Velleman seems to be about this discussion? As concerned as they were when I asked for spare parts, as concerned as they are when, after not being able to get spare parts I asked for machining plans for the parts, because I’m not rich enough to own Inventor 2018. As concerned they were when discussing the print quality. This is what I’m pointing out.
So yeah, for now I’m signing off this forum and off Velleman too. Imm do my own way, without anything to do with this. The mecanical part is one thing, the rest is easily replaced. As for the machining plans I found an engineer office that accepted to turn all the Inventor files into machining plan in pdf, so I’m ok for spare parts now.
BTW, everything is documented…
Ok, now I do see what the sparse, one-line documentation says about this change.
How are you getting the Delta to navigate outside of its cylinder? This sounds like a slicing issue first and foremost? I am still trying to understand what actual problem this change would resolve?
Lol, ok, there’s absolutely no changes made be Velleman, but a few configuration, suport for LCD and that’s about it… Nothing to brag about… This is a comparison between Velleman’s 1.1.4 and Marlin’s 1.1.4 on my own git repository
EDIT
I got it to run outside of it’s radius by a firmware bug most likely, fixed by this commit I linked. I always make sure my pieces are no bigger than diameter 190 skirt included and centered.
Yes, that was kind of my point, originally. If you know enough about what you are doing to be installing beta firmware, diff-ing and applying the Velleman customizations is not difficult. That is the beauty of the Marlin firmware architecture.
EDIT: It doesn’t sound like you really know why or how you got your delta to go out-of-bounds? Can you share some g-code or something? How will you evaluate whether the patch fixes your problem?
There we go, complete changeset for those that want to know what is changed on Velleman’s firmware vs Marlin 1.1.4
Now updating to Marlin 1.1.9
@Dr_Vegetable BTW I’m not sure you are understanding my point. I’ll stop after this most prolly but:
- Activity is showing life and dedication in an open source project
- Having a 5 versions old firmware shows a non will to follow development.
- You keep asking me for specific bugs, I gave you one simple. What does it matter, I have the fix already?
- Marlin RELEASES, not beta as you keep saying. Their master branch is the alpha, users are building beta and devs push out RELEASES, such as 1.1.4 was and 1.1.9 currently is. 1.1.9 is tagged to be the last of 1.1.x. I’m asking for at least releases to be followed, because as you might have now read in the releases history, many new features were implemented and many bugs squashed, such as better coasting, you know, those pesky bubbles on the walls of your prints?
So for me that’s it, I have started to build my own firmware, will publish the repo link here for people that want the improvements. About the rest, well, as said the Vertex Delta is great, the support is lower than 0
Dear Psycho,
It was only about a week ago that you posted a glowing review of how great your first two months were with this printer, and how awesome the output quality is. Suddenly you’re in here ranting about how Velleman owe you constant software updates for an open source package?
You haven’t made a clear case for why this bug fix is so urgent to you, or should be to anyone else. I have not seen this behavior in my printer, I haven’t seen other people complain about it, and you yourself haven’t explained what problem you are experiencing. If you expect a vibrant developer community here, and you expect the company to share your urgency, you need to tell us what the actual problem is.
You made an oblique reference to having your printer somehow go out of bounds, but I haven’t seen you describe what you were doing or what you were printing at the time. You haven’t given the folks at Velleman, (or any of the community members here) any way to reproduce your issue, and you don’t seem to have a plan to determine whether updating your firmware actually addresses any issue.
I question your methodology. If you don’t know how you made it happen, you cannot evaluate whether the new firmware fixes it!
If you have a real-world scenario where this bug could affect all of us, I would appreciate if you would actually share those details with the community. And if you don’t have that, then admit that you are simply grasping at straws, applying patches because the description fits a symptom you think you might have seen.
Velleman have delivered a more than functional product. As a company, they need to balance your desire for cutting-edge features against the basic goal of providing a stable product. Unless there is a compelling reason for them to promote a new firmware update, it only creates extra work and confusion for all of their customers. You haven’t made a case for why this patch is necessary.
So good luck with your printer. I hope you will continue to contribute to this community and share your experiences. I am sure you will learn a lot, now that you have started looking at the code.
There’s a difference between “constant” and 9 month…
Unless there is some compelling reason to update firmware, it could be ten years old.
“If it ain’t broke, don’t fix it.” - Ancient Proverb.
1 Like
If you look at Marlin’s updates, quite many features are/were broken. You have your theory, I have mine. Fine
Re the article about the printer, it’s true, the mechanical part of it is brilliant, and with a little fiddling everything is just great, this, with the fact that Velleman doesn’t want to sell spare parts to Switzerland, made me buy a second one.
The problem imo is in the rest. You check life by looking for a heartbeat.
I agree with the Doctor.
I have not had any of the issues you are talking about.
As far as constant firmware updates look at your car how often does the MFG put out updates for the the firmware there. Personally I think the K8800 is an excellent machine.
Spare parts you should talk to the dealer that you purchased the printer from.
Velleman can not make them buy these parts that is up to the distributor.
1 Like
A car and a printer is not exactly the same… I don’t care, I have updated the firmware already to latest Marlin
As for the spare parts, you know that they have an online shop, don’t you?