r0dnay

ah ok, didnt realise you meant OS environment variable, thanks for clarifying its ok, i hashed out what i added when it didnt work and it can see the printer, ill change the variable in windows and see how it goes, thanks

would it be CURA_DEVICENAMES or CURA_DEVICEINFOS for the com port location? i found this part in the code 1 # set CURA_DEVICENAMES=USB[1-9] -> e.g. not matching /dev/ttyUSB0 2 pattern = environ.get('CURA_DEVICENAMES') 3 if pattern and not search(pattern, port[0]): set CURA_DEVICENAMES=COM7<<<<<<<<added this line here but cura cant see the printer and wont make 'Print to USB' button available, so tried COM7\: which didnt work either is my syntax or location of code incorrect? 4 continue 5 6 # set CURA_DEVICETYPES=CP2102 -> match a type of serial converter 7 pattern = environ.get('CURA_DEVICETYPES') 8 if pattern and not search(pattern, port[1]): 9 continue 10 11 # set CURA_DEVICEINFOS=LOCATION=2-1.4 -> match a physical port 12 # set CURA_DEVICEINFOS=VID:PID=10C4:EA60 -> match a vendor:product 13 pattern = environ.get('CURA_DEVICEINFOS') 14 set CURA_DEVICEINFOS=LOCATION=COM7 <<<<<<<<<<<<<<<<<<<i added to this line also both ways, but that didnt work either 15 if pattern and not search(pattern, port[2]): 16 continue

which python files handle the hardware/com port side of things? is there a particular reason/s why cura cant handle com ports well? what are the limitations cura faces? or is it human limitation? just trying to ascertain the best way to tackle this thanks again

thanks for that, noted. is there any way i can turn off com port sniffing/locking up, so cura only looks for the com port its holding on to? that way i can at least use another app for a different printer?

in the meantime if anyone else can point me in the right direction or knows python (im not a coder at all, but i can work some basic things out to a degree) well enough to scan through the files etc, itd be much appreciated. im sure plenty of cura/slicer users would love being able to use specific printers by opening seperate instances of the software, would be great to get a workaround

i found the file, it doesnt define a path to a file to reference machine_instance, thanks anyway, ill have a dig around and see if i can find where the software calls on machine_instances

i got the feeling help with what i need to do wouldnt be forthcoming and mentioning it might not cultivate an answer at all, but being as you asked, i am using creality's version of cura, i have 2 printers, ive learned that this software has issues with mixing comports/printer profiles etc what i thought id do is install two instances of the slicer, but regardless of where i install, the software will always only reference some kind of configuration from a central location, so every instance of the software would all reference the same files for printer configs etc to work around this, i thought i would change the code in one of the installations so that it references those 'config' files from another directory - thus each software will in theory (havnt done it yet to confirm) should automatically connect to the relevant printer, the only one set up on that particular installation. i figured that there must be a file somewhere that points to a path where the 'config' file is located, i though once i find it, i could edit the path and set up a printer solely on that installation. not sure if that makes any sense thanks for the name of the resources file name, but i was wondering where the file was put by the cura installation locally on my machine

ok thanks, would you be able to paste the path for the resources class file for ultimaker's cura? would be much appreciated

ok great, ill do that in the meantime, any idea whats the path for the code which checks machine configurations for the ultimaker cura software?

hi i wondered if anyone could tell me which file contains the code which points cura to machine_instances with the following path C:\Users\USERNAME\AppData\Roaming\Creality Slicer\4.8\machine_instances thanks