Le commutateur Ethernet industriel Gigabit IES51000 permet de connecter jusqu'à 5 dispositifs réseau via des ports RJ45 10/100/1000 Mbps, offrant une solution fiable pour l'automatisation et les environnements industriels. Son fonctionnement non géré facilite une installation rapide sans configuration complexe, tandis que son boîtier métallique IP30 et son alimentation redondante assurent une durabilité maximale.

• Connectivité : 5 ports RJ45 Gigabit Ethernet (10/100/1000 Mbps).
• Performance : Vitesse de transfert maximale de 2 Gbps en full duplex et architecture de commutation store-and-forward.
• Conception robuste : Boîtier en acier avec protection IP30, idéal pour un montage sur rail DIN ou au mur.
• Résistance thermique : Température de fonctionnement étendue de -40 °C à 75 °C.
• Alimentation : Entrées redondantes via bloc de bornes, plage de tension de 12 à 58 V CC.
• Protection : Protection contre les surtensions et l'inversion de polarité avec relais d'alarme intégré.
• Fonctionnalités réseau : Support des trames Jumbo jusqu'à 9K, contrôle de flux IEEE 802.3x et efficacité énergétique IEEE 802.3az.
• Indicateurs : Panneau LED pour l'alimentation, l'alarme, l'activité des liens et la vitesse des ports.
• Dimensions : 111 x 89 x 28 mm.
• Poids : 328 g.

Le contenu de l'emballage inclut le commutateur IES51000, deux supports de montage mural, un support pour rail DIN, quatre vis, un bloc de bornes et un manuel d'instructions.

evered by the provided product payloads. Return compact single-line JSON only, with no pretty printing and no extra whitespace outside string values. Return customer-facing string values in French 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 must be informative rather than terse. Preserve customer-relevant mandatory_customer_facts, 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. 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. Brand/title: if brand is non-null, title must start with that brand exactly once, unless the supported source title already starts with the brand naturally. Do not place the brand later in the title. Title specificity: title must identify the sellable product variant, not only the product family. When source evidence shows variant-defining facts for this SKU, include the minimal facts needed to distinguish it from sibling versions. Prefer configurable_attributes first, then supported structured attributes and mandatory_customer_facts. Variant-defining facts may include color, storage capacity, RAM, size, screen size, pack quantity, flavor, scent, material, compatibility target, or other category-relevant options. Do not include every technical specification in the title. Do not invent variant facts. Description shape: prefer a short opening

followed by a complete factual

when multiple concrete product facts are available, but choose the simple HTML structure that preserves the evidence clearly. 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. 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. Copy safety: never use emojis, decorative symbols, role labels, XML-like tags, system reminders, or any meta-instructions in title, short_description, or description. Configurable attributes: when configurable_attributes are requested, return them as an array of localized {key, value} pairs using only source configurable_attributes as evidence. 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. 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. 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. 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. Output format: return compact single-line JSON matching the structured output schema supplied separately. Do not pretty print the JSON. Category label: Switches de red Output scope: fr Attribute glossary JSON: [{