EnOcean profiles supported in LM

[zubin]

   

Finally I got it working. Thanks for the excellent help. I had to change the b0 to 9. (Found this when I understood how the dimmer behaved when setting it to raw bytes, split)

If anyone ever need to control a FUD61NPN-230V actuator here are my notes:

1. First of all turn on confirmation signal on the actuator: top rotary switch to CLR, LED flashes, during 10 seconds turn bottom rotary switch all the way to the left 3 times, LED light is on for 2 seconds.
   
2. Follow guide that admin posts above (in example below my 4-byte unsigned integer object had address 1/1/5):
   First, you have to create one object with 4-byte unsigned integer data type and another with 1-byte scaled. 4-byte object should be mapped to KNX > EnOcean object with 4-byte RAW profile.
   
3. Add the following script to the 1-byte scaled object (just for initial teach command):
   b3 = 0xE0b2 = 0x47b1 = 0xFFb0 = 0x00a3 = bit.lshift(b3, 24)a2 = bit.lshift(b2, 16)a1 = bit.lshift(b1, 8)res = bit.bor(a3,a2,a1,b0)grp.update('1/1/5', res, dt.uint32)
   
4. Put the actuator into learning mode: turn bottom rotary to EC1, upper rotary to LRN
   
5. Set an object value for 1-byte scaled object (0-100) to teach in. (The actuator should stop flashing)
   
6. Turn back actuator to desired functionality
   
7. Add the following script to 1-byte scaled object (to be able to control the actuator)
   -- dimmingb3 = 0x02-- dimmer value [0..100]b2 = event.getvalue()-- ramp time in secondsb1 = 1-- data telegram, absolute value, store finalb0 = 9a3 = bit.lshift(b3, 24)a2 = bit.lshift(b2, 16)a1 = bit.lshift(b1, 8)res = bit.bor(a3,a2,a1,b0)grp.update('1/1/5', res, dt.uint32)
   
8. The dimmer can now be controlled through the 1-byte scaled object
   

If you need to read the values from the actuator as a 1-byte scaled object:

1. In EnOcean >> KNX tab find the actuator (that should send confirmation signals if step 1 above was followed)
   
2. Set profile as "RAW 4-bytes, split"
   
3. Map Data Byte 2 to an object.
   
4. Create a new object as "5.001 scale" (in my example 1/1/6)
   
5. Add the following script to the Data Byte 2 object created in point 3:
   value = event.getvalue()res = (value/100)*255grp.write('1/1/6', res, dt.uint8)
   

Hello jorgenbl,

I tried your above mentioned step but unfortunately it didn't work for me for dimming case.

i was able to only Turn On/Off the light in FUD61NPN-230V

Also for information i tested the received signals from LM3 in Enocean Dolphin
Please refer below attached image.

Data telegram received for Dimming  from LM3 seems perfect and are actually as required by Eltako , but still i dont know how it dosent dims the light for me.

Please let me know where am i wrong .

Please refer image attached 1,2,3 for scripting done in LM3
and image 4 for Dolphin view received telegram from LM3

Also note i have taught in under EC1 position.

Have you tried the scripting for Eltako FSB61NP-230V curtain actuator ??

Waiting for your positive reply.

Thanks.

   
   
   
   

---

Please see below TXT with EnOcean profiles which we currently support in LogicMachine. 
More profiles can be added by request.

05-01-01 = Rocker Switch, 1 Rocker
05-01-02 = Rocker Switch, 1 Rocker (inverted)
05-01-03 = Rocker Switch, 1 Rocker (separate)
05-02-01 = Rocker Switch, 2 Rocker
05-02-02 = Rocker Switch, 2 Rocker (inverted)
05-03-01 = Rocker Switch, 4 Buttons
05-04-01 = Key Card Activated Switch
05-10-00 = Window Handle
06-00-01 = Single Input Contact
07-02-01 = Temperature Sensor (-40C..0C)
07-02-02 = Temperature Sensor (-30C..10C)
07-02-03 = Temperature Sensor (-20C..20C)
07-02-04 = Temperature Sensor (-10C..30C)
07-02-05 = Temperature Sensor (0C..40C)
07-02-06 = Temperature Sensor (10C..50C)
07-02-07 = Temperature Sensor (20C..60C)
07-02-08 = Temperature Sensor (30C..70C)
07-02-09 = Temperature Sensor (40C..80C)
07-02-10 = Temperature Sensor (-60C..20C)
07-02-11 = Temperature Sensor (-50C..30C)
07-02-12 = Temperature Sensor (-40C..40C)
07-02-13 = Temperature Sensor (-30C..50C)
07-02-14 = Temperature Sensor (-20C..60C)
07-02-15 = Temperature Sensor (-10C..70C)
07-02-16 = Temperature Sensor (0C..80C)
07-02-17 = Temperature Sensor (10C..90C)
07-02-18 = Temperature Sensor (20C..100C)
07-02-19 = Temperature Sensor (30C..110C)
07-04-01 = Temperature & Humidity Sensor (0C..40C, 0%..100%)
07-04-02 = Temperature & Humidity Sensor (-20C..60C, 0%..100%, Battery)
07-06-01 = Light Sensor (300lx..60000lx)
07-06-02 = Light Sensor (0lx..1024lx)
07-06-03 = Light Sensor (0lx..100lx, 300lx..30000lx)
07-07-01 = Occupancy Sensor
07-08-01 = Light Sensor 0lx to 510lx, Temperature 0°C to +51°C and Occupancy
07-08-02 = Light Sensor 0lx to 1020lx, Temperature 0°C to +51°C and Occupancy
07-08-03 = Light Sensor 0lx to 1530lx, Temperature -30°C to +50°C and Occupancy
07-09-04 = Humidity, CO2, Temperature Sensor
07-10-01 = Temperature Sensor; Set Point, Fan Speed and Occupancy Control
07-10-02 = Temperature Sensor; Set Point, Fan Speed and Day/Night Control
07-10-03 = Temperature Sensor; Set Point Control
07-10-04 = Temperature Sensor; Set Point and Fan Speed Control
07-10-05 = Temperature Sensor; Set Point and Occupancy Control
07-10-06 = Temperature Sensor; Set Point and Day/Night Control
07-10-07 = Temperature Sensor; Set Point and Fan Speed Control
07-10-08 = Temperature Sensor; Fan Speed Control
07-10-09 = Temperature Sensor; Fan Speed and Day/Night Control
07-10-10 = Temperature and Humidity Sensor; Set Point and Occupancy Control
07-10-11 = Temperature and Humidity Sensor; Set Point and Day/Night Control
07-10-12 = Temperature and Humidity Sensor; Set Point Control
07-10-13 = Temperature and Humidity Sensor; Occupancy Control
07-10-14 = Temperature and Humidity Sensor; Day/Night Control
07-30-01 = Single Input Contact, Battery Monitor
07-30-02 = Single Input Contact

Hello Admin

It would be great if you add in 

1. A5-12-01 - ENERGY KWH MONITORING.
2. A5-20-03 - WIRELESS BI-DIR ACTUATOR (FOR % FEEDBACK VISUALIZATION)

Thanks