[OLD] LogicMachine firmware 2016.09

[gtsamis]

gtsamis
Please try this patch for your Reactor (this won't work on Load Balancer). Install through Logic Machine -> Utilities -> Install updates.
https://dl.openrb.com/lm-16.09-rc2/20160...x_mxs.lmup

Thank you, 
I will install the update next week and will let you know

[gtsamis]

gtsamis
Please try this patch for your Reactor (this won't work on Load Balancer). Install through Logic Machine -> Utilities -> Install updates.
https://dl.openrb.com/lm-16.09-rc2/20160...x_mxs.lmup

Thank you, 
I will install the update next week and will let you know

Tried it and seems to be working fine.
Thank you admin

[admin]

Good news, thanks for testing

[rocfusion]

Hi, is this patch suitable for the LM4 too, I have noticed objects appearing for no apparent reason.

Thanks,

roger

[admin]

Yes, it's compatible will all published firmwares apart from Load Balancer.

[andeug]

I get the same error: some objects with address 2/xx/xx are apprearing without reason. This happens after I re-program the firmware on any device connected to KNX using my LM4 hardware. Note that I download the firmware via ETS3 using local LAN and I also have USB commissioning port, but I don't use it for such purpose.

Attached is a screenshot.

[rocfusion]

ok thanks, saying that andeug. I get the same impression. Programming modules via the Logic machine with ETS4 is not the same as an USB coupler. Parameters defined in the application programming of modules dont seem to take affect. Will try the patch hopefully this is resolved.

thanks,


Roger

[rocfusion]

Hi,

Ok just tested the RC2 firmware plus the patch with an LM4. Sniffer disabled all is good. Enable sniffer and programmed a dimmer actuator, just changed some parameters so nothing major. Then did an application only download with ets4. After that new objects appeared on the LM4. This time 6x 1bit addresses. Something is not right when sniffer is enabled.

Thanks,


Roger

[PassivPluss]

Hi. I Just installer a New Dali driver and the only way I could fint it was to run a full New scan and i had to text/map all existing Dali again. The other options didn't work. The drivers then also changed adresses so I had to blink existing lamps again.

[AEK]

Hi. I Just installer a New Dali driver and the only way I could fint it was to run a full New scan and i had to text/map all existing Dali again. The other options didn't work. The drivers then also changed adresses so I had to blink existing lamps again.

you should set address to new ballast with usb-Dali interface. LM can't set address to one ballast.
then you shoukd use "search only new devices"

[gjniewenhuijse]

Hi. I Just installer a New Dali driver and the only way I could fint it was to run a full New scan and i had to text/map all existing Dali again. The other options didn't work. The drivers then also changed adresses so I had to blink existing lamps again.

you should set address to new ballast with usb-Dali interface. LM can't set address to one ballast.
then you shoukd use "search only new devices"

Or something like this:
- backup your lm!
- connect only the new device to your dali line, temporary disconnect the existing dali devices
- create a 1 byte object with 05 1 byte unsigned integer
event logic for this object:
------------------------------
require('user.dali')
address = tonumber(event.datahex, 16)
log('addr', address)
address = bit.lshift(address, 1) + 1
dalicmd('int', 'setdtr', { value = address })
dalicmd('int', 'storeshortaddress', { addrtype = 'broadcast' })
------------------------------
- set the address for your new dali devices with this object (only the new dali object is connected on your dali line!!!!!!!)
- search for only new dali devices
- connect all your dali devices back to the dali line

[admin]

Roger, I've tried doing full application download via ETS and I don't see any objects after I had the patch applied on my test LM. Can you try installing the patch once more? What is the physical address of the device that you're programming and which group addresses are appearing?

[andeug]

Hi,


I've really had a bad weekend and I am unable to program anymore my electric panel via LM4. I will describe below the syndromes that I am experiencing:

1. Before restarting, the LM4 had the lower led blinking intermittently in red/green. What this means? CPU high activity? Due to what?
2. When I read the addresses on the line, they are randomly read via LM4's remote connection. I've repeated the scan 3 times and found that the results are different and not all the devices are discovered. Do I have a timeout somewhere? Has anyone experiencing the same issue?
3. I am unable to program any of my KNX switches (and other KNX devices). Most of the devices are not responding anymore, although yesterday I was able to program them all by pressing the button in the back of the devices. This has happened at the first try.

I am connected via local LAN using a Gigabit Ethernet connection. My ETS3 is virtualised on an iMac via Parallels Desktop, with a Windows 7 running as virtual machine.

I cannot program anything right now and I am stuck without switches in my home (don't laugh!  ) and I can control the lights just using the iPhone and the Schneider's 7" Touch Panel. I won't ever try to see what would happen if I re-program an dimming/switching actuator, as I will probably stay without lights in my flat...

Please advise. Should I rollback to another version? Or is it a known problem?


Andreas

[rocfusion]

Hi Andreas,

I have exactly the same thing. You are running multiple line couplers. I have discovered its not possible to program the bus with the default physical address 15 dot. In my installations I set the physical address to 1.0.250. That's because if I set the LM on 1.1, 1.2 and higher you can program the line the LM is on but no other lines. This has been around in all firmware releases that I have used.


Thanks,

Roger

[andeug]

Hi Roger,


See attached what settings I have.

KNX Address: 15.15.255 - > This one I should change it? 
Multicast IP: 224.0.23.12

Also, all my devices are on a single bus line. I have attached a screenshot, for you to understand better how my project is structured. Is it okay that all addresses are starting with 1.1.xx? Please let me know if you need further information and hopefully I will be able to turn on again my lights today... 

I'm in Sweden like in '89 in Eastern Europe, with only 6hrs of light/day, from outside... and I am unable to program my KNX bus.



Thank you,
Andreas

[rocfusion]

Hi Andreas,

Just try setting the KNX address to 1.0.250, restart the LM. The see if you can program.

Thanks,

Roger

[andeug]

Hi Roger,


I've set 1.1.0 to LM4 to the top of the line and all the devices are starting with 1.1.1. 
Both USB and LM4 are programming now the devices locally or remote. This was my problem, actually. 

Thanks a lot for your support and now all my programming via ETS3 works.
I will work now to migrate the whole project in ETS4... not sure if any of the people from this forum are still using the old ETS3...


Andreas

[jorgenbl]

Hi,

I am thinking of upgrading from version "20150917". (LogicMachine Re:actor V3)

All my configurations, scripts, objects, pairing with enocean devices, knx devices etc.
Will this be the same/working after an upgrade? or will I have to pair devices again?
And if I experience issues, a downgrade will roll back to my current settings/configuration?

I want to avoid having to pair all my enocean actuators again.

Can you also please update the supported enocean profile list. (Last thread i could find was from 2015, http://forum.logicmachine.net/showthread...ht=enocean)

thanks,

Jørgen

[admin]

Make a backup before upgrading just in case. All your settings will remain unchanged and you won't have to pair EnOcean devices again.

Current profile list:

Code:

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-0A Temperature Sensor (50C..90C)
07-02-0B Temperature Sensor (60C..100C)
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-02-1A Temperature Sensor (40C..120C)
07-02-1B Temperature Sensor (50C..130C)
07-04-01 Temperature & Humidity Sensor (0C..40C, 0%..100%)
07-04-02 Temperature & Humidity Sensor (-20C..60C, 0%..100%)
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 & Occupancy
07-08-02 Light Sensor 0lx to 1020lx, Temperature 0°C to +51°C & Occupancy
07-08-03 Light Sensor 0lx to 1530lx, Temperature -30°C to +50°C & Occupancy
07-09-04 Humidity, CO2, Temperature Sensor
07-10-01 Temperature Sensor; Set Point, Fan Speed & Occupancy Control
07-10-02 Temperature Sensor; Set Point, Fan Speed & Day/Night Control
07-10-03 Temperature Sensor; Set Point Control
07-10-04 Temperature Sensor; Set Point & Fan Speed Control
07-10-05 Temperature Sensor; Set Point & Occupancy Control
07-10-06 Temperature Sensor; Set Point & Day/Night Control
07-10-07 Temperature Sensor; Set Point & Fan Speed Control
07-10-08 Temperature Sensor; Fan Speed Control
07-10-09 Temperature Sensor; Fan Speed & Day/Night Control
07-10-0A Temperature Sensor; Set Point & Single Input Contact
07-10-0B Temperature Sensor & Single Input Contact
07-10-0C Temperature Sensor & Occupancy Control
07-10-0D Temperature Sensor & Day/Night Control
07-10-0D Temperature Sensor & Day/Night Control
07-10-10 Temperature & Humidity Sensor; Set Point & Occupancy Control
07-10-11 Temperature & Humidity Sensor; Set Point & Day/Night Control
07-10-12 Temperature & Humidity Sensor; Set Point Control
07-10-13 Temperature & Humidity Sensor; Occupancy Control
07-10-14 Temperature & Humidity Sensor; Day/Night Control
07-20-10 Generic HVAC interface
07-30-01 Single Input Contact, Battery Monitor
07-30-02 Single Input Contact
07-38-08-02 Dimmer

[jorgenbl]

Thanks for the quick response.

In the thread I linked to above I had to make a workaround for all of my eltako actuators (FUD161NPN) because my profile was not available in the supported list.
Do you think you will be able to add that any time soon?

http://www.eltako.com/fileadmin/download...lowRes.pdf
From this sheet is seem to be profile: A5-38-08

If I understand correctly that refers to:
07-38-08?


Jørgen