# setup (Monday)

sqlexpr (needs internet, but can be installed through an offline version of the installer)
- server configuration: mixed mode
- password: abc
- sql server administrator: aslak-PC\aslak (aslak)

smartconnector
- sql server express
- give previous password (abc)
- localdb requires (like sql express) a separate install
- if successful it will start a service exposing a web interface on http://localhost:8082/Login
  - username: admin
  - initial password: Admin!23
  - new password: Password!23

smartconnector license:
- Get it from here: https://www.smartconnectorserver.com/Marketplace
- password: Password!23
- developer license for runtime 2.4 (developer) under license depot
- license key: 83AE460B2A7C26CED5CB65057501938CDE5C4060687E9F820213AC605D52B08B061FE48156FED89E84F7FA88AA81515A13B4B0700217D77575DCF101F8631CD2
- developer lincese runs out in 60 days. Then you just go back and get another one

install enterprise server (in the /Ebo of the archive, all defaults)
- License Administrator
- Enterprise Server (http:80, https:443, TCP:4444, local system)
- Workstation

run licence administrator (which is now installed)
- chose Licences and add the license file from under /Ebo
- this will run out
- Get a new one from the exchange community or through Niels (Schneider DK)

run "software administrator building operations" (search in the start menu)
- watch out for red marks (indicating port conflicts)
- start the server

run "workstation building operation" (type in start menu)
- default username password: admin/admin
- new password: Password!23
- also exposes https://localhost

install azure data studio (for a backchannel into the database of users (encrypted) and endpoints (not encrypted))

NuGet account:
- Password: Password!23
- https://www.myget.org/F/mongoose/auth/530ff9fe-a643-4636-9745-eff419fb3253/api/v3/index.json

# tuesday

definition slides could use more structure to ease reception

ews clients reuse connections

the smart connector thread count is basically a thread pool

"+" can be used to bind to all interfaces

password age limit set to zero to not require it to change

SubscriptionReader seems important

asynchronuous operations only goes to the SQL database (which is updated on a schedule) where as synchronuous goes directly to the source (and is then slow)

passive third party data flow seems interesting

every public property will be exposed for configuration through the UI

NoBusyWait() - otherwise a busy while loop will eat your memory (don't use busy wait)

ILongRunningProcess, e.g. for processes listening on a socket

https://github.com/buildingslabs/smartconnectorsamples

EWO only supports 30 min subscriptions, then it gets automatically unsubscribed

forcing is performing a manual override

only one program can write to a point. This can at times lead to ugly code

Scripts are working on raw values so one has to be a bit carefull to make it portable between imperial and metric. The UI does conversion to your locale though.

SmartConnector.Utilities under NuGet (from public repo that we can contribute to)

you can use tuples in c#

openweathermaps can give you current and predicted waether for free

Logger.LogError and Logger.LogDebug

openweathermap account:
- asjo
- Password!23_
- Default api key: 1186cc9834d174db8a0678dcc56382f1

Install https://marketplace.visualstudio.com/items?itemName=NUnitDevelopers.NUnit3TestAdapter

F12 goes to definition

# wednesday

how to open the code: Got to C:\Users\aslak\source\repos\SmartConnectorSamples and click "SmartConnectorSamples". This is a solutions file.

got the weather forecasts working by completing the merge (maybe?)

you can deploy a debug dll and then licence won't be required

3 types of subscriptions in ebo
- value changes: sensor values
- hierarchy changes: e.g., a point being moved
- alarm changes: not really sure

trends is a timeseries

alarm consists of a timestamp, a message, a priority and a linked point

custom ews servers

licensing ...

when building for release the resulting dll will be in C:\Users\aslak\source\repos\SmartConnectorSamples\SmartConnector.WeatherExtension\bin\Release . It needs to be moved to C:\Program Files\Schneider Electric\SmartConnector

Logs: C:\ProgramData\SmartConnector\Logs

C:\ProgramData is hidden!

whatever I rightclick and host will be created on your server

TODO: we should add a "configured" signal

we get a timestamp for when a point is invalidated

Jeff says that some Russians have been working on a high-performance OPC (da or ua?) smartconnector thing

send jeff an email about getting access to the smartconnector developer forum

yesterday we had tu import stuf from XsL

# Wednesday: writing a processor

managedewsclient is recommended over ewsclient

it is SOAP

subscriptions seem very volatile and complex (lots of potential exception to take care of) to work with

The cache is essentially a shared memory segment, which can be cleared. The reason for having multiple segments is protection.

limit subscription to 500-1000 items to avoid errors

the plan is to move some of the code Jeff is writing today into the utilities libraries for convenience.

UpdateValues(...) -> SendValues(...)

the cache of a test is being cleared before/after(?) every execution

invalid id if the interface is offline (e.g., if openweather was down)

subscriptions are better than getvalues

the get going guide?







# misc notes (monday ...)

quite nice graphics based on HTML5

they use a hardcoded conditioning time for room scheduling

alexa support for room scheduling, and temperature setup

they have a structural overview of the breaker system

extract some information from IFC and BIM models, but has humans in the loop

they can remotely lock and unlock doors

cheap sensor for retrofitting desks for occupancy detection

uses interfaces with named entries for mapping scripts to point names

haystack-style tag names and brick for the future metadata

github project: olga ontology library generator, build on stardock(?). ecostructure olga

smartconnecter is for everything which doesn't ahve a native interface

If I poll I will get the latest value at the timestamp of querying. If I go through trendlogs, I will get the time of reception/sampling.

Can we pull the meter data through Schneider?

csp (common service protocol?) protocol for quick access (but still involves polling)

ews support polling and subscription (which is basically polling on dynamically defined sets of points)

As (automation server) has minited space for logs, ES (enterprise server) does not.

thin client is a browser, thich client is the "workstation" desktop application

tenant: this is where I can add users through their emails

azuredatastudio is usefull for looking at what is in the database. SQL management studio (2012) can also be used.

Documentation (guide really): C:\Program Files\Schneider Electric EcoStruxure\Building Operation 2.0\WorkStation\Guide

Logs (c# logging ends up here): C:\ProgramData\SmartConnector\Logs

Choose severity for logging: http://localhost:8082/ServiceSettings

Choose which things to log: http://localhost:8082/LoggingFilters

Existing scripts and how to use them: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 2.0\WorkStation\Script Editor\Code Library

the scripting language is "plain englist"

code has to be run by a task

point names are relative to the folder the script is contained in

manual mapping from a well-defined tree structure (e.g., /sdu/ou44/u180/temperature) to providers (e.g., some some path under bacnet)

can use SoarUI for testing

Digital means boolean

multistate is essentially an enum

opening a script editor is REALLY slow

a scipt can see if a point is online (or if a point is bound to it)

binding templates for primitive automatic searches for potential bindings

flavor of what is coming (not done or given):
- pacific electic for brick?