Separate names with a comma.
Some features disabled for guests. Register Today.
See docs:blackbox:faq-emi [OpenBuilds Documentation]
Checking wiring is good. Now on to EMI then?
Does look like EMI: Good call: docs:blackbox-x32:faq-emi [OpenBuilds Documentation]
Most likely EMI from the VFD. See docs:blackbox:faq-emi [OpenBuilds Documentation] Not software related
If you have EMI issues it would show up during some test cuts too - random stalls, usb corruption, false hard limits alarms etc - see the symptoms...
All symptoms of Serial Corruption. Typically caused by EMI: docs:blackbox-x32:faq-emi [OpenBuilds Documentation]
Thanks!
Looks like the USB port shutdown from EMI (per the log): See docs:blackbox:faq-emi [OpenBuilds Documentation]
Looks good then (: Dust extraction is a known EMI source: See docs:blackbox:faq-emi [OpenBuilds Documentation]
...file Errors 2 and 25 indicate malformed gcode, but could also be EMI. Is the Interface's data cable router clear of any AC, Stepper motor...
Refer to docs:blackbox:faq-emi [OpenBuilds Documentation]
Peter. Can emi cause this? It seems to perfect to be emi, but ....
docs:blackbox-x32:faq-emi [OpenBuilds Documentation] EMI symptoms in log shows as example in 1.1 Corrupted Serial data / streaming errors
Sounds like EMI, checkout docs:blackbox-x32:faq-emi [OpenBuilds Documentation] - any 3rd party components like a VFD spindle in use? Dust extraction?
Spindle EMI: see docs:blackbox-x32:faq-emi [OpenBuilds Documentation]
yes =emi"]docs:blackbox-x32:faq-emi [OpenBuilds Documentation] docs:blackbox-x32:faq-usb-connection-failed [OpenBuilds Documentation]
See the above
Sounds like EMI: See docs:blackbox-x32:faq-emi [OpenBuilds Documentation]