Jump to content

FlyingDoc

Members
  • Content Count

    456
  • Joined

  • Last visited

Community Reputation

0 Neutral

About FlyingDoc

  • Birthday 12/29/1968
  1. Neue Version getestet. Ergebnis. Hab den Angeschlossenen IMU nicht gesehen. War einzeln angesteckt und sonst nichts. Nach dem ich den Deamon neu gestartet habe war der IMU in der Liste zu sehen und hat funktioniert. Das Log ist aber nicht exorbitand geswachsen. 2019-12-20 22:40:17.187668 <I> <main_winapi.c:388> Brick Daemon 2.4.1+fd1 started (as service) 2019-12-20 22:40:17.189340 <W> <main_winapi.c:396> Warning(s) in config file 'C:\ProgramData\Tinkerforge\Brickd\brickd.ini', run with --check-config option for details 2019-12-20 22:40:19.465268 <I> <libusb:winusbx_init> libusbK DLL is not available, will use native WinUSB 2019-12-20 22:40:19.467268 <I> <libusb:windows_init> UsbDk backend is not available 2019-12-20 22:49:26.088046 <I> <usb.c:194> Added USB device (bus: 1, device: 6) at index 0: IMU Brick 2.0 [6wVmVp] 2019-12-20 22:49:27.245592 <I> <network.c:304> Added new client (N: 127.0.0.1:50029, T: plain-socket, H: 940/940, B: 0, P: 0, A: disabled) 2019-12-20 22:49:35.551313 <I> <client.c:252> Client (N: 127.0.0.1:50029, T: plain-socket, H: 940/940, B: 0, P: 0, A: disabled) disconnected by peer 2019-12-20 22:49:39.023099 <I> <usb.c:414> Removing USB device (bus: 1, device: 6) at index 0: IMU Brick 2.0 [6wVmVp] 2019-12-21 00:51:20.674954 <E> <event_winapi.c:268> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-21 00:51:20.675353 <E> <event.c:539> Event loop aborted 2019-12-21 00:51:20.676987 <I> <main_winapi.c:501> Brick Daemon 2.4.1+fd1 stopped 2019-12-21 23:07:30.674533 <I> <main_winapi.c:388> Brick Daemon 2.4.1+fd1 started (as service) 2019-12-21 23:07:30.675699 <W> <main_winapi.c:396> Warning(s) in config file 'C:\ProgramData\Tinkerforge\Brickd\brickd.ini', run with --check-config option for details 2019-12-21 23:07:30.686123 <I> <libusb:winusbx_init> libusbK DLL is not available, will use native WinUSB 2019-12-21 23:07:30.687530 <I> <libusb:windows_init> UsbDk backend is not available 2019-12-21 23:07:30.727582 <I> <usb.c:194> Added USB device (bus: 1, device: 6) at index 0: IMU Brick 2.0 [6wVmVp] 2019-12-21 23:07:34.647431 <I> <network.c:304> Added new client (N: 127.0.0.1:51074, T: plain-socket, H: 936/936, B: 0, P: 0, A: disabled) 2019-12-21 23:07:38.880840 <I> <client.c:252> Client (N: 127.0.0.1:51074, T: plain-socket, H: 936/936, B: 0, P: 0, A: disabled) disconnected by peer 2019-12-21 23:08:49.093330 <I> <network.c:304> Added new client (N: 127.0.0.1:51215, T: plain-socket, H: 952/952, B: 0, P: 0, A: disabled) 2019-12-21 23:08:57.386102 <I> <client.c:252> Client (N: 127.0.0.1:51215, T: plain-socket, H: 952/952, B: 0, P: 0, A: disabled) disconnected by peer 2019-12-22 00:06:13.795580 <I> <usb.c:414> Removing USB device (bus: 1, device: 6) at index 0: IMU Brick 2.0 [6wVmVp] 2019-12-22 02:07:39.397166 <E> <event_winapi.c:268> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-22 02:07:39.397829 <E> <event.c:539> Event loop aborted 2019-12-22 02:07:39.399960 <I> <main_winapi.c:501> Brick Daemon 2.4.1+fd1 stopped 2019-12-22 23:06:32.050797 <I> <main_winapi.c:388> Brick Daemon 2.4.1+fd1 started (as service) 2019-12-22 23:06:32.052312 <W> <main_winapi.c:396> Warning(s) in config file 'C:\ProgramData\Tinkerforge\Brickd\brickd.ini', run with --check-config option for details 2019-12-22 23:06:32.065926 <I> <libusb:winusbx_init> libusbK DLL is not available, will use native WinUSB 2019-12-22 23:06:32.067303 <I> <libusb:windows_init> UsbDk backend is not available 2019-12-22 23:06:32.106933 <I> <usb.c:194> Added USB device (bus: 1, device: 6) at index 0: IMU Brick 2.0 [6wVmVp] 2019-12-22 23:06:35.404747 <I> <network.c:304> Added new client (N: 127.0.0.1:53396, T: plain-socket, H: 948/948, B: 0, P: 0, A: disabled) 2019-12-22 23:07:22.462057 <I> <usb.c:414> Removing USB device (bus: 1, device: 6) at index 0: IMU Brick 2.0 [6wVmVp] 2019-12-22 23:08:19.440094 <I> <client.c:252> Client (N: 127.0.0.1:53396, T: plain-socket, H: 948/948, B: 0, P: 0, A: disabled) disconnected by peer 2019-12-23 21:06:26.097493 <E> <usb_winapi.c:119> Could not write to notification pipe: WSAECONNABORTED (71010053) 2019-12-23 21:06:26.100215 <E> <usb_winapi.c:119> Could not write to notification pipe: WSAECONNABORTED (71010053) 2019-12-23 21:06:58.502323 <I> <network.c:304> Added new client (N: 127.0.0.1:54934, T: plain-socket, H: 896/896, B: 0, P: 0, A: disabled) 2019-12-23 21:07:14.821635 <I> <client.c:252> Client (N: 127.0.0.1:54934, T: plain-socket, H: 896/896, B: 0, P: 0, A: disabled) disconnected by peer 2019-12-23 21:07:16.057508 <I> <network.c:304> Added new client (N: 127.0.0.1:54938, T: plain-socket, H: 952/952, B: 0, P: 0, A: disabled) 2019-12-23 21:07:20.838120 <I> <main_winapi.c:211> Received stop command 2019-12-23 21:07:26.060894 <I> <main_winapi.c:501> Brick Daemon 2.4.1+fd1 stopped 2019-12-23 21:24:48.974478 <I> <main_winapi.c:388> Brick Daemon 2.4.1+fd1 started (as service) 2019-12-23 21:24:48.975639 <W> <main_winapi.c:396> Warning(s) in config file 'C:\ProgramData\Tinkerforge\Brickd\brickd.ini', run with --check-config option for details 2019-12-23 21:24:48.991629 <I> <libusb:winusbx_init> libusbK DLL is not available, will use native WinUSB 2019-12-23 21:24:48.993204 <I> <libusb:windows_init> UsbDk backend is not available 2019-12-23 21:24:49.036225 <I> <usb.c:194> Added USB device (bus: 1, device: 6) at index 0: IMU Brick 2.0 [6wVmVp] 2019-12-23 21:24:49.185194 <I> <network.c:304> Added new client (N: 127.0.0.1:57447, T: plain-socket, H: 972/972, B: 0, P: 0, A: disabled) 2019-12-23 21:24:51.315636 <I> <client.c:252> Client (N: 127.0.0.1:57447, T: plain-socket, H: 972/972, B: 0, P: 0, A: disabled) disconnected by peer 2019-12-23 21:24:53.125924 <I> <network.c:304> Added new client (N: 127.0.0.1:57457, T: plain-socket, H: 984/984, B: 0, P: 0, A: disabled)
  2. Ich habe die Version getestet. Geht nicht. Innerhalb von ein paar Minuten war das Log von 0 auf 244 MB angestiegen. Ich habe mal die ständig kommenden Einträge minimiert. Es ist immer der selbe. Deswegen die Sternchen. 2019-12-16 22:38:06.442993 <I> <main_winapi.c:376> Brick Daemon 2.4.1 started (as service) 2019-12-16 22:38:06.444293 <W> <main_winapi.c:384> Warning(s) in config file 'C:\ProgramData\Tinkerforge\Brickd\brickd.ini', run with --check-config option for details 2019-12-16 22:38:06.460943 <I> <libusb:winusbx_init> libusbK DLL is not available, will use native WinUSB 2019-12-16 22:38:06.462639 <I> <libusb:windows_init> UsbDk backend is not available 2019-12-16 22:38:06.518538 <I> <usb.c:194> Added USB device (bus: 1, device: 6) at index 0: IMU Brick 2.0 [6wVmVp] 2019-12-16 22:38:11.020795 <I> <network.c:304> Added new client (N: 127.0.0.1:62490, T: plain-socket, H: 956/956, B: 0, P: 0, A: disabled) 2019-12-17 00:19:17.431758 <I> <client.c:252> Client (N: 127.0.0.1:62490, T: plain-socket, H: 956/956, B: 0, P: 0, A: disabled) disconnected by peer 2019-12-17 22:46:23.991284 <E> <event_winapi.c:228> Could not write to USB ready pipe: WSAECONNABORTED (71010053) 2019-12-17 22:47:26.695720 <I> <network.c:304> Added new client (N: 127.0.0.1:64583, T: plain-socket, H: 972/972, B: 0, P: 0, A: disabled) 2019-12-17 22:47:26.710409 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.710460 <E> <usb_transfer.c:300> Could not submit write transfer 017785A8 (handle: 0177C7B0, submission: 13) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:26.710524 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.710546 <E> <usb_transfer.c:300> Could not submit write transfer 017789C4 (handle: 0177C880, submission: 14) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:26.710618 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.710643 <E> <usb_transfer.c:300> Could not submit write transfer 01778DE0 (handle: 0177C950, submission: 15) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:26.710687 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.710706 <E> <usb_transfer.c:300> Could not submit write transfer 017791FC (handle: 0177CA20, submission: 16) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:26.710745 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.710763 <E> <usb_transfer.c:300> Could not submit write transfer 01779618 (handle: 0177CAF0, submission: 17) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:26.710801 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.710821 <E> <usb_transfer.c:300> Could not submit write transfer 01779A34 (handle: 0177CBC0, submission: 18) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:26.710856 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.710874 <E> <usb_transfer.c:300> Could not submit write transfer 01779E50 (handle: 0177CC90, submission: 19) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:26.710908 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.710926 <E> <usb_transfer.c:300> Could not submit write transfer 0177A26C (handle: 0177CD88, submission: 20) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:26.710965 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.710983 <E> <usb_transfer.c:300> Could not submit write transfer 0177A688 (handle: 0177D268, submission: 21) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:26.711043 <E> <libusb:winusbx_submit_bulk_transfer> ReadPipe/WritePipe failed: [22] Das Gerät erkennt den Befehl nicht. 2019-12-17 22:47:26.711076 <E> <usb_transfer.c:300> Could not submit write transfer 0177AAA4 (handle: 0177CF28, submission: 22) to IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_IO (-1) 2019-12-17 22:47:38.064350 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:47:38.064393 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:47:38.064411 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:47:38.064426 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:47:38.064440 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:47:38.064454 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:47:38.064468 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:47:38.064482 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) * * * * 2019-12-17 22:48:11.770978 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771162 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771193 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771212 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771226 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771240 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771254 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771268 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771282 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771296 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771301 <I> <main_winapi.c:209> Received stop command 2019-12-17 22:48:11.771310 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-12-17 22:48:11.771796 <W> <usb_transfer.c:208> Could not cancel pending read transfer 01773818 (handle: 01770CD0, submission: 12) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.771828 <W> <usb_transfer.c:243> Leaking pending read transfer 01773818 (handle: 01770CD0, submission: 12) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.771853 <W> <usb_transfer.c:208> Could not cancel pending read transfer 01773C34 (handle: 01770DA0, submission: 2) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.771870 <W> <usb_transfer.c:243> Leaking pending read transfer 01773C34 (handle: 01770DA0, submission: 2) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.771888 <W> <usb_transfer.c:208> Could not cancel pending read transfer 01774050 (handle: 01770E70, submission: 3) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.771913 <W> <usb_transfer.c:243> Leaking pending read transfer 01774050 (handle: 01770E70, submission: 3) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.771930 <W> <usb_transfer.c:208> Could not cancel pending read transfer 0177446C (handle: 01770F80, submission: 4) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.771954 <W> <usb_transfer.c:243> Leaking pending read transfer 0177446C (handle: 01770F80, submission: 4) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.771970 <W> <usb_transfer.c:208> Could not cancel pending read transfer 01774888 (handle: 017704A0, submission: 5) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.771980 <W> <usb_transfer.c:243> Leaking pending read transfer 01774888 (handle: 017704A0, submission: 5) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.771993 <W> <usb_transfer.c:208> Could not cancel pending read transfer 01774CA4 (handle: 01770570, submission: 6) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.772004 <W> <usb_transfer.c:243> Leaking pending read transfer 01774CA4 (handle: 01770570, submission: 6) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.772016 <W> <usb_transfer.c:208> Could not cancel pending read transfer 017750C0 (handle: 01777A20, submission: 7) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.772026 <W> <usb_transfer.c:243> Leaking pending read transfer 017750C0 (handle: 01777A20, submission: 7) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.772040 <W> <usb_transfer.c:208> Could not cancel pending read transfer 017754DC (handle: 01777B30, submission: 8) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.772052 <W> <usb_transfer.c:243> Leaking pending read transfer 017754DC (handle: 01777B30, submission: 8) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.772064 <W> <usb_transfer.c:208> Could not cancel pending read transfer 017758F8 (handle: 01777C40, submission: 9) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.772087 <W> <usb_transfer.c:243> Leaking pending read transfer 017758F8 (handle: 01777C40, submission: 9) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.772115 <W> <usb_transfer.c:208> Could not cancel pending read transfer 01775D14 (handle: 01778518, submission: 10) for IMU Brick 2.0 [6wVmVp]: LIBUSB_ERROR_NOT_FOUND (-5) 2019-12-17 22:48:11.772134 <W> <usb_transfer.c:243> Leaking pending read transfer 01775D14 (handle: 01778518, submission: 10) for IMU Brick 2.0 [6wVmVp] 2019-12-17 22:48:11.772454 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772476 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772488 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772498 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772509 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772519 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772530 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772539 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772550 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772574 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772584 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772594 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772604 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772614 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772625 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772635 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772646 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772656 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772666 <E> <libusb:do_close> Device handle closed while transfer was still being processed, but the device is still connected as far as we know 2019-12-17 22:48:11.772676 <W> <libusb:do_close> A cancellation for an in-flight transfer hasn't completed but closing the device handle 2019-12-17 22:48:11.772771 <W> <libusb:libusb_exit> some libusb_devices were leaked 2019-12-17 22:48:11.774399 <I> <main_winapi.c:489> Brick Daemon 2.4.1 stopped
  3. Hallo TF Team. Leider bringt der Deamon auch in der neuen Version noch das Problem das er beim ersten Start nicht funktioniert , aber dafür mir die Festplatte mit dem Logfile zuspammt. Vorgestern Abend installiert. Und innerhalb von 4h über 8 GB an Logfile produziert. Wolltet ihr nicht die maximale Anzahl der Einträge limitieren?
  4. Ädendschen Ädendschen. Dis is e new Deschd.
  5. Der erste Versuch und ein Volltreffer. Mit sc config "Brick Daemon" depend=tcpip funktioniert es.
  6. Hallo TF Team. Ich wollte es schon ewig melden, habe es aber lange verpasst, da ich arbeitsmäßig und familiär ziemlich gebunden bin im Moment. Bei meinem Laptop habe ich folgendes Phänomen. Beim Start von Win 10 kann der Daemon keine Verbindung aufbauen. Ich habe heute mal in die Log geschaut warum und habe folgendes gefunden. 2019-08-22 21:51:08.044366 <E> <event_winapi.c:228> Could not write to USB ready pipe: WSAECONNABORTED (71010053) 2019-08-22 21:52:09.341898 <I> <log_winapi.c:173> Log Viewer connected to info pipe 2019-08-22 21:52:23.436638 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) Die Verbindung funktioniert erst, wenn ich den Daemon Dienst neu starte. 2019-08-22 21:53:48.196921 <I> <main_winapi.c:209> Received stop command 2019-08-22 21:53:48.196922 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-08-22 21:53:48.197252 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-08-22 21:53:48.197274 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-08-22 21:53:48.197308 <E> <event_winapi.c:261> Could not read from USB ready pipe: WSAECONNRESET (71010054) 2019-08-22 21:53:48.200701 <I> <main_winapi.c:489> Brick Daemon 2.4.0 stopped 2019-08-22 21:53:49.534941 <I> <main_winapi.c:376> Brick Daemon 2.4.0 started (as service) 2019-08-22 21:53:49.555603 <I> <libusb:winusbx_init> libusbK DLL is not available, will use native WinUSB 2019-08-22 21:53:49.556743 <I> <libusb:windows_init> UsbDk backend is not available 2019-08-22 21:53:49.596024 <I> <usb.c:194> Added USB device (bus: 1, device: 4) at index 0: IMU Brick 2.0 [6wVmVp] 2019-08-22 21:53:49.941343 <I> <log_winapi.c:173> Log Viewer connected to info pipe Ich vermute mal, das mein Rechner einfach zu schnell startet und etwas noch nicht geladen ist was der Daemon beim USB benötigt. Vom Start bis zum Login Screen sind es rund 10 Sekunden. Vielleicht kann man das Problem ja beheben in dem man vor dem Verbindungsversuch testet ob die benötigte Treiberkomponente schon im Windows geladen ist. P.s. Könntet iht die Länge des Logfile begrenzen. Mir hat der Daemon meine Platte mit dem Logfile völlig vollgeschrieben. Also alles wenn eine bestimmte Größe erreicht ist die ältesten Beiträge abschneiden. Das waren dann mehrere GByte. ( Kein Scherz) Und da hatte ich nur eine 256 GByte Systemplatte. Jetzt 1 TByte. Er Protokolliert ja alles. Und wenn jede Sekunde ein Fehlereintrag kommt geht das ratz fatz. Ich habe mich gewundert warum meine Systemplatte irgend wann bis auf das letzte Byte gefüllt war. Da schliesst man ja nicht sofort drauf.
  7. Erstens muß die Ethernet Extension direkt auf den Red Brick. Zweitens findest du die Extension dann nicht in dieser Liste , sondern direkt beim Red Brick Reiter unter Settings im Reiter Network.
  8. Nein. Du kannst mehrere gleichzeitig verbinden. Alle Clienten erhalten dann auch das gleiche Callback wenn es configuriert ist.
  9. WIelange hast du denn gewartet. Es dauert wirklich eine gefühlte Ewigkeit bis es durch ist.
  10. Das das Feld auf Disconnect wechselt hat noch nichts mit der Verbindung zum RED zu tun. Das bedeutet einfach nur das du zum lokalem Brickdemaon Verbindung hast. So. Weiter. 1. Hast du im Red schon die SD Karte mit dem IMG ( also quasi die Festplatte mit Betriebssystem) 2. Wenn der RED an ist, müsste die Grüne LED auf dem RED blinken. Das zeigt an das dir Deamon auf dem RED läuft. Sonst siehst du ihn nicht im Brick Viewer! Auch wenn der RED läuft.
  11. Ich habe wie du empfohlen hast den 2.3.0 installiert. Jetzt funktioneren die Callback wieder. Danke.
  12. Ich arbeite gerade an beiden Varianten. Mit neuem Image (da muß ich aber noch viel anpassen) und mit dem Versuch den Daemon zu aktualisieren. Dabei kommt folgender Fehler. Ich habe den Daemon nach eurer Anleitung mit aktualisisert. Der Daemon startet aber wie schon beschrieben nicht.
  13. So. Nach dem ich Zeit zum Testen hab, die Italiener haben gerade bei uns das gesamte Netzwerk im Betrieb geändert, habe ich festgestellt, das es an der RED Img Version liegt. Beim 1.8er gehen die Callback nicht.
  14. Habe gerade festgestellt , das wenn ich das Bricklet an einen einzelnen Master stecke, geht alles. Da muss ich den Stapel mal auseinander nehmen und einzeln testen.
×
×
  • Create New...