28.02.2013 Views

LTV 1200 Operator's Manual - CareFusion Emergency Preparedness

LTV 1200 Operator's Manual - CareFusion Emergency Preparedness

LTV 1200 Operator's Manual - CareFusion Emergency Preparedness

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Symptoms Possible Causes What to Do<br />

Ventilator gets<br />

excessively hot.<br />

Ventilator does not<br />

work with LTM<br />

Graphics Monitor.<br />

Patient circuit leaks.<br />

ventilator must run<br />

harder to maintain<br />

PEEP.<br />

Internal problem with<br />

the ventilator.<br />

Communications<br />

setting is not set to<br />

MONITOR mode.<br />

Ventilator requires<br />

upgrades to be<br />

compatible with LTM<br />

Graphics Monitor.<br />

Defective connections<br />

between the LTM<br />

Graphics Monitor and<br />

the ventilator.<br />

Perform a Leak Test and reseat or replace the<br />

leaking parts or connections. See page 11-8 for<br />

instructions.<br />

Immediately contact a certified Pulmonetic<br />

Systems’ service technician.<br />

Set communications setting to MONITOR mode.<br />

See page 10-16 for instructions.<br />

Check LTM compatibility in the Model Number<br />

menu. See page 10-19 for instructions.<br />

If the ventilator is not LTM compatible, it will<br />

require upgrading by a certified Pulmonetic<br />

Systems’ service technician to accommodate the<br />

LTM Graphics Monitor.<br />

Check the Communications Data Cable<br />

connection between the ventilator’s<br />

communications port and the LTM Graphics<br />

Monitor’s Data Port. See the LTM Graphics<br />

Monitor Operator’s <strong>Manual</strong>, P/N 11010, for<br />

detailed instructions.<br />

Page 15-14 <strong>LTV</strong> ® <strong>1200</strong> Ventilator Operator’s <strong>Manual</strong><br />

p/n 18247-001, Rev. G

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!