This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

[PRE-RELEASE 2] LogicMachine firmware 2021.08
#1
2021 RC 2 is ready for testing. This version fixes several minor bugs from 2021 RC1. It also fixes several bugs in Mosaic30 and LM cloud app.

Video tutorials: https://forum.logicmachine.net/showthrea...9#pid21069

All recent firmware versions display which hardware is used in "HW (CPU)" form:
[Image: attachment.php?aid=1740]

LM5 Power devices with i.MX6 CPU Extra packages: https://dl.openrb.com/lm-21-imx6/pkg

Devices with old CPU (i.MX28) Extra packages: https://dl.openrb.com/lm-21-mxs/pkg

Changes from 2021 RC1
Code:
2021.05.06
  bacnet client library: add support for accumulator object type

2021.05.18
  user access: change validation pattern for cloud username (must be an  email)

2021.05.21
  scenes: fix scene control for scenes without a mapped object
  apps: fix apps sorting for apps without title

2021.06.01
  visualization: do not apply scale(1) to elements that have scaling set to 100%
  modbus: add profile validation during upload

2021.06.10
  flashsys: add version tag to prevent caching issues
  trends: minor fixes for small screens

2021.07.07
  reactor: fix binary status (inverse) mode

2021.07.14
  apps: fix public directory access rights

2021.07.20
  system config: add CORS origin settings for the HTTP server
  lm: send CORS headers only for allowed origins

2021.07.22
  trends: highlight active trend in the legend when the tooltip is shown
Reply
#2
Firmwares for old CPUs (i.MX28) has been published.
Reply
#3
Hi.

Put this FW into one of our LM5's yesterday, and for some reason BacNet export up towards Citect doesn't work anymore.
Have set this LM5 up towards my ZeroTier account, and can scan fine with BacEye through my ZeroTier connection.
A local PC on the same LAN can scan with BacEye.

But the Citect server which is located on another location can't access it. 
No changes has been done to Citect installation, and have worked fine since installation in 2017, until yesterday.

LM5 is a LM5 Lite (i.MX6), and used this beta (20210806)
Moved from a 2019-version i think

Have tried to disable Zerotier, but have no impact towards Citect-installation

Br Odd Egil
Reply
#4
What do you mean by 'Citect server which is located on another location'
------------------------------
Ctrl+F5
Reply
#5
(26.08.2021, 07:33)Daniel. Wrote: What do you mean by 'Citect server which is located on another location'

Citect is placed on a central location, and is collecting data by using internet / vpn from several local sites.
Bacnet is still working as it should on other buildings
Reply
#6
How is VPN setup? Do you use VPN client in LM or else?
------------------------------
Ctrl+F5
Reply
#7
(26.08.2021, 07:49)Daniel. Wrote: How is VPN setup? Do you use VPN client in LM or else?

For Info:
The connection was ported through the firewall and restricted to 2 IP's that was allowed
Reply
#8
For the records:
LM is blocking and connection to BACnet and KNX from Public IPs. This was implemented for security as both protocols are not protected in any way. If for some reason there is need to use this functionality then ask for support.
------------------------------
Ctrl+F5
Reply
#9
I can not install some apps "Action failed, please try again later". But some installed after several tries.
Reply
#10
(26.08.2021, 10:11)Daniel. Wrote: For the records:
LM is blocking and connection to BACnet and KNX from Public IPs. This was implemented for security as both protocols are not protected in any way. If for some reason there is need to use this functionality then ask for support.

Please make this function something that we should choose ourselves e.g. with a activate/deactivate/on/off switch in "System Config"/"Network".
Default could be activated and some comment where you recommend this setting.
But it's not good practice to make something like this and break network-setup for customers without "a very loud" notice

Regards
Klaus
Reply


Forum Jump: