> For the complete documentation index, see [llms.txt](https://enless.gitbook.io/centre-aide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enless.gitbook.io/centre-aide/guides-installation/capteurs/editor-12/informations-generales.md).

# Informations générales

TX PULSE : informations générales

{% columns %}
{% column width="41.66666666666667%" %}

<div data-with-frame="true"><figure><img src="https://1364423745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FtlamWRy9KZUPtb43CyJ4%2F600_036_Frontview_v2.png?alt=media&amp;token=b12f0d1c-9f56-457e-b7b2-9b22adaac89b" alt=""><figcaption></figcaption></figure></div>
{% endcolumn %}

{% column width="58.33333333333333%" %}
Conçu pour la télérelève de compteurs, ce capteur LoRaWAN se raccorde sur vos compteurs d’impulsions (contact-sec ou collecteur ouvert). Il compte le nombre d’impulsions générées par le compteur et envoie périodiquement l’index en radio.

Compatible avec les protocoles LoRaWAN et LoRa Easy (protocole propriétaire Enless), ses données peuvent être remontées directement vers votre système de supervision ou votre GTB, sans tirage de câbles ni travaux lourds.
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
La garantie de ce produit est de 24 mois
{% endhint %}

### Caractéristiques

<table data-header-hidden><thead><tr><th width="228.67578125"></th><th></th></tr></thead><tbody><tr><td><strong>Protocoles supportés</strong></td><td>LoRaWAN<br>LoRa Easy (protocole propriétaire Enless)</td></tr><tr><td><strong>Classe LoRaWAN</strong></td><td>Classe A</td></tr><tr><td><strong>Version LoRaWAN</strong></td><td>Version 1.0.2 | RP001-1.02. revB <mark style="color:$tint;">(TX PULSE 600-036)</mark><br>Version 1.0.4 - RP002-1.0.3 <mark style="color:$tint;">(TX PULSE 600-136)</mark></td></tr><tr><td><strong>Fréquence</strong></td><td>EU868 <mark style="color:$tint;">(TX PULSE 600-036)</mark><br>US915 <mark style="color:$tint;">(TX PULSE 600-136)</mark></td></tr><tr><td><strong>Identifiants</strong></td><td>LoRaWAN : DevEUI, AppEUI, AppKey<br>LoRa Easy : LoRa ID</td></tr><tr><td><strong>Puissance d'émission</strong></td><td>25mW (14 dBm)</td></tr><tr><td><strong>Encryptage</strong></td><td>AES128 en mode LoRaWAN</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="235.28515625"></th><th></th></tr></thead><tbody><tr><td><strong>Indice de protection boitier</strong></td><td>IP65</td></tr><tr><td><strong>Fixation</strong></td><td>Murale (vissé), Collier, Rail DIN</td></tr><tr><td><strong>Température de fonctionnement</strong></td><td>-20 / +55°C</td></tr><tr><td><strong>Alimentation</strong></td><td>Batterie Lithium 3 .6V type D (BAT D 1000-031)<br>Info : Batterie remplaçable</td></tr><tr><td><strong>Durée de vie de batterie</strong></td><td><p>12 ans pour un envoi toutes les 5 minutes (SF9)</p><p>Jusqu’à 15 ans d’autonomie<br><br>Attention : un stockage prolongé des batteries sans être utilisées (plus de 6 mois) peut entrainer un risque de passivation et une réduction de l'autonomie annoncée.</p></td></tr><tr><td><strong>Paramétrage</strong></td><td>LoRaWAN : Downlink<br>LoRa Easy : Depuis le serveur du récepteur</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="226.40625"></th><th></th></tr></thead><tbody><tr><td><strong>Interface</strong></td><td>Entrées impulsionnelles</td></tr><tr><td><strong>Nombre d’entrées</strong></td><td>2 entrées</td></tr><tr><td><strong>Type d’entrées</strong></td><td>Contact-sec et Collecteur ouvert</td></tr><tr><td><strong>Type d’impulsions supportées</strong></td><td><p>Durée : 50ms minimum</p><p>Fréquence : 10Hz maximum</p></td></tr><tr><td><strong>Fonction additionnelle</strong></td><td>Antirebond</td></tr></tbody></table>

### Dimensions

<div align="left"><figure><img src="https://1364423745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FahYLDDJV3P1L5Dr6IdSd%2F600_031_Plans_Full.png?alt=media&amp;token=86e239b1-783f-4e92-b4f4-0fb3e625b3fd" alt="" width="563"><figcaption></figcaption></figure></div>

### Etiquette d'identification

<figure><img src="https://1364423745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FtTgTOsDLlB4PghfAWs13%2FE%CC%81tiquette%20technique%20blanche%20sur%20fond%20transparent.png?alt=media&amp;token=fe27587c-08c2-4c05-a67d-1b524d0f6bdd" alt=""><figcaption><p>Exemple, la référence du produit peut varier selon le modèle</p></figcaption></figure>

### Mentions légales pour les produits 915MHz

<table><thead><tr><th>Anglais</th><th valign="top">Français</th></tr></thead><tbody><tr><td><p>This device complies with part 15 of the FCC Rules and with Innovation, Scienceand Economic Development Canada licence-exempt RSS standard(s). Operation issubject to the following two conditions: (1) This device may not cause harmfuli nterference, and (2) This device must accept any interference received, including interference that may cause undesired operation.<br></p><p>NOTE: The grantee is not responsible for any changes or modifications not expressly approved by the party responsible for compliance. Such modifications could void the user’s authority to operate the equipment.<br></p><p>NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:<br></p><ul><li>Reorient or relocate the receiving antenna.</li><li>Increase the separation between the equipment and receiver.</li><li>Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.</li><li>Consult the dealer or an experienced radio/TV technician for help.<br></li></ul><p>CAN ICES-003(B) / NMB-003(B</p></td><td valign="top"><p>L’émetteur/récepteur exempt de licence contenu dans le présent appareil est conforme aux CNR d’Innovation, Sciences et Développement économique Canada applicables aux appareils radio exempts de licence. L’exploitation est autorisée aux deux conditions suivantes :</p><p>1. L’appareil ne doit pas produire de brouillage.<br><br>2.L’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement.<br></p><p>CAN ICES-003(B) / NMB-003(B)</p></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enless.gitbook.io/centre-aide/guides-installation/capteurs/editor-12/informations-generales.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.