How do I create a new printer configuration?
Hello. I want to create my own configuration in RatOS for my printer, which is not supported by the system as standard. Is there an instruction or short instructions for this? At the moment, the main problem is a misunderstanding of the overall picture of the dependence of some files on others (many parameters are specified several times in different files). When trying to create a completely new printer and specifying "template": "vostok-printer.template.cfg" in printer-definition.The error "Cannot find module'./vostok appears on the site in the Configuration Files section.ts'" at the same time, a file with this name is in the /pi/ratos-configurator/templates folder.
12 Replies
Are you trying to make a configuration, or just get your printer working?
Now I have a printer running on a clean klipper. I want to switch to RatOS because I see advantages there. Therefore, I want to add another type of printer to the system. Now I have taken the voron 2.4 files as a basis and am turning them into the option I need. if you do not create a new file in templates, but use the existing one, it does not give an error. Now another y-axis motor is missing for testing. Printer configuration: kinematics: cartesian, drives: x, y, y1, z, z1 (in the future, when I figure out this configuration, I plan to finish the IDEX version and with 4 motors on the z axis)
Now it has started to show 2 engines on the y axis. therefore, the main question is how to use your template files": "voron-v24-printer.template.cfg" now I have edited an existing file to avoid an error.
Now I tried to change the contents of the /home/pi/ratos-configurator/templates/voron-v24.ts file, but it didn't lead to anything. Also, after deleting this file, no error appeared, from this I make the assumption that the file I need with the same name and content is not used directly from this folder. probably, adding your own file to this folder did not lead to a positive result.
For this to work you'd have to check out the non deployment branch of the configurator, ie v2.1.x for the current production code. Keep in mind that code lives in src/ rather than in the root, and you'd have to delete the node_modules dir in the root and run
pnpm install in the src/ directory.
furthermore you want to do sudo systemctl stop ratos-configurator and manually run it with pnpm dev
Now you can modify the code in src/
The code you're looking at is compiled code. You don't want to modify that 🙂Let's save it for history) An approximate procedure:
cd ratos-configurator
git checkout v2.1.x
git branch -a* (* indicates the current branch)*
git pull
cd src
npm install
pnpm dev -- --host 0.0.0.0
replace line in env
RATOS_SCRIPT_DIR=/home/pi/ratos-configurator/src/scripts
Main files for editing:
ratos-configurator/src/templates/printer.ts
printer_data/config/RatOS/printers/printer-definition.schema.json
There is an error ERROR (6552): Couldn't find printer settings file: /home/pi/printer_data/ratos/last-printer-settings.json
It shows that the configuration has not been saved before (you can ignore it)
Now, when I try to create a configuration with IDEX, I encounter this error
at the same time, at some point it started working, but then it stopped again (
the same thing happened with the microstep, at some point I got 128, but then it started showing 64 again and ignoring the settings in json
it looks like this happens when deleting the "toolboard": "btt-ebb42-12", but I have a printer without a board in my head)
it seems that there is a problem that makes it almost impossible to change the head parameters other than those existing for official idex printers
We currently don't support toolboardless IDEX.
You can change all hardware including the toolboard. But toolboards are currently required.
Are you planning to add a clear selection button for T1? Are there any approximate dates?
Not planned at the moment no. Again because we don't support a second toolhead without a toolboard we don't have the wiring diagrams or the pin alias standards.
It's a whole lot of effort for something i consider a niche usecase at this point.