cgfighter 0 Posted February 6 in Issue with cura 3.2 and monoprice select mini v2 I installed cura 3.2 twice and every time I try to select my printer "monoprice select mini v2" it opens for a sec then closes the program. Any idea what could be happening? I am using windows 10 with the most recent updates if that helps Share this post Link to post Share on other sites
i_rupar 1 Posted February 6 in Issue with cura 3.2 and monoprice select mini v2 I noticed when I upgraded Cura today that anytime I tried to any the monoprice mini select, it would crash immediately. After digging around it looks like the problem is in the malyan_m200.def.json file. It is used for providing definiations for the MP mini select. To fix the problem edit \Ultimaker Cura 3.2\resources\definitions\malyan_m200.def.json About 2/3rds of the way down there is a line "material_diameter": { "value": 1.75 }, Change it to "material_diameter": { "default_value": 1.75 }, save and all should be good. Hope this helps 1 Share this post Link to post Share on other sites
BrightBerry 0 Posted February 6 in Issue with cura 3.2 and monoprice select mini v2 I have the same problem, also posted it in the other topic: Share this post Link to post Share on other sites
BrightBerry 0 Posted February 6 in Issue with cura 3.2 and monoprice select mini v2 8 minutes ago, i_rupar said: I noticed when I upgraded Cura today that anytime I tried to any the monoprice mini select, it would crash immediately. After digging around it looks like the problem is in the malyan_m200.def.json file. It is used for providing definiations for the MP mini select. To fix the problem edit \Ultimaker Cura 3.2\resources\definitions\malyan_m200.def.json About 2/3rds of the way down there is a line "material_diameter": { "value": 1.75 }, Change it to "material_diameter": { "default_value": 1.75 }, save and all should be good. Hope this helps That was the trick, thanks! Share this post Link to post Share on other sites
BrightBerry 0 Posted February 6 in Issue with cura 3.2 and monoprice select mini v2 Maybe the topic should be changed to "Issue with Cura 3.2 and Monoprice Select Mini (V2) / Malyan M200" Share this post Link to post Share on other sites
i_rupar 1 Posted February 6 in Issue with cura 3.2 and monoprice select mini v2 Good idea. I don't know if the OP can edit the title or if it might require a mod to do it. Share this post Link to post Share on other sites
cgfighter 0 Posted February 6 in Issue with cura 3.2 and monoprice select mini v2 It did thank you very much! I would have never figured that out on my own. If the moderators want to they can go right ahead do that. Share this post Link to post Share on other sites
Ldonyo 1 Posted February 8 in Issue with cura 3.2 and monoprice select mini v2 On 2/6/2018 at 3:34 PM, cgfighter said: I installed cura 3.2 twice and every time I try to select my printer "monoprice select mini v2" it opens for a sec then closes the program. Any idea what could be happening? I am using windows 10 with the most recent updates if that helps I get exactly the same behavior and I have the same printer. Also running fully updated Windows 10 64-bit. Share this post Link to post Share on other sites
GOONfpv 0 Posted February 10 in Issue with cura 3.2 and monoprice select mini v2 (edited) What should I be using to edit the file. I tried note pad, but could not save it as a JSON file. It's also saying I do not have access to the file, add access from administrator. Anyone know how to get by this issue? Thanks for the help. Edited February 10 by GOONfpv Share this post Link to post Share on other sites
Ldonyo 1 Posted February 10 in Issue with cura 3.2 and monoprice select mini v2 I used Word Pad to do the editing. If you open Word Pad as Administrator, you should be good. You should be able to right-click on the Word Pad exe file and select Run as Administrator from the menu that pops up. 1 Share this post Link to post Share on other sites
Ldonyo 1 Posted February 10 in Issue with cura 3.2 and monoprice select mini v2 On 2/7/2018 at 6:04 PM, Ldonyo said: I get exactly the same behavior and I have the same printer. Also running fully updated Windows 10 64-bit. That edit worked for me, as well. Share this post Link to post Share on other sites
