evcc-io / evcc

Sonne tanken ☀️🚘
https://evcc.io
MIT License
3.4k stars 620 forks source link

Garo Wallbox- Error "[lp-1 ] ERROR charge timer: modbus: length in response header '12081' must not be zero or greater than '254'" #13335

Closed m03pchen closed 5 months ago

m03pchen commented 6 months ago

Describe the bug

Hello everyone,

I have a Garo wallbox ((GLBDCMW-T211FC-VCC) connected to my homeassistant via wifi. The garo_wallbox addon is running on the homeassistant and also displays all values. I can also access the wallbox's web interface via the local IP, change the mode (on/off) and an other things (like loadpower 6-16 ampere)

After the 3 Minute start this error pops into thelog:

"[lp-1 ] ERROR charge timer: modbus: length in response header '12081' must not be zero or greater than '254'"

The error comes every minute again. No wallbox is displayed under the device settings - only the Volvo. On the overview page, however, the Volvo is always shown as "not connected" even if the charging cable is connected and I start the wallbox via Home Assistant or web interface.

Config from http://wallbox-ip:8080/servlet/rest/chargebox/config

{
"ocppConnected": false,
"maxChargeCurrent": 16,
"productId": "119",
"programVersion": "8.4",
"firmwareVersion": 8,
"firmwareRevision": 4,
"lbVersion2": true,
"serialNumber": 2180591,
"meterSerialNumber": "122145V",
"meterType": 341,
"factoryChargeLimit": 32,
"switchChargeLimit": 16,
"rfidReaderPresent": false,
"rfidMode": "RFID_DISABLED",
"powerbackupStatus": 2,
"lastTemperature": 29,
"warningTemperature": 59,
"cutoffTemperature": 64,
"reducedIntervalsEnabled": false,
"reducedCurrentIntervals": [],
"softwareVersion": 189,
"availableVersion": 0,
"updateUrl": "",
"networkMode": 1,
"networkType": 0,
"networkSSID": "WIFIname",
"webNetworkPassword": "",
"networkAPChannel": 6,
"ethNetworkMode": 0,
"gcConfigTimestamp": null,
"gcloudActivated": false,
"gcActivatedFrom": null,
"ethGateway": "",
"ethDNS": "",
"ethIP": "",
"ethMask": 24,
"localLoadBalanced": false,
"groupLoadBalanced": false,
"groupLoadBalanced101": false,
"energyReportEnabled": false,
"master": true,
"timezone": null,
"slaveList": [
{
"reference": "Name-Wallbox",
"serialNumber": 2180591,
"lastContact": 1644515054363,
"online": false,
"loadBalanced": false,
"phase": 4,
"productId": 132,
"meterStatus": 0,
"meterSerial": "122145V",
"chargeStatus": 48,
"pilotLevel": 16,
"accEnergy": 9200,
"firmwareVersion": 8,
"firmwareRevision": 4,
"wifiCardStatus": 2,
"connector": "DISABLED",
"accSessionEnergy": 0,
"sessionStartValue": 9200,
"accSessionMillis": 0,
"sessionStartTime": 1644506881670,
"currentChargingCurrent": 0,
"currentChargingPower": 0,
"nrOfPhases": 1,
"twinSerial": -1,
"cableLockMode": 1,
"minCurrentLimit": 6,
"dipSwitchSettings": 8092,
"cpuType": 2004993,
"updateable": false
}
],
"gridNetType": "TN",
"slaveControlAvailable": true,
"currentMultiplier": 100,
"rfPower": 31,
"twinSerial": -1,
"twinSwitchLimit": 0,
"energySerials": [
"2180591"
],
"packageVersion": "1.3.7",
"cableAutoUnlocked": false,
"internetSharingEnabled": false,
"webAPPassword": null,
"standalone": true,
"castra": false,
"cpuType": 2004993
}

chargepoint GridPVBattery

Steps to reproduce

I dont know...

Configuration details

network:
  # schema is the HTTP schema
  # setting to `https` does not enable https, it only changes the way URLs are generated
  schema: http
  # host is the hostname or IP address
  # if the host name contains a `.local` suffix, the name will be announced on MDNS
  # docker: MDNS announcements don't work. host must be set to the docker host's name.
  host: 192.168.178.101
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 20s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval

# database configuration for persisting charge sessions and settings
# database:
#   type: sqlite
#   dsn: <path-to-db-file>

# sponsor token enables optional features (request at https://sponsor.evcc.io)
sponsortoken: ***************

# telemetry enables aggregated statistics
#
# Telemetry allows collecting usage data (grid and green energy, charge power).
# Data is aggregated, no individual charging sessions are tracked. The collected,
# anonymous data can be retrieved using https://api.evcc.io.
#
# See https://github.com/evcc-io/evcc/pull/4343 or details.
#
# For time being, this is only available to sponsors, hence data is associated with
# the sponsor token's identity.
#
# telemetry: true

# log settings
log: info
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  cache: error
  db: error

# modbus proxy for allowing external programs to reuse the evcc modbus connection
# each entry will start a proxy instance at the given port speaking Modbus TCP and
# relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP)
modbusproxy:
  #  - port: 5200
  #    uri: solar-edge:502
  #    # rtu: true
  #    # readonly: true # use `deny` to raise modbus errors

# meter definitions
# name can be freely chosen and is used as reference when assigning meters to site and loadpoints
# for documentation see https://docs.evcc.io/docs/devices/meters
meters:
  - name: Home
    type: template
    template: sungrow-hybrid
    usage: grid

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: *.*.*.* # Hostname
    port: 502 # Port
    timeout: 10s # optional

  - name: PV
    type: template
    template: sungrow-hybrid
    usage: pv

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: *.*.*.* # Hostname
    port: 502 # Port
    timeout: 10s # optional 

  - name: Batterie
    type: template
    template: sungrow-hybrid
    usage: battery

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: *.*.*.* # Hostname
    port: 502 # Port
    timeout: 10s # optional 

# charger definitions
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for documentation see https://docs.evcc.io/docs/devices/chargers
chargers:
  - name: Garo-Wallbox
    type: template
    template: bender
    host: *.*.*.* # IP-Adresse oder Hostname
    port: 8080 # Port (optional) 

# vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for documentation see https://docs.evcc.io/docs/devices/vehicles
vehicles:
  - name: VolvoV60
    type: template
    template: volvo-connected
    title: VolvoV60 # Wird in der Benutzeroberfläche angezeigt (optional)
    user: ***** # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: ***** # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    vin: ***** # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (optional)
    capacity: 18 # Akkukapazität in kWh (optional)
    vccapikey: ***** # Volvo developer portal VCC API Key, siehe https://github.com/evcc-io/evcc/discussions/3677#discussioncomment-4106300

# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
    grid: Home # grid meter
    pv:
      - PV # list of pv inverters/ meters
    battery:
      - Batterie # list of battery meters
  residualPower: 100 # additional household usage margin
  maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Wallbox # display name for UI
    charger: Garo-Wallbox # charger
    vehicle: VolvoV60
    mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available

    # remaining settings are experts-only and best left at default values
    priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
    soc:
      # polling defines usage of the vehicle APIs
      # Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery
      # or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.
      poll:
        # poll mode defines under which condition the vehicle API is called:
        #   charging: update vehicle ONLY when charging (this is the recommended default)
        #   connected: update vehicle when connected (not only charging), interval defines how often
        #   always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
        mode: connected
        # poll interval defines how often the vehicle API may be polled if NOT charging
        interval: 5m
      estimate: true # set false to disable interpolating between api updates (not recommended)
    enable: # pv mode enable behavior
      delay: 1m # threshold must be exceeded for this long
      threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
    disable: # pv mode disable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)

# tariffs are the fixed or variable tariffs
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type: fixed
    price: 0.265 # EUR/kWh

    # or variable tariffs
    # type: tibber
    # token: "*****" # access token
    # homeid: "*****" # optional if multiple homes associated to account

    # type: awattar
    # region: de # optional, choose at for Austria
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional

    # type: elering # Nordpool
    # region: ee # or lt, lv, fi
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: energinet # Energinet using the price in DKK
    # region: dk1 # or dk2
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: entsoe # Entso-E european market data
    # domain: BZN|DE-LU # https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas
    # securitytoken: # api token
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: pun # PUN - Prezzo unico nazionale - Hourly Italian wholesale prices
    # charges: 0 # optional, additional charges per kWh
    # tax: 0 # optional, additional tax (0.1 for 10%)

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: general

    # type: custom # price from a plugin source; see https://docs.evcc.io/docs/reference/plugins
    # price:
    #   source: http
    #   uri: https://example.org/price.json
    #   jq: .price.current

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.08 # EUR/kWh

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: feedIn
  co2:
    # co2 tariff provides co2 intensity forecast and is for co2-optimized target charging if no variable grid tariff is specified
    # type: grünstromindex # GrünStromIndex (Germany only)
    # zip: <zip>

    # type: electricitymaps # https://app.electricitymaps.com/map
    # uri: <uri>
    # token: <token> # needs to be a token with forecast (not in the free tier)
    # zone: DE

    # type: ngeso # National Grid Electricity System Operator data (Great Britain only) https://carbonintensity.org.uk/
    # provides national data if both region and postcode are omitted - Choose ONE only!
    # region: 1 # optional, coarser than using a postcode - The region details are at https://carbon-intensity.github.io/api-definitions/#region-list
    # postcode: SW1 # optional - Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only

# mqtt message broker
mqtt:
  # broker: localhost:1883
  # topic: evcc # root topic for publishing, set empty to disable
  # user:
  # password:

# influx database
influx:
  # url: http://localhost:8086
  # database: evcc
  # user:
  # password:

# eebus credentials
eebus:
  # uri: # :4712
  # interfaces: # limit eebus to specific network interfaces
  # - en0
  # certificate: # local signed certificate, required, can be generated via `evcc eebus-cert`
  #   public: # public key
  #   private: # private key

# push messages
messaging:
  events:
    start: # charge start event
      title: Charge started
      msg: Started charging in "${mode}" mode
    stop: # charge stop event
      title: Charge finished
      msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
    connect: # vehicle connect event
      title: Car connected
      msg: "Car connected at ${pvPower:%.1fk}kW PV"
    disconnect: # vehicle connected event
      title: Car disconnected
      msg: Car disconnected after ${connectedDuration}
    soc: # vehicle soc update event
      title: Soc updated
      msg: Battery charged to ${vehicleSoc:%.0f}%
    guest: # vehicle could not be identified
      title: Unknown vehicle
      msg: Unknown vehicle, guest connected?
  services:
  # - type: pushover
  #   app: # app id
  #   recipients:
  #   - # list of recipient ids
  # - type: telegram
  #   token: # bot id
  #   chats:
  #   - # list of chat ids
  # - type: email
  #   uri: smtp://<user>:<password>@<host>:<port>/?fromAddress=<from>&toAddresses=<to>
  # - type: ntfy
  #   uri: https://<host>/<topics>
  #   priority: <priority>
  #   tags: <tags>

Log details

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2024/04/07 21:20:38 evcc 0.125.0
[main  ] INFO 2024/04/07 21:20:38 using config file: /config/evcc.yaml
[main  ] INFO 2024/04/07 21:20:38 starting ui and api at :7070
[lp-1  ] WARN 2024/04/07 21:23:39 poll mode '{connected 5m0s}' may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
[site  ] INFO 2024/04/07 21:23:39 site config:
[site  ] INFO 2024/04/07 21:23:39   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2024/04/07 21:23:39     grid:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/04/07 21:23:39     pv 1:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/04/07 21:23:39     battery 1: power ✓ energy ✓ currents ✗ soc ✓ capacity ✗
[site  ] INFO 2024/04/07 21:23:39   vehicles:
[site  ] INFO 2024/04/07 21:23:39     vehicle 1: range ✓ finish ✓ status ✓ climate ✗ wakeup ✗
[lp-1  ] INFO 2024/04/07 21:23:39 loadpoint 1:
[lp-1  ] INFO 2024/04/07 21:23:39   mode:        off
[lp-1  ] INFO 2024/04/07 21:23:39   charger:     power ✗ energy ✗ currents ✗ phases ✗ wakeup ✗
[lp-1  ] INFO 2024/04/07 21:23:39   meters:      charge ✗
[lp-1  ] DEBUG 2024/04/07 21:23:39 phase timer inactive
[lp-1  ] DEBUG 2024/04/07 21:23:39 pv timer inactive
[lp-1  ] INFO 2024/04/07 21:23:39 vehicle updated: unknown -> VolvoV60
[lp-1  ] ERROR 2024/04/07 21:24:39 charger enabled: modbus: length in response header '12081' must not be zero or greater than '254'
[site  ] WARN 2024/04/07 21:24:39 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
[site  ] DEBUG 2024/04/07 21:24:39 ----
[lp-1  ] DEBUG 2024/04/07 21:24:39 charge power: 0W
[site  ] DEBUG 2024/04/07 21:24:39 pv power: 0W
[site  ] DEBUG 2024/04/07 21:24:39 battery soc: 76%
[site  ] DEBUG 2024/04/07 21:24:39 battery power: 512W
[site  ] DEBUG 2024/04/07 21:24:39 grid meter: 1W
[site  ] DEBUG 2024/04/07 21:24:39 site power: 613W

What type of operating system are you running?

Linux

Version

0.125.0

andig commented 6 months ago

Try having only one system talking to the box.

m03pchen commented 6 months ago

Try having only one system talking to the box.

I tried it today. I deactivated the Garo add-on and completely restarted Homeassistant (Power shutdown) Then I started HA with EVCC only - log looks exactly the same. 3 minutes until EVCC is completely started and one minute later the modbus: length error appears

andig commented 6 months ago

@premultiply es geht um Bender- da musst Du mal bitte schauen.

premultiply commented 6 months ago

Was sagt denn evcc charger --log trace --diagnose?

m03pchen commented 5 months ago

Was sagt denn evcc charger --log trace --diagnose?

Sorry aber wo genau gebe ich den Befehl ein ? Bei mir läuft HA auf Proxmox - glaube da komme ich nicht in die Console dafür oder?

premultiply commented 5 months ago

Einfach auf einem normalen System Windows, macOS, Linux etc. in der Konsole ausführen. evcc ist eine einzelne ausführbare Datei.

m03pchen commented 5 months ago

Ehrlich gesagt komme ich so nicht weiter. Habe gerade mal versucht EVCC über Windows zu konfigurieren, PV Anlage und Fahrzeug klappt. Bei der Wallbox kommt folgendes (gleiches):

"Teste die Konfiguration von Garo GLB, GLB+, LS4, LS4 compact ... Fehler: modbus: length in response header '12081' must not be zero or greater than '254'

Der Test von Garo GLB, GLB+, LS4, LS4 compact ist fehlgeschlagen. Soll es trotzdem in die Konfiguration aufgenommen werden? Yes

Garo GLB, GLB+, LS4, LS4 compact Garo GLB, GLB+, LS4, LS4 compact wurde erfolgreich hinzugefügt."

Ich habe dann aus Unwissenheit deinen Befehl eingegeben:

C:\Download\evcc>evcc charger --log trace --diagnose [main ] INFO 2024/04/09 20:28:51 evcc 0.125.0 [main ] INFO 2024/04/09 20:28:51 using config file: C:\Download\evcc\evcc.yaml [db ] INFO 2024/04/09 20:28:51 using sqlite database: C:\Users****.evcc\evcc.db [db ] TRACE 2024/04/09 20:28:51 SELECT count() FROM sqlite_master WHERE type='table' AND name="settings" -1 [db ] TRACE 2024/04/09 20:28:51 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "settings" AND sql IS NOT NULL order by type = "table" desc 1 [db ] TRACE 2024/04/09 20:28:51 SELECT FROM settings LIMIT 1 -1 [db ] TRACE 2024/04/09 20:28:51 SELECT FROM settings 0 [db ] TRACE 2024/04/09 20:28:51 SELECT count() FROM sqlite_master WHERE type='table' AND name="device_details" -1 [db ] TRACE 2024/04/09 20:28:51 SELECT count() FROM sqlite_master WHERE type='table' AND name="devices" -1 [db ] TRACE 2024/04/09 20:28:51 SELECT count() FROM sqlite_master WHERE type='table' AND name="configs" -1 [db ] TRACE 2024/04/09 20:28:51 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "configs" AND sql IS NOT NULL order by type = "table" desc 1 [db ] TRACE 2024/04/09 20:28:51 SELECT FROM configs LIMIT 1 -1 [db ] TRACE 2024/04/09 20:28:51 SELECT count() FROM sqlite_master WHERE type='table' AND name="config_details" -1 [db ] TRACE 2024/04/09 20:28:51 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "config_details" AND sql IS NOT NULL order by type = "table" desc 2 [db ] TRACE 2024/04/09 20:28:51 SELECT FROM config_details LIMIT 1 -1 [db ] TRACE 2024/04/09 20:28:51 SELECT count() FROM sqlite_master WHERE type = "table" AND tbl_name = "config_details" AND (sql LIKE "%CONSTRAINT ""fk_configs_details"" %" OR sql LIKE "%CONSTRAINT fk_configs_details %" OR sql LIKE "%CONSTRAINT fk_configs_details%" OR sql LIKE "%CONSTRAINT [fk_configs_details]%" OR sql LIKE "%CONSTRAINT fk_configs_details %") -1 [db ] TRACE 2024/04/09 20:28:51 SELECT count() FROM sqlite_master WHERE type = "index" AND tbl_name = "config_details" AND name = "idx_unique" -1 [db ] TRACE 2024/04/09 20:28:51 SELECT count() FROM sqlite_master WHERE type = "table" AND tbl_name = "config_details" AND (sql LIKE "%CONSTRAINT ""fk_devices_details"" %" OR sql LIKE "%CONSTRAINT fk_devices_details %" OR sql LIKE "%CONSTRAINT fk_devices_details%" OR sql LIKE "%CONSTRAINT [fk_devices_details]%" OR sql LIKE "%CONSTRAINT fk_devices_details %") -1 [db ] TRACE 2024/04/09 20:28:51 SELECT count() FROM sqlite_master WHERE type = "table" AND tbl_name = "config_details" AND (sql LIKE "%""device_id"" %" OR sql LIKE "%device_id %" OR sql LIKE "%device_id%" OR sql LIKE "%[device_id]%" OR sql LIKE "% device_id %") -1 [db ] TRACE 2024/04/09 20:28:51 SELECT * FROM configs WHERE configs.class = 1 ORDER BY id 0

Ansonsten bin ich mit meinem Können ohne Anleitung leider am Ende

premultiply commented 5 months ago
chargers:
  - name: Garo-Wallbox
    type: template
    template: bender
    host: *.*.*.* # IP-Adresse oder Hostname
    port: 8080

Port 8080 klingt falsch. Was passt am Default 502 nicht?

m03pchen commented 5 months ago

Habe mal den Port 8080 gegen 502 ausgetauscht:

[main ] INFO 2024/04/09 21:11:51 evcc 0.125.0 [main ] INFO 2024/04/09 21:11:51 using config file: /config/evcc.yaml [main ] INFO 2024/04/09 21:11:51 starting ui and api at :7070 [lp-1 ] WARN 2024/04/09 21:11:52 poll mode '{connected 5m0s}' may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK. [site ] INFO 2024/04/09 21:11:52 site config: [site ] INFO 2024/04/09 21:11:52 meters: grid ✓ pv ✓ battery ✓ [site ] INFO 2024/04/09 21:11:52 grid: power ✓ energy ✓ currents ✗ [site ] INFO 2024/04/09 21:11:52 pv 1: power ✓ energy ✓ currents ✗ [site ] INFO 2024/04/09 21:11:52 battery 1: power ✓ energy ✓ currents ✗ soc ✓ capacity ✗ [site ] INFO 2024/04/09 21:11:52 vehicles: [site ] INFO 2024/04/09 21:11:52 vehicle 1: range ✓ finish ✓ status ✓ climate ✗ wakeup ✗ [lp-1 ] INFO 2024/04/09 21:11:52 loadpoint 1: [lp-1 ] INFO 2024/04/09 21:11:52 mode: off [lp-1 ] INFO 2024/04/09 21:11:52 charger: power ✗ energy ✗ currents ✗ phases ✗ wakeup ✗ [lp-1 ] INFO 2024/04/09 21:11:52 meters: charge ✗ [lp-1 ] DEBUG 2024/04/09 21:11:52 phase timer inactive [lp-1 ] DEBUG 2024/04/09 21:11:52 pv timer inactive [lp-1 ] INFO 2024/04/09 21:11:52 vehicle updated: unknown -> VolvoV60 [lp-1 ] ERROR 2024/04/09 21:11:52 charger enabled: dial tcp 192.168.178.10:502: connect: connection refused

premultiply commented 5 months ago

https://docs.evcc.io/docs/devices/chargers#garo-glb-glb-ls4-ls4-compact

Der 'Modbus TCP Server für Energiemanagement-Systeme' muss aktiviert sein. 'Registersatz' darf NICHT auf 'Phoenix' oder 'TQ-DM100' eingestellt sein. Die dritte Auswahlmöglichkeit 'Ebee', 'Bender', 'MENNEKES' etc. ist richtig. 'UID Übertragung erlauben' muss aktiviert sein.

Ist das alles gegeben?