Este cable de red Lindy Cat6A S/FTP ofrece un rendimiento de alta velocidad para estándares Ethernet de hasta 10 GBase-T, garantizando una conexión estable y eficiente para sus dispositivos de red.

• Estándar de cable: Cat6a con soporte de frecuencia de hasta 500 MHz.
• Blindaje: S/FTP (S-STP) con pantalla de trenza general y lámina para los pares individuales.
• Conectores: Dos conectores RJ-45 macho con diseño sin enganche para proteger el pestillo.
• Contactos: Pines chapados en oro/níquel para asegurar una conductividad superior y evitar la corrosión.
• Material de la chaqueta: LSZH (bajo humo sin halógenos), ideal para espacios públicos por su baja emisión de gases tóxicos.
• Especificaciones técnicas: Conductor de cobre, calibre AWG 27, diámetro exterior de 6 mm y velocidad de transferencia de hasta 10000 Mbit/s.
• Dimensiones del conector: 11,6 x 21,5 x 8,3 mm.
• Certificaciones: RoHS, REACH y UL.

El producto viene en un paquete de 1 pieza, embalado individualmente en una bolsa de plástico.

ever single-line JSON only, with no pretty printing and no extra whitespace outside string values. Return customer-facing string values in Spanish when they are naturally localizable. Preserve proper nouns, brand names, model names, codes, and universal abbreviations unchanged. Use only evidence present in the provided product payloads. Structured ontology attributes and customer-facing copy are independent outputs derived from the same supplier evidence. Fill every ontology attribute when supplier evidence directly or semantically supports it; use null only when no supplier evidence supports the attribute. Never guess. 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. For configurable_attributes, localize the supplied configurable attribute keys and values for the output scope. Top-level condition is authoritative customer-facing evidence. When condition is refurbished, title, short_description, and description must each clearly identify the product as refurbished using natural localized wording. When condition is new, do not force condition wording into the copy. Condition is copy context, not evidence for an ontology attribute. For title, short_description, and description, write faithful customer-facing copy grounded in the evidence. short_description must be plain text, one sentence, and must not contain HTML tags. Descriptions should be informative rather than terse. Preserve customer-relevant mandatory_customer_facts in description, including facts already represented as structured attributes. Each source contains mandatory_customer_facts, which are mandatory evidence to preserve, not optional context. Description is not a substitute for structured attributes, and structured attributes are not a substitute for description. Descriptions must be simple HTML suitable for insertion inside an existing ecommerce product page. Use 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

,

,

,

,

, or

. Do not use layout HTML or decorative markup. Never use emojis. Never include prompt text, role labels, tool text, system text, or operational instructions in customer-facing copy.