I’m an Englishman with no Nigerian relatives, I was just making a stupid point. I love the work done in this thread, it is super interesting and way above my IT/coding skills. Thanks go to all the contributers no matter what language you choose. But I have managed to root my V3KE and put Guppy UI on it, the sonic pad is harder to crack, I want to use 2 cameras but it isn’t playing ball.
AFAIK (from what little I know) there is not one Indigenous Australian language (I’m assuming due to it’s large size & still sparse population). So that may be a challenge …
I hope everyone knows they can type in whatever language they are most familiar & comfortable with - most of us will go to any length to understand and help.
Of course, if you speak one of my languages it will be quicker. But then that’s just me. There are smarter and more multilingual people here already!
Oh she still works, I’m a part time geek not a professional one or a fulltime geek with lacking knowledge. Great minds think alike but idiots rarely differ.
Hey fellow SE owners. I’ve switched over to an external monitor recently, and figured I’d mention that Octoprint/Octodash is now capable of sending messages to my printer LCD while printing using Octodash via M873 commands as well. Sadly, this addition has made the use of Iroh’s plugin unsupported, and the M873 commands being sent by the Octodash dependencies via either the printer notifcations, printer dialogues, or Octoprint Display ETA plugins. None of these functioned before updating to Iroh’s firmware, and werent used after installiing Iroh’s plugin and using G commands rather than the M873 command. So I’m not sure if the firmware itself would allow for the use of these plugins or if its something that Octodash is helping to achieve in conjunction with Iroh’s firmware. I assume that if they worked with the firmware alone Iroh wouldnt have had to bother with his plugin, BUT, at the same time, Iroh’s plugin is honestly incredibly well written. Muuuuch better than other options I just mentioned as far as GUI. Iroh’s plugin takes full advantage of the screen and all its abilities, both keeping the abilities of the original and adding more. The other plugins now just display very basic information, and in a very Spartan kind of way. Theres no extra capabilities, and the orignal tuning capabilities of the LCD are lost completely. I may just remove it at this point as its just giving me like [### ]30% type messages, or if I have all three plugins running in conjunction, it’ll give me “Good Accuracy!” messages and “L=4/190” type messages. All of which can be seen in a much more pleasing manner on the new Octodash LCD I’ve built using a cheap DSI 5 inch screen and my Rpi4 running the Octopi image. So yeah, I figured Id mention that since I’m pretty sure the only thing making it possible are the changes made within Iroh’s firmware updates, as I’m certain these didnt work in the past. Hence why I sought out Iroh’s firmware and plugin in the first place. And I dont think they would work if I were JUST running Octodash either if I were still running stock firmware. So the firmware is good for that too if anyone has considered going that direction. I upgraded for reason mentioned quite recently on the thread, like being able to view the thumbnail of what I was printing on the screen itself, etc. Plus, I want to turn it into a fallout terminal type thing or something. Thought that would be a fun project. Lol. I just thought it was a nice touch that the stock LCD now does something at least.
I will say, strangely Iroh’s plugin no longer appears under my installed and active plugins on octoprint. But I know its doing something, because when I connect to the printer it still gives me the “Octoprint Connected” message at the top with the little oldschool emoji octopus. lol. So I know the plugin is there somewhere doing something, likely facilitating the function of the other plugins. But I cant see it anymore or alter any settings, even searching via the octoprint dashboard to uninstall it is impossible. I figured Id test my theory at one point and see if the screen would still work if I turned Iroh’s plugin off and discovered it was nowhere to be found. Lol. Anyway, nice little possibly unintended success I figured you guys might be interested in.
The issues with degraded printing are not due to Marlin itself, and unfortunately, is due to updating the display from the @Iroh3d Octoprint plugin. With it turned off, it prints without any issues. I’m quite confident that @Iroh3d will fix the issue.
I had it disappear on me once when I installed an older version. After a few reboots and re-installs it showed up in the interface again. I just thought it was me since I was going back and forth between older and newer versions in testing.
So, yes M73 was enable to send updates too using my plugin. But the same way as M117 if another plugin send info through M117 or M73 they will overlap. You can use your prefered one by disabling one or another to avoid overlaping.
Chuck another shrimp on the barbie, new follower here. Excellent work thanks. One printer adapted to new firmware and Octo print, one left alone for comparing
Just a FYI, there is an ongoing issue that affects the quality of the prints specially in curved surfaces.
I have a drafted version to test if is going to solve the current issue but I will be available to test till next weekend so hopefully if I can fix it will be delivered in two weeks.
Sounds great. I tried doing a rewrite of the O9000.cpp (removing all the if…else if statements to something faster) to see if would make any differences, and it did a bit, but not enough. This then got me going down a rabbit hole, and hours latter (and late into the night!) I have a modified O9000.cpp and plugin that now needs testing on my printer to see if things work better (or are worse!). If it does I’ll share, if not, I’ll hide in shame…
Yes, I did indeed mean the M73 commands. I knew the M117 commands were enabled, but it was nice to see I could use M73 as well if I liked.
I just updated to your most recent release btw, very nice. I did notice that the baud rate was still set to the stock 125000 setting or whatever it is in the version I just downloaded though. Only reason I noticed was because I intended on changing it anyway. Im getting a lot of problems all the sudden with strange retractions while going around curves and I think I’ve tracked the problem to the LCD screen receiving messages during the print. I was trying to calibrate my first “fast” PLA filament when I added Octolapse to my plugins and suddenly I was immediately having problems I’d never had before. Even after your firmware upgrade, and then adding the new 5 inch LCD and Octodash, everything was fine. But for some odd reason the addition of Octolapse seemed to start a cascade of sorts. Id run one volumetric flow rate calibration print before adding it that did fine. Tried to print another one after adding Octolapse and everything went to hell. Hah. At first I blamed OCtolapse, then myself, as I was playing with retraction settings to dial the filament in and it only seemed to happen on retracts. As if the extruder gears just didnt know what to do for a second or something, so it would fight with itself and rattle a bit around every curve. I started looking into it and found the thing about increasing the baud rate and figured if I was going to change it I may as well update to the new firmware. Tried to print a simple file I had on the SD card in the printer and it seemed okay, but there were next to no curves in that model. I know it retracted just fine though. So yeah. I also just scrolled up a bit to skim the recent comments and catch up when I saw you mention a similar problem occurring with your plugin at times, and see you recommended the same thing. For some odd reason the your plugin still isnt showing up under my listed plugins, so I may try to unistall it via ssh and reinstall it, or possibly just go without since it wont work in conjunction with octodash apparently and the firmware itself is responsible for the enabling of M117 and M73. So yeah. I’m sure youre aware of how the baud is set, but just in case, I figured Id mention it seemed to be at defaults on this version of your firmware. About to try the print again now and cross my fingers. I’ll also need to order a better usb c cable i think. I’m just using one of the many I have lying around. But as I said, it was working perfectly before, so idk honestly. Still trying to troubleshoot currently, so I’m about to run another print and I’ll update you guys when I get it sorted. Any advice is welcome in any language you please. Lol.
Thanks again Iroh, youre a value to this community and you make my printer more fun. Considering its about the sole source of both my joy and sorrow as of late, the fact that youre improving the experience for us and helping to assuage my anguish in the process makes you my current favorite human. haha. Cant thank you and all the folks you forked off of enough, truly…
May all your prints be successful and you extruders never clog! lol.