ENsigfox DRY CONTACTS - Guide utilisateur / User guide version V1.2.064Page of 804.1.2 Product configuration data framesFollowing reception of a downlink frame with the code 0x10 or on switching to the operating mode (from the Park or Command Mode), thenext frames (0x10 to 0x14) representing the application configuration of the product are transmitted:0 1 2 3 4 5 6 7 8 9 10Code Status PAYLOAD0x10 Cf Status S300 S301 S302 S303 S304 S305 S306 X X0x10 0xAB 0x90 0x48 0x73 0x00 0xB4 0x32 0x01Description of the frame:• Byte 2: register 300, periodicity of the Keep Alive frame, expressed in tens of minutes• Byte 3: register 301, periodicity of transmission (periodic mode), expressed in tens of minutes• Byte 4: register 302, configuration of input TOR1• Byte 5: register 303, configuration of input TOR2• Byte 6: register 304, configuration of input TOR3• Byte 7: register 305, configuration of input TOR4• Byte 8: register 306, product mode (Park, Standard (production), Test or REPLI)In the example in grey this gives:• Byte 2=0x90: register 300, Keep Alive frame transmitted every 12 hours• Byte 3=0x48: register 301, periodical transmissions are made every 0x48=72 in decimal x 10 minutes = 720 minutes i.e. every 12 hours• Byte 4=0x73: register 302:• TOR1 configured in periodic mode• Counting of high and low edges• Waiting period of 1 second• Byte 5=0x00: register 303:• TOR2 disabled• No waiting period• Byte 6=0xB4: register 304:• TOR3 configured in event mode• Detection of high edges only• Waiting period of 20 second• Byte 7=0x32: register 305:• TOR4 configured in periodic mode• Counting of low edges only• Waiting period of 50 milliseconds• Byte 8=0x01: register 306, Production mode in progressIn this example, given that inputs TOR1 and TOR4 are configured in periodic mode, the transmission period of the Keep Alive frame has noimpact because it is not emitted.