Issue: sensorconnect not going to historian
# umh-support
t
Issue: sensorconnect not going to my historian....?
j
did you opened in an old tab? if yes, refresh teh tab to get the new frontend changes
to fix the sensorconnect disappeared in the protocol
t
ugh...i swear I was using the same tab as earlier to set it up...refresh fixed that...
j
@Ferdinand
t
I just used the default everything....didn't change the input config, or the processor config....I am getting it in the tag browser.
Copy code
{
  "Detection_instability_alarm": false,
  "Distance_error": false,
  "Error": false,
  "Insufficient_incident_light_level_error": false,
  "Monitor_output_1__Detection_level_": 161,
  "Monitor_output_2__Incident_light_level_": 14,
  "Output1": true,
  "Output2": false,
  "Warning": false,
  "metadata": {
    "sensorconnect_device_product_code": "AL1340",
    "sensorconnect_device_serial_number": "000220918159",
    "sensorconnect_device_url": "http://192.168.100.32:80",
    "sensorconnect_port_iolink_device_id": "65578",
    "sensorconnect_port_iolink_product_name": "E3AS-F1000IPD",
    "sensorconnect_port_iolink_serial": "11003C28",
    "sensorconnect_port_iolink_vendor_id": "612",
    "sensorconnect_port_mode": "io-link",
    "sensorconnect_port_number": "2"
  },
  "timestamp_ms": 1729865405733
}
f
Does the asset exists for that tag ?
t
Yep
j
Let us check on Monday together what is happening there. On Monday there will also be the new bridges, which will tell you if insertion of something failed 🙂