M2M Enginko MCF-LW06485 User manual

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

Table

of

Contents

MCF-LW06485

Operating

Manual

Important

safety

information

Read

this

manual

before

attempting

to

install

the

device!

Failure

to

observe

recommendations

included

in

this

manual

may

be

dangerous

or

cause

a

violation

of

the

law.

The

manufacturer

will

not

be

held

responsible

for

any

loss

or

damage

resulting

from

not

following

the

instructions

of

this

operating

manual.

Do

not

dismantle

or

modify

in

any

way.

Avoid

mechanical

stress

Do

not

use

any

detergent

or

alcohol

to

clean

the

device.

Disposal

information

for

users

Pursuant

to

and

in

accordance

with

Article

14

of

the

Directive

2012/19/EU

of

the

European

Parliament

on

waste

electrical

and

electronic

equipment

(WEEE),

and

pursuant

to

and

in

accordance

with

Article

20

of

the

Directive

2013/56/EU

of

the

European

Parliament

on

batteries

and

accumulators

and

waste

batteries.

The

barred

symbol

of

the

rubbish

bin

shown

on

the

equipment

indicates

that,

at

the

end

of

its

useful

life,

the

product

must

be

collected

separately

from

other

waste.

Please

note

that

the

lithium

batteries

must

be

removed

from

the

equipment

before

it

is

given

as

waste

and

disposed

separately.

To

remove

the

batteries

refer

to

the

specifications

in

the

user

manual.

For

additional

information

and

how

to

carry

out

disposal,

please

contact

the

certified

disposal

service

providers.

1.

Description

This

device

can

be

interfaced

to

any

Modbus

RTU

RS485

device

to

read

and

write

any

register

of

the

connected

device

(up

to

31

slaves

or

512

bytes

of

data

for

every

message)

through

the

LoRaWAN®

platform.

Configuration

is

simply

made

using

a

configuration

file

uploaded

to

the

interface

via

USB

or

with

downlinks.

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

MCF-LW06485

is

available

with

DIN

rail

option

(MCF-DIN105):

2.

Overview

2.1

Technical

data

CPU

Cortex

M4

RTC

EEProm

32KB

Flash

1MB

Encryption

AES

128

bit

LiPo

800mAh

rechargeable

battery

Class

C

LoRaWAN®

stack

EU868,

AS923,

AU915,

US915

Modbus

RTU

RS485

Integrated

termination

and

polarization

resistors

USB

On

The

Go

IoT

node

setup

ad

firmware

upgrade

via

USB

interface

Power

supply

10÷36Vdc

Storage

temperature

range

-20°C

÷

+80°C

Working

temperature

range

-10°C

÷

+70°C

Dimensions

L

x

H

X

P:

81

x

60

x

24mm

3

Installation

3.1

Connection

3.1.1

Connection

as

stand-alone

device

Please

refer

to

following

connections:

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

Name

Description

J3.7

IO5

Modbus

A

(+)

yellow

wire

J3.8

IO6

Modbus

B

(-)

white

wire

J3.9

GND

Negative

power

supply

J3.10

VDD

Positive

power

supply

range

[10-36Vdc]

Power

can

also

be

supplied

by

USB.

3.1.2

Connection

with

DIN

rail

option

Please

refer

to

following

connections:

Modbus

data

lines:

Name

Description

J1.7IO5

Modbus

A

(+)

J1.8IO6

Modbus

B

(-)

Power

supply:

Name

Description

J2.1

Vdc

Positive

power

supply

range

[10-36Vdc]

J2.2

GND

Negative

power

supply

Floor

consumption

(included

termination

and

polarization

resistors):

425mW

Note:

add

600mW

for

a

duration

of

2

seconds

for

every

LoRaWAN

transmission

(in

the

worst

case),

and/or

150mW

for

the

duration

of

the

ModBus

communication.

Power

can

also

be

supplied

by

USB.

3.1.3

Termination/Polarization *Polarizations

are

available

only

if

MCF-LW06485

is

10-36Vdc

supplied.

Please

note

dip2

and

dip3must

have

same

status.

dip1

ON/OFF

=

120

OHM

termination

on

Modbus

INSERTED/NOT

INSERTED

dip2

ON/OFF

=

Modbus

B

line

polarization

INSERTED/NOT

INSERTED*

dip3

ON/OFF

=

Modbus

A

line

polarization

INSERTED/NOT

INSERTED*

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

Quick

flashing

Quick

flashing

3.1.4

Antenna

The

magnetic

antenna

must

be

positioned

on

ametal

body.

It

should

preferably

be

vertical

and

at

least

30

cm

away

from

other

metal

bodies.

The

installation

must

take

place

in

a

place

where

the

LoRaWAN®

signal

coverage

is

good

(SF=7

optimal,

SF=12

weak).

Use

the

provided

clip

to

hold

the

antenna

connector

in

place,

as

in

the

picture:

3.2

Configuration

To

deploy

the

sensor,

use

LoRaWEB

online

tool,

to

setup

LoRaWAN®

credentials

and

other

preferences

(only

available

for

Windows®)

:

(iot.mcf88.cloud/LoRaWeb)

Before

connect

the

device

the

first

time,

please

install

LoRaBridge

applicarions

and

drivers:

Validate

your

settings

reading

data

after

the

write.

enginko

provides,

upon

free

registration,

user

manuals,

javascript

examples,

downlink

generator,

uplink

decoder,

firmware

updates

and

different

tools

:

3.3

System

led

LoRaWAN®

not

configured Slow

flashing

Joining

Sending

Quick

flashing

Receiving

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

Flashing

2

seconds

Flashing

1

second

Data

error

Connection

error

3.4

Firmware

update

Save

the

new

firmware

file

(.exe)

on

the

PC,

run

the

file,

select

the

USB

FW

port

and

start

the

update:

and

waiting

for

the

end

message.

4.

Setup

4.1

Period

is

the

interval

(in

minutes)

between

one

measure

and

the

The

sensor

sends

one

measures

for

every

transmission.

Value

can

be

between

15

and

65535

minutes

(default:

30

minutes).

Period

interval

can

be

set

with

App

or

with

downlink

command.

4.2

Modbus

settings

4.2.1

Serial

line

settings

Baudrate

[bps]:

set

the

baudrate

for

the

serial

line

(defalt

=

off).

Fixed

Steady

state

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

Read

Coil

Read

Discrete

Input

Read

Holding

Registers

Read

Input

Registers

Write

Single

Coil

Write

Single

Holding

Register

Write

Multiple

Coils

Write

Multiple

Holding

Registers

Parity:

set

the

Modbus

frame

parity.

Note:

when

saving

these

parameters,

the

system

asks

if

you

want

to

save

only

or

to

save

and

load

the

Modbus

configuration

file.

4.2.2

Registers

map

configuration

Basic

configuration

is

made

through

an

.XLS

file

containing,

for

every

row,

the

parameters

of

the

register(s)

to

be

read

or

write.

Template

file

can

be

downloaded

here:

File

can

be

uploaded

via

USB

or

sent

with

LoRaWAN®

dowlinks.

Due

to

the

radio

regulation,

the

amount

of

data

that

the

interface

can

send

during

a

period

of

time

can

vary,

and

depends

also

from

duty

cycle,

spreading

factor

and

data

rate.

For

example,

with

EU868

band,

the

MCF-LW06485

can

send

from

1KB

(SF

=

12)

to

30KB

(SF

=

7)

every

hour.

In

case

of

periodic

transmission,

you

have

to

set

the

readingperiod

the

amount

of

data

you

have

to

send

for

every

reading

from

the

slaves.

4.2.3

Configuration

file

format

Label:

mnemonic

label

of

the

register.

Modbus

address:

slave

address

(expressed

as

decimal

value)

Modbus

function:

Function

Code

Register

Type

1

2

3

4

5

6

15

16

Dec

address:

register

starting

address

(expressed

as

decimal

value),

without

offset.

Note:

please

check

Modbus

length:

lenght

(in

word)

of

the

register

to

be

read

or

write.

Attention:in

case

of

“Write

Single

Coil”,

length

must

be

1,

and

data

00

(disable)

or

01

(enable).

In

case

of

“Write

Multiple

Coils”,

Length

is

the

number

of

coils,

and

data

must

be

n

byte

long,

with

n

=

(length

+

7)

/

8.

Data:

in

case

of

write

command,

data

to

be

write,

hexadecimal

values

formatted

as

string.

Alwaysuse

‘

(single

quote)

before

the

digits).

Baudrate

(bps):

serial

line

baudrate,only

needed

if

different

from

the

settings

in

LoRaWEB.

Allowedvalues:

1200,

2400,

4800,

9600,

19200.

38400,

57600,

115200.

Parity/stop:

serial

line

parity/stop,only

needed

if

different

from

the

settings

in

LoRaWEB.

Allowedvalues:

8-n-1,

8-n-2,

8-e-1,

8-

o

-1

for

none,

even

or

odd

Examples:

reading

a

2

byte

holding

register,

starting

from

address

10001

of

slave

1

Label

Input

status

1

3

10001

1

writing

a

2

byte

holding

register

(with

value

1000h),

starting

from

address

53

of

slave

2:

Label

Modbus

address

Modbus

function

Dec

address

Modbus

length

Data

Baudrate

(bps)

Parity/stop

Analog

output

1

2

4.2.4

Configuration

with

downlinks

Modbus

address

Modbus

function

Dec

address

Modbus

length

Data

Baudrate

(bps)

Parity/stop

6

53

1

1000

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

MODBUS

to

Downlink

converter:

convert

the

.XLS

configuration

file

in

one

or

more

downlink

payload

to

be

sent

to

the

device

instead

using

USB

port-.

Temporary

Downlink:

the

configuration

file

is

executed

and

then

discarded.

Configuration

Downlink:

the

configuration

file

is

saved

in

memory

and

executed

periodically.

4.3

Other

settings

Delay

for

reading

[ms]:

delay

added

between

the

reading

of

one

Modbus

register

and

the

one

(default

=

0).

DST:

set

to

change

DST

(default:

none).

Time

sync

uplink:

set

to

disable

time

synchronization

request

(default:

enabled).

Normally

sensor

asks

for

a

time

sync

at

every

power

on

(uplink

starting

with

01)

or

once

a

week.

If

no

or

wrong

reply

received,

it

will

retry

after

1

week.

If

not

handled

in

the

right

way

can

generate

unnecessary

traffic

on

the

network.

Please

check

chapter

2.1

.

Confirmed

Uplinks:

set

for

unconfirmed

uplinks

(default:

confirmed

uplink).

Single

join/day:

set

for

to

allow

only

one

join

per

day

(default:

multiple

join

allowed).

LED

working:

Set

OFF

to

turn

off

the

diagnostic

led.

USB:

Internal

use.

5.

Diagnostic

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

Press

Check

to

verify

the

correct

communication

betweet

the

LoRaWAN®

interface

and

the

slave(s).

6

LoRaWAN

network

The

sensor

is

compliant

with

LoRaWAN®

specification

1.0.2,

regional

1.0.2b.

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

6.1

Activation

The

device

supports

the

following

activations

on

a

LoRaWAN®

network:

1.

NONE:

sensor

not

activated

2.

OTAA:

the

JoinEUI

and

the

AppKey

not

setted,

must

be

written

to

the

device;

3.

OTAA

MCF88:

Over

the

air

activation,

fixed

keys:

JoinEUI

=

904e915000000002,

AppKey

on

request;

4.

OTAA

ENGINKO:

Over

the

air

activation,

fixed

keys:

JoinEUI

=

904e915000000002,

AppKey

on

request;

5.

ABP:

requires

writing

to

the

device

of

NwkSkey,

AppSkey,

DevAddr.

The

device

exits

factory

activated

with

NONE

mode.

On

request

devices

can

be

shipped

aleady

activated.

Note:

in

OTAA

AppKey

is

write

only,

in

reading

the

field

will

always

be

empty,

even

if

set.

6.2

Other

settings

Network

settings:

please

keep

“Any”

settings.

Change

it

only

if

Objenious

network

is

used

(default_

any).

Network

type:

LoRa

syncword

can

be

setted

as

“private”(0x12)

instead

“public”

(0x34),

butthe

NS

must

be

setted

accordingly(default:

public).

Band:

select

the

right

LoRaWAN

®

band

settings

accodingly

to

country

requirements.

7

Passwords

The

device

can

be

protected

by

passwords,

to

avoid

unauthorized

persons

to

read

data

or

modify

parameters.

As

default

passwords

are

equal

to

0.

m2m Germany GmbH | Am Kappengraben 18-20 | 61273 Wehrheim | 06081 5873860

Allowedvalues

range

from

0

to

999999999

(only

numbers).

To

change

the

passwords,

set

the

new

values

with

LoRaWEB:

Once

the

passwords

are

setted,

to

gain

access

from

LoRaWEB

to

the

sensor,

set

the

right

values

before

reading

from

the

device:

To

bring

back

the

sensor

to

factory

default

and

reset

the

passwords,

a

reset

code

must

be

requested

to

enginko

(please

provide

the

DevEUI

of

the

sensor

when

you

ask

for

that

code).

8

General

configuration

file

With

LoRaWEB

is

possible

to

configure

the

device

using

an

XML

file,

instead

to

manually

adjust

the

parameters

(for

details

about

the

file

format

please

ask

to

enginko).

This

is

very

useful

especially

in

case

of

multiple

devices

configuration.

With

“Save”

button

an

XML

file

with

the

actual

configuration

of

the

sensor

will

be

generated.

This

is

useful

to

store

or

clone

the

configuration,

or

to

send

it

to

enginko's

support

if

needed.

8.1

Multi

devices

configuration

WIth

LoRaWEB

is

possible

to

configure

many

devices

in

an

easy

way.

For

multi-configuration

is

needed

at

least

one

XML

file

with

the

parameters

to

set.

Settings

on

this

file

will

be

applied

to

all

the

sensors.

With

an

additional

XLS

file

is

possible

to

load

different

LoRa

configuration

parameters

(Activation

Type,

AppKey,

AppEUI,

NetKey,

DevAddress,

Band,

Private

option)

for

each

sensor,

based

on

DevEUI.

XLS

is

prevailing

on

the

XML,

so

if

both

files

are

enabled,

if

the

DevEUI

of

the

device

matches

one

of

the

DevEUIs

in

the

XLS

file,

LoRa

parameters

will

be

setted

M2M enginko MCF-LW06485 User manual

Popular Media Converter manuals by other brands