Welcome to the SeeMeCNC Community

It seems like some have move on to Repetier 0.92, in order to move to different thermistors.
I got a DyzEND hot end that I am trying to integrate to my Rostock MAX v2.
It looks like a nice solid design, can go up to 500C and have a good selection of stainless steel nozzles to choose from.

Not having complete success with the integration to the SeeMeCNC custom 0.91 firmware.
Seems like the thermistor table is quite off. Starts off at 86C at room temp.
I guess I need a valid thermometer to validate if the temperature is good above 86C.

Anyone has a ported the custom SeeMeCNC 0.91 firmware to 0.92 and care to share?
Any other suggestions?

Here is a link to that neat hot end:
http://shop.dyzedesign.com/dyzend

Thanks ahead!
LD in balmy Montréal

You don't need to upgrade to .92 neccesarily, you can add their thermistor table to the firmware as a user defined table, and use it that way. (Table here: http://dyzedesign.com/support/dyzend-te ... /#repetier) That being said, I do believe that if you search for it, Gchristopher uploaded a version of .92 for the max in his dual extrusion thread. (two actually, one set for dual extrusion and one set for normal use), but I don't have a link to it off the top of my head, and am a little busy to find it.

I followed their instructions (but on 0.91) and I am getting 86C at room temp.
Too much error, I think, even when considering a coverage curve shifted to support up to 500C.
A 10C error at room might be explained by the poor precision at that low temperature for a thermistor optimized for a 200-500C range.
Following my first effort, they improved the instructions on porting this new hot end to Repetier.

OK, Xenocrates, I found the post you were pointing at: https://github.com/gchristopher/3dprint ... 0Bluetooth
For a single non-stock extruder and Bluetooth. Should be a good starting point for me.
Thanks Xenocrates.

That is a neat looking hotend, could you let us know how well it works?

You can try my configuration if you want. I'm running 0.92.6 I believe.
You will probably want to tweak it to your printer though, as I changed the thermistors setting to reflect my thermocouple measurements at temperature.

I have 0.92 running 100%... Here's my firmware... Keep in mind, my machine is extremely modified - so you'll need to make a few changes in config.h... But it will work.

Jrjones wrote:You can try my configuration if you want. I'm running 0.92.6 I believe.
You will probably want to tweak it to your printer though, as I changed the thermistors setting to reflect my thermocouple measurements at temperature.

If his FW is 0.91, and yours is 0.92 and you only give him config.h - the code will never compile... You need the actual firmware .cpp files, not one header file.

JJPowelly wrote: If his FW is 0.91, and yours is 0.92 and you only give him config.h - the code will never compile... You need the actual firmware .cpp files, not one header file.

Or he can upload the config.h to the firmware tool and use that as a starting point, which is what I would do so that he can see what is different on his machine compared to someone else's machine.

Firmware tool on repetier site is very beta-esque... It's hard to get the code to compile in 0.92 after using it...

I just found this thread while searching for Dyzend.

It's been a while, but I hope at least some of yall are still active.

I've been having a lot of trouble setting up my new dyzEnd and I was wondering if anyone has a configuration that is up and running.

Please let me know ASAP, I'm getting sick of uploading configurations one after another only to find out there is something else wrong with them.

Just noticed this discussion, way too late. Thought I'd add more links. getting dual extrusion working in 92.X really only had two parts:

- finding a valid 92.X configuration.h file to start with. I think I started with Nylocke's configuration.h file. Then it's checking that everything matches your machine mods vs theirs.
- For 92.4, there were problems with pins.h for a second extruder. I found the fixes in posts by jfettig and Polygonhell