null Skip to main content

Roland VersaObject MO-180 Direct to Object UV Flatbed Printer

Was: $39,495.00
Now: $27,995.00
Financing Options:

Click here for product brochure: MO-180 Datasheet

Delivery zones: IL, IN, IA, WI 

This item will ship via LTL Freight 

Take your business to new heights with the VersaOBJECT MO-180. Incredibly advanced yet easy to use, this state-of-the-art UV flatbed enables you to grow your business and enter lucrative new markets by providing:

  • High-Definition Print: Reproduce small letters, fine textures, gradations, and color-matched graphics with ease.
  • High Productivity: Do more with staggered printheads, powerful UV lamps, and an A2 or A3 print bed.
  • Greater Flexibility: Print directly on substrates and three-dimensional objects up to 8 inches thick, including cylindrical items with an optional rotary attachment.
  • Intuitive Interface: Now with touchscreen control and more powerful, easy-to-use VersaWorks 7 RIP software

Productivity Features

 

Broad Substrate Compatibility

Print onto a virtually limitless range of flexible and rigid substrates and objects.

Efficient and Fluid Workflows

Produce your work, your way with flexible job-management features.

Professional Color Management

Match your customers' color with ease thanks to advanced RIP features.

Printing Distance Mode

Print directly onto irregular or curved objects with a high degree of accuracy.

Time Saving Turnaround

Switch to digital direct-to-object printing and eliminate long set-up and finishing times.

 

Get your EUV5 Inks here.

 

// Uses React's native (unpatched) value setter + a real dispatched event, // so the app's own onChange / validation / append logic fires correctly. // build the visible field the user will actually type into // copy the real field's classes + computed styles so it looks identical // preload with existing value (formatted) if the real field already has one // hide the real field visually but keep it in the DOM and functional, // so your app's own validation / append event still works as before // place the visible field right where the real one used to be // send only the plain digits to the real field — this matches what // the numeric field type expects, so no "invalid phone number" error // keep focus/blur events flowing to the real field too, in case your // app's validation triggers specifically on those