Not able to print with IDEX
I'm getting this error when trying to print: Error evaluating 'gcode_macro START_PRINT:gcode': gcode.CommandError: Something went wrong! Missing important post processor start print parameter!
I've added RatoS debug, my printer.cfg and ratos.cfg and the gcode I'm trying to print
118 Replies
please show me the machine tab screen
where i can see the software versions
om on a tablet and cat unzip the files, can you uploadthe gocde as agcode file please
please SSH into the pi and run
sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh
then shpw me the complete console outputLast login: Tue Sep 24 09:49:45 2024 from 192.168.50.101
pi@ratrig:~ $ sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh
Updating RatOS device symlinks..
###### Updating whitelisted commands
###### Updating service permissions
###### Installing beacon module...
beacon: beacon already installed, skipping...
###### Installing git hooks
Node 18 already installed
###### Registering klippy extension 'z_offset_probe_extension' with the RatOS Co nfigurator...
Success!
✓ Successfully registered extension "z_offset_probe_extension"
###### Registering klippy extension 'ratos_extension' with the RatOS Configurator...
Success!
✓ Successfully registered extension "ratos_extension"
###### Registering klippy extension 'resonance_generator_extension' with the RatOS Configurator...
Success!
✓ Successfully registered extension "resonance_generator_extension"
Success!
✓ Successfully registered kinematics extension "ratos_hybrid_corexy"
###### Symlinking klippy extensions
Success!
✓ Symlink for "beacon.py" already exists. Skipping.
✓ Symlink for "gcode_shell_command.py" already exists. Skipping.
✓ Symlink for "ratos_homing.py" already exists. Skipping.
✓ Symlink for "z_offset_probe.py" already exists. Skipping.
✓ Symlink for "ratos.py" already exists. Skipping.
✓ Symlink for "resonance_generator.py" already exists. Skipping.
✓ Symlink for "ratos_hybrid_corexy.py" already exists. Skipping.
✓ Symlink for "linear_movement_vibrations.py" already exists. Skipping.
✓ Symlink for "timelapse.py" already exists. Skipping.
###### Updating beacon firmware...
Beacon '604E4B825154364134202020FF150B0E' is already flashed with the current firmware version '2.1.0'. Skipping.
To force update, re-run
update_firmware.py with the --force flag set.
###### Restarting configurator...now try to start a print, but this time name the file like this
then share the mainsail console output
just print a cube
That's why it doesn't work 🙂
Not sure why you added that, but that effectively disables the post processing
And thus you're unable to print anything @dyocis @Helge Keck
found the issue
ahh, mikl as well
lol
Ahh, I added that to my hybrid setup. It was for something in the discord. I don't remember why anymore.
this was a temporary fix bc we had some issues some days ago
Yep, I didn't even think about it
luckily we have hawkeye mikl
It's running the test.gcode now!
Ugh, lost communication with toolboard. This had been an issue since before IDEX. the LDO orbitool board is giving me all kinds of trouble
please show me your toolboard strain relief
It's probably the O2 safety features, i noticed some problems specifically on IDEX in the way the custom sections are generated for T1.
gimme a sec i'm gonna post a potential fix
solid
@dyocis try this
oh and
Gah the run leds should have
value: 1 not 0
So in total:
not a friend of this config tbh
O2_RUN_LED
this should start with a _Yeah there's multiple things that need fixing here
otherwise one can kill its baord by accidentaly move the slider in the UI
much of it is copied from bob's config examples
Ok, I'll give that a try
AFAIK it's just for the LED
It doesn't actually enable/disable anything
wait, the output pin on my bnards is the power control
,aybe there are more now
there are multiple output pins 😂
Yea, I had it turned off in my original config too
robert needs always a extra sausage
:kekw:
Oh yes. They're all super cool features but it's so much extra stuff that no other board needs atm, so there's quite a number of shenanigans to be implemented to properly handle it.
I put in an issue on his git a few days ago about the constant lost comms, but haven't heard anything back yet
tbf i would suspect RatOS first on this one
Because the board is so complicated
thats not good, its wrnog imo
[heater_fan toolhead_cooling_fan_t1]
# Use max_power: 0.5 for 12V, max_power: 1 for 24V (in printer.cfg)
max_power: 0.995
cycle_time: 0.0001Many little quirks such as the max power stuff to avoid tripping the safety features etc.
Didn't make it very far...lol
the power should be controlled like this according to robert
[output_pin part_fan_power]
pwm: True
hardware_pwm: False
cycle_time: 0.0001
value: 0.3 # 12VI've got a 24v fan
plus, you should even check with a multimeter the output since they can differ slightly
Hardware pwm sucks balls
This is not the same board btw
This is for the unreleased one
ok ok
😂
im quiet
:kekw:
ups
So add the pwm stuff, or no?
No, just the stuff i posted
this: https://discord.com/channels/582187371529764864/1294314941989257217/1294321047818211429
rule #1, always do what mikl says
Ok, after I added your stuff I got the lost comm on T1 above
And @dyocis make sure you put it in printer.cfg far enough down so your other custom stuff doesn't end up overwriting it
you have a lot of stuff going on
lemme double check
where did you add it?
I just moved it to right above the steppers
Side note btw:
- do not manually add
nozzle_diameter to printer.cfg, set it in the hardware configurator, that's where VAOC gets the value from, and it's emitted to RatOS.cfg so there's no need for this.
Okay that should've worked. I noticed you put value:0 for your run_led which doesn't make much sense to me.I'll remove it
It just turns it off at boot
It would be turned off at all times unless you manually enable it
an only for T1, as you're using the same name, so there's effictively only one section, last one taking precedence.
I moved some of this stuff over from my hybrid config.
Try setting them the value to 0 again in the two section from the config i posted
loss comm on T1 again
with:
?
Just made that change. Trying again
Before IDEX I would only get this error on longer prints...3-4 hours. Now it's doing it every time. just got loss comm on T0
i'm assuming it's the safety features tripping
wait, have you connected the 4028's to the toolboard?
Yes, 24v 2 wire 4028s
Oh so those low performance ones
prolly not that then.. they shouldn't pull enough amps to trigger anything.
I mean, they have similar specs to the stock 2048s, they are server fans.
Do you have a link?
hold on, I'll find it
Never seen any 24V 2-wire ones with that performance, it's not really possibly with voltage control because of the RPM's.
That one has a significantly beefier dc/dc converted made for such fans
also, that's not supposed to be public information just yet 😂
yeah they have less than 1/4th the pressure
and 2/3 the airflow
Not even close
I tried a few different ones. but that one worked the best.
They won't trigger anything, they only pull 0.15A
Hmm, I can put the stock fans on, if you think that'll help. When I was trying to figure this out on hybrid, I disconnected the fans completely and still got comm shutdowns
Nono, you'd have to wire those very differently as those WILL trigger the toolboard safety features
The part fans shouldn't come on till the 3rd layer anyway
It's like 4 of the ones you currently have in one
I only really print with ASA, so I wasn't too worried about cooling
The ones you have, yeah. 4-pin 4028's will run full bore until there's a PWM signal
So instant safety trip
anyways
that's not it
I'm not sure what makes it shit itself
I mean for the comm error, the fans wouldn't trigger a safety before it even finishes the homing cycle
Post klippy.log maybe there's something interesting in there
4-pin 4028's would trigger as soon as the board is booted and power is applied
that's why i was going down that road
but you're not using those
it's complaining about T0 now
not t1
Yea, I started looking into the stock fans, but I wasn't confident on how to wire them
Yea, it goes back and forth between the two
where have you connected the small power adapters for the boards? to the psu or to the mcu?
To the PSU. THey're getting 24.2V during printing
ok
Can't find anything suspicious in the log
I gotta go.. It's odd, i have one running on my minion with no issues.
I was going to put in the stock toolboards and fans when I did IDEX because of this issue, but I found the ground wire of the tool fan had a bad crimp, so I convinced myself that was the issue....lol
Thanks @miklschmidt I appreciate your help
i mean if anything is miswired or shorting or have a loose connection etc, that will result in the same error as you're getting now
Sure thing, will look into it more and fix the t1 generation later tonight (prolly after midnight)
midnight GMT+2 that is 😄
6 hours from now
I checked all the crimps and tested everything I could, and it all checked out. If it was only doing it on one toolhead, I'd rip it apart, but it's doing it on both, so that tells me its either software, or bad batch of boards?
I bought 3, so I have a spare set that I've been switching in and out while I was testing on hybrid, but nothing really ever came of it. Same issue no matter what hardware was installed
Little update, I moved the usbs to the waveshare hub and off of my other hub, that was plugged into the waveshare. I was able to make it through a 5 min print. On hybrid, when I moved from the waveshare to the other hub, this issue was greatly reduced, so now it's doing the opposite.
put the baords directly into the PI usb connectors
not into a hub
use the HUB for accesiores and not the MCUs
so that tells me its either software,Yeah i'm thinking this is likely.. Going over the official configs now It should be fine on the waveshare hub as long as it's connected to one of the USB 3.0 on the pi, but yeah, hooking those straight to the USB 2.0 ports on the Pi won't hurt.
I've got my SSD, Beacon and the MCU in the Pi ports. The toolheads are on the waveshare
SSD is suckng a lot of juice
i had similar issues onmy IDEX 3.1
well, dont. know if it wasa power problem orsomething. else, but had issues with a USB SSD nad multiple MCUs
I've got a 5v 75w PSU wired in
Alright @dyocis so everything is identical to the stock config except for these, paste those in. I'm highly skeptical that they'll change anything, but worth a shot.
I'm in a meeting ATM. I'll be free in about an hour and will do this. Thanks for continuing to work on this with me
I would keep all MCU's on the same device tree, so put beacon and mcu on the waveshare hub together with the toolboards.
SSD in the second USB 3.0 port on the pi and then put VAOC on the USB 2.0 port on the pi.
Sure thing
It doesn't like the pwm setting
Solution
Here's how I setup the USBs
Don't judge my cable management. I'm not done yet!
Where did you change the sdcard_print_file macro and what did you change it too?
It was in my printer.cfg, I just removed it
Weird I don’t have it there and got the same error you got
Is everything up to date?
I think so
I added that a few days ago to address an issue that has since been fixed
Everything in the update manager is updated
I'd open another post. We're T/Sing a different issue all together now. Helge and Mikl will jump in there to help
When they can....they are super busy
👍
the fuck
Ah sorry it's only for output_pins and extruder, it's just
cycle_time on fans.. because consistency 👍
you need to remove itI'll throw it in there after this print finishes. Hasn't errored once since I switched the USBs and put in that code, so maybe it's fixed? It was only doing it occasionally with hybrid after a few hours, so I'll potentially waste some filament later tonight and see if it makes it through
It's not unlikely that it's just a matter of putting the right devices on the right ports.
mixing several different usb standards is always fun on Pi's.
I can't its in a only read file
So an official ratos file, nothing for you to do (it's supposed to be there), you only need to remove it if you added an override yourself to printer.cfg. If you're continuing to have problems please open a new thread and post the error message and a debug zip and i'll come take a look.
ok
how do i get the debug zip
nevermind found
it
I'm going to close this post, as the original issue has been fixed. If I have anymore loss of comm issues with the toolboard, I'll open a new post. Thanks for the help @miklschmidt and @Helge Keck