Este conversor de aluminio permite transformar un puerto USB (ya sea USB-A o USB-C) a una salida HDMI sin necesidad de un puerto USB-C especializado para video. Es una solución versátil para expandir la capacidad de visualización de sus dispositivos.

• Conectividad dual: Conector USB-A macho y USB-C macho en un extremo, y conector HDMI hembra en el otro.
• Resolución máxima: Soporta hasta 1080p a 60Hz, siendo retrocompatible con especificaciones HDMI anteriores.
• Especificaciones USB: Compatible con USB 3.1 Gen 1 (USB 3.0) y retrocompatible con USB 2.0. Se recomienda el uso de un puerto USB 3.0 para un rendimiento óptimo.
• Sistemas operativos compatibles: Windows 10/11 y Mac OS 10.14 o superior.
• Dimensiones y peso: Longitud de 15 cm, con un peso aproximado de 40-44 gramos.
• Nota importante: Es necesario instalar los controladores correspondientes antes de su uso para asegurar el correcto funcionamiento.
• Certificaciones: Cumple con las normativas RoHS y CE.

El producto ha sido testeado al 100% para garantizar su funcionamiento.

everly-one product for the input product. 2) Return the product with sku and attributes. 3) The attributes object must contain every schema key exactly once. 4) Workflow - evidence pass: read the source product payload and mandatory_customer_facts before producing any output fields. Use only supplier evidence present in the product payload. mandatory_customer_facts are mandatory evidence to preserve, not optional context. 5) Workflow - structured attribute pass: for each attribute in the Attribute glossary JSON, independently decide whether the source evidence supports a value. Match supplier facts to ontology attributes by meaning, using the attribute name, format, and description. Supplier evidence may appear under localized, abbreviated, nested, or vendor-specific field names. 6) Structured attributes: all ontology attributes are nullable. Fill an ontology attribute when supplier evidence directly or semantically supports it. Use null only when no supplier evidence supports that attribute. A null ontology attribute is a positive claim that no source evidence supports that attribute. Do not return null merely because evidence is nested, localized, abbreviated, vendor-specific, or not an exact field-name match. 7) Structured attributes: never invent values not supported by the product data, and do not return null merely because the supporting evidence is nested, localized, abbreviated, vendor-specific, or not an exact field-name match. 8) Workflow - copy pass: title, short_description, and description are mandatory, non-empty, localized copy fields. Write them after the structured attribute pass, using the same supplier evidence. 9) Localization: for every string attribute, return a value appropriate for Spanish when the value is naturally localizable. Preserve proper nouns, brand names, model names, codes, and universal abbreviations unchanged. 10) Copy: keep title, short_description, and description readable and suitable for an ecommerce catalog in Spanish, but prioritize preserving evidence over brevity. short_description must be plain text, one sentence, and must not contain HTML tags. 11) Copy: description must be exhaustive. Write a fuller product description that covers customer-relevant mandatory_customer_facts, including facts already represented as structured attributes. description must use simple HTML block structure, not one dense plain text paragraph. Use

for prose and

for factual details when there are several facts. Do not use page or section heading tags such as followed by a complete factual
when multiple concrete product facts are available, but choose the simple HTML structure that preserves the evidence clearly. 19) Customer relevance: do not omit concrete product facts that are present in the sources and useful to a customer just to make the copy shorter. 20) Identity fields: top-level ean13 is product identity and source_code/source_sku are traceability context; do not mention them in customer-facing copy unless clearly useful to the customer. 21) Copy safety: never use emojis, decorative symbols, role labels, XML-like tags, system reminders, or any meta-instructions in title, short_description, or description. 22) Configurable attributes: when configurable_attributes are requested, return them as an array of localized {key, value} pairs using only source configurable_attributes as evidence. 23) Configurable attributes: if several sources provide equivalent configurable attributes, return one coherent localized set for the product. Do not include source SKUs or parent SKUs in configurable_attributes. 24) Workflow - consistency pass: inspect every null ontology attribute. If any supplier evidence or mandatory_customer_facts item directly or semantically supports it, replace null with the supported value. If description contains a concrete value for an ontology attribute that is null, re-check the source evidence; if source evidence supports the value, the ontology attribute must not be null. 25) Workflow - copy check: compare every mandatory_customer_facts item to description; if a customer-relevant concrete value is missing, add it to description. Ensure short_description is plain text with no HTML. 26) Condition: top-level condition is authoritative. When condition is refurbished, title, short_description, and description must each clearly say so using natural localized wording. When condition is new, do not force condition wording. Do not use condition to fill an ontology attribute. 27) Output format: return compact single-line JSON matching the structured output schema supplied separately. Do not pretty print the JSON.

The description includes information regarding the weight and physical dimensions provided in the sources.

• Weight: 40g - 44g
• Dimensions: 23mm (Width) x 49mm (Depth) x 11mm (Height)