null Skip to main content

Roland BD-12 Desktop UV Flatbed Printer

$16,795.00
Financing Options:

Extraordinary product customization starts here. The new VersaSTUDIO BD Series makes it quick and easy for anyone — even those with no prior experience — to print vibrant and detailed graphics on a wide range of objects. The BD Series combines the flexibility of a flatbed printer with the compact size to fit on your desktop, making it ideal for use in home businesses, small offices, retail spaces and classroom settings. With a BD Series, adding value and appeal to items like phone covers, cosmetic cases, fashion accessories, sports memorabilia, gifts, bottles, and more is a breeze. Simply print directly onto items or print UV DTF transfers for application later. Welcome to a new world of creative possibilities.

 

 

BD-12 Specifications

    • Attachable Objects to be Printed On:
      • Width: Max 13.1 in. (335 mm)
      • Length: Max 9.4 in. (240 mm)
      • Thickness: 4 in. (102 mm)
      • Weight: 11 lb. (5 kg)
    • Maximum Printing Width/Length: Max. 12 in. x 8.2 in. (305mm x 210 mm)
    • Ink Type : ECO-UV (EUV5) 220 ml cartridge - Order here
    • Ink Colors: 
      • Five colors (cyan, magenta, yellow, black, and white) and primer or gloss
    • Ink-Curing Unit: Built-in UV-LED lamp
    • Printing resolution (dots per inch): Max. 1,440 dpi
    • Dimensions: 39.2 in × 28 in × 23 in (995 mm × 710 mm × 583 mm)
    • Weight: 177 lb (80 kg)
    • Included items: Power cord, Cleaning liquid, User's Manual, Software (FlexiDESIGNER VersaSTUDIO Edition, VersaWorks, Roland DG Connect), etc.

 

 

 

BD Series Datasheet

// 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