Need help with configuration files. Modix 120x V2 6HC 3HC
-
We have a Modix 120x V2 that we replaced the main board in with a DUET 6HC & 3HC expansion board. We have everything wired up and used the RipRap config tool ,but can't get it to work the steppers don't move. It also has a Raspberry PI hooked up to it. Wiling to pay to get firmware written for our setup.
-
@ScuderiaJoe Did you notice this thread: "Modix3D Configuration and Macro files"? Follow the link to GitHub given by the OP @ComedianTF2. Of course, pin names for the 6HC are different, so you have to take that into account.
-
@infiniteloop just FYI, those configuration files and macros use deprecated code and don't really work. My company has a modix big 60 that I set up and I had to rewrite everything due to deprecated code and conflicting commands.
-
those configuration files and macros use deprecated code
I don't speak gCode fluently, but when I had a look at the config.g for the big60, it was clearly written for RRF 3.4, it uses conditionals, global variables etc. - no signs of deprecated code, instead: state of the art. Without a Modix printer at hand, I can't test its functionality, but basically, I assume the real obstacle lies in adapting the code to the specific hardware - in my understanding, the printers do not only differ in size but come in multiple configurations (e.g. print heads, hotends etc.). The effects you describe can easily originate from a mismatching firmware version on the Duet, too.
-
@infiniteloop yes, I realize that it is coded that way with conditionals and global variables. The fact of the matter is, when putting it on the machine and running it it kept throwing errors due to the conditionals and global variables. Going into the macros that are supplied, there is deprecated code that is used in the macros that does not make them function properly.
Trust me, this was probably the smallest issue we had with our machine. It was an absolute nightmare. I wasn't about to reverse engineer code written by God knows who, from a company that couldn't even crimp connectors properly which caused us to lose stepper drivers on the duet 2.
-
@Surgikill Having upgraded my printer from 2.0.3 to RRF 3.3 some time ago, I encountered similar troubles - in the end, I spelled each and every GCode with the help of the GCode dictionary. On the Modix, you had to even take a bigger leap. I wouldn’t blame Modix for that: their job is to deliver a printer that works out of the box. Migrating customers to an entirely new RRF is beyond their abilities - which you’ve proved by painful experience. Either you need an expert on location, or you have to educate yourself to grow your expertise.
Given the limited capabilities of RRF 2.x to automate updates, you had no choice than to become an expert yourself. Which, in my eyes, is a good thing: now you not only call a large format printer your own, you finally can master it in all relevant aspects (which is a completely different quality of ownership).
Oh, talking of crimps: being almost daily on this forum, I got the impression that a major percentage of the threads - regardless of the initial request - ended with an "Oops, I found the bad crimp".
-
@Surgikill That's quite interesting, I've been working hard to re-write the entire code of the printers, and I am pretty sure I caught all of the depreciated code. But if you point me to anything that was missed, I would love to fix it.
-
@ComedianTF2 bltouch deploy macro is deprecated
@infiniteloop yes, a printer that should work out of the box. That means a printer that doesn't need every single crimp re-terminated, and causes you to burn out stepper drivers due to bad connections. I do consider myself an expert, seeing as my personal machines at home are more complex than the modix machines, and they have all been designed, programmed, and assembled by myself. Should I also touch on the assembly instructions being completely inconsistent, and sometimes nonexistent? If I buy a v3 printer with upgrades, I shouldn't need to go to the v2, v3, and v4 assembly guides to get the correct information. I should actually receive my hotend, with all the complete materials needed to assemble it, instead of it missing the heater block, thermistor, heater cartridge, etc. This is not what you expect out of a printer that works "out of the box".
-
@Surgikill Good catch, I had overlooked the I1 parameter, though that shouldn't give any problems; the parameter is ignored. The rest of the deployprobe.g and retractprobe.g are correct though, and that should not give an error.