Jump to content

wengzh

Members
  • Gesamte Inhalte

    5
  • Benutzer seit

  • Letzter Besuch

wengzh's Achievements

Newbie

Newbie (1/14)

0

Reputation in der Community

  1. Thank you very much for the update! I've checked my wifi status, and there seems to be an issue with my Client mode connection (Please see attached image). The signal strength is very different from yours. I then set the connection mode to Access Point only, and the data logging error disappears. We might need to build a network of sensors in a large number of rooms and send data using a WIFI mesh or an alternative option to a database server, would the issue with the Client mode be a problem in this case?
  2. Thank you very much. Looking forward to discussing further after your test.
  3. Thank you for the advice and I am now powering the stack with a power plug. Please see attached image on the set-up. However the error remains as the same as my previous set-up.
  4. Thank you very much for getting back to me. I am using the Brick Viewer at the moment, and the Brick logger for logging the data. Please find attached another datasheet where the data were set to be logged every 10 milisecond, and this error can occur multiple times in one second. P.S. I use a USB cable connecting to another PC to power the stack (1 x Master Brick + 1 WIFI Extension 2.0 + 1 Humidity 2.0), would that cause any problem? logger_data_WIFI_per_10_ms.csv
  5. I am using "1 x Master brick + 1 x WIFI extension 2.0 + 1 x humidity 2.0 sensor" to collect environmental data in a research project pilot study. They all connect properly and I can see real-time data being updated on the Brick Viewer interface. However When I try to log the data into a csv file, the following error always occurs repeatedly: "Did not receive response for function *... in time (-1)" I have tried different time-steps (from 10 miliseconds to 5 seconds), and on different PCs and MACs, and the same error remains. If I am connecting the Master Brick directly with a USB, then the error disapears, so presumably this error is caused by unstable data-exchange with the WIFI extension? Any insight on this error would be very much appreciated! logger_data_WIFI.csv
×
×
  • Neu erstellen...