Jump to content

fridolin11

Members
  • Posts

    15
  • Joined

  • Last visited

About fridolin11

  • Birthday 02/12/1995

fridolin11's Achievements

Rookie

Rookie (2/14)

  • Collaborator Rare
  • One Year In
  • One Month Later
  • Week One Done
  • First Post

Recent Badges

0

Reputation

  1. Ich habe nun alle meine Servo drives angeschlossen und mir sind dabei folgende Dinge aufgefallen: Nach ca. 42 Drives wurde die Modbus Verbindung unzuverlässig und ich vermute dass dies der maximalen Slave Anzahl für mein Setup entspricht. Ich verwende nun drei separate RS485 Bricklets mit 2x 35 und 1x 28 Slaves und das funktioniert tiptop. Ich habe mich hier gegen einen Modbus Repeater entschieden, da ich gerade genügend RS485 Bricklets zur Verfügung hatte ;) Alle drei Modbus Systeme sind nur am einen Ende mit dem Master mit 120 Ohm Terminiert. Sobald ich das andere Ende ebenfalls terminiert habe, wurde die Übertragung unzuverlässig bei vielen Slaves. Die Maschine wurde wie folgt programmiert: Während die Maschine läuft frage ich beginnend bei Slave 1 dessen Drehgeschwindigkeit ab ("modbus_master_read_holding_registers"), und gebe ihm dann entsprechend ein Moment vor, mit dem der Servo bremsen soll ("modbus_master_write_single_register"). Danach wiederhole ich diesen Vorgang für den nächsten Slave usw. bis zu Slave Nummer 98, und beginne den Prozess dann wieder von vorne. Für eine gesamte Schleife benötige ich ca. 8 Sekunden und am meisten Zeit verliere ich dadurch, dass ich zwischen dem "read" und dem "write" Befehl einen Delay von 60 ms einbauen musste, da ich sonst ein Timeout bekomme. Ist das eine Übliche Übertragungsrate für Modbus? Die Baudrate beträgt 19200 bps. Für meine Anwendung passt das so aber ich hatte erwartet dass es ein bisschen schneller laufen würde. Es kann allerdings auch gut daran liegen, dass meine Software zu langsam ist. Das Programm läuft auf Node-Red und die Bricklets werden über MQTT angesteuert.
  2. No the cable doesn't have any ferrit cores on the ends and the same problem occured with different cables on different ports. What completely solved my issue was unplugging the power to the step-down brick from my second masterbrick stack (the one that caused trouble). So the components are powered like this: 24V 60W PSU -> Step-Down PSU and Stack 1 -> 5V Output from Step-Down powers my Raspberry Pi over USB-C -> Second Stack is powered by the Raspberry Pi over the USB Cable and no longer from its own dedicated PSU Maybe a slight difference in the voltage ouput from the different PSUs caused the problem instead of interference in the cable? Either way, my Problem is solved and all the components work fine :) Thank you so much for your inputs!
  3. Dear photron Thank you so much for your reply! I just checked ther version of brickd: 2.4.5 The live view was very helpful, and I was able to identify the problem. The stack which is directly next to my raspberry works fine all the time. The other stack, which is connected over a 1.5 m long usb cable causes the stall condition messages. They only occur though once I turn on some larger loads with the industrial relay bricklets. I routed all the signal cables seperately from the power lines but the noise occures nonetheless. Regarding the powersupply of the raspberry: Both stacks have a Tinkerforge Step-Down PSU which are powered by two 24V 60W PSUs. The raspberry is connected over the usb-c port to the 5V output from one of the Step-Down PSUs The output from the Step-Down Bricks is rated for 5V 3A, which matches the PSU which Raspberry recommends The bricks are directly connected to the Raspberry Pi and I currently don't have a powered USB-hub to test out other possible connections I most definitely will just remove the second seperate stack and will just include all of the bricklets into the first stack. Instead of an USB cable I will then have the cables from the bricklets routed over the 1.5 m. Most of those cables are not subsceptible to noise except for maybe one RS485 connection. I will have to test that tough.
  4. I just found the log files. This is what shows up when I try to connect over brickv: 2024-02-26 16:22:36.039557 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:36.039807 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:36.039912 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:36.040000 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:36.040650 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:22:38.838728 <I> <network.c:304> Added new client (N: 127.0.0.1:43914, T: plain-socket, H: 20/20, B: 0, P: 0, A: disabled) 2024-02-26 16:22:39.977974 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:39.978205 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 8185) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:39.980536 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:22:44.588868 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8290) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:44.589047 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 8288) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:44.590777 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:22:46.513998 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:46.515795 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:22:54.639888 <I> <usb.c:506> Removing USB device (bus: 1, device: 19) at index 1: Master Brick [6kLrqd] 2024-02-26 16:22:54.998130 <I> <usb.c:273> Added USB device (bus: 1, device: 20) at index 1: Master Brick [6kLrqd] 2024-02-26 16:22:54.998368 <W> <network.c:509> Broadcasting response (U: 6kLrqd, L: 33, F: 255, S: 1, E: 0, I: 0, packet: 30 31 F1 D0 21 FF 18 00 36 6B 4C 72 71 64 00 00 30 00 00 00 00 00 00 00 30 03 02 00 02 05 02 0D 00) because no client/zombie has a matching pending request 2024-02-26 16:22:59.334920 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.334942 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8510) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.334946 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.334951 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.334954 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.334963 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.334966 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.334970 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.334973 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 8512) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.334977 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:22:59.335758 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:00.469956 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8513) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:00.470414 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:00.470467 <W> <usb_transfer.c:428> Read transfer 0x195abc8 (handle: 0x1964600, submission: 8369) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.470472 <W> <usb_transfer.c:428> Read transfer 0x195abe8 (handle: 0x1964690, submission: 8371) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.470476 <W> <usb_transfer.c:428> Read transfer 0x195ac08 (handle: 0x1964720, submission: 8373) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.470480 <W> <usb_transfer.c:428> Read transfer 0x195ac28 (handle: 0x1967160, submission: 8355) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.470483 <W> <usb_transfer.c:428> Read transfer 0x195ac48 (handle: 0x19671f0, submission: 8357) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.470487 <W> <usb_transfer.c:428> Read transfer 0x195ac68 (handle: 0x1966160, submission: 8359) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.470490 <W> <usb_transfer.c:428> Read transfer 0x195ac88 (handle: 0x19661f0, submission: 8361) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.470493 <W> <usb_transfer.c:428> Read transfer 0x195aca8 (handle: 0x1966280, submission: 8363) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.470512 <W> <usb_transfer.c:428> Read transfer 0x195acc8 (handle: 0x1966310, submission: 8365) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.470520 <W> <usb_transfer.c:428> Read transfer 0x195ace8 (handle: 0x1964ad8, submission: 8367) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:00.471146 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd] 2024-02-26 16:23:03.608132 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:03.608153 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:03.608157 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:03.608161 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:03.608164 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:03.608167 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:03.609345 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:03.609456 <W> <usb_transfer.c:428> Read transfer 0x195abc8 (handle: 0x1964600, submission: 8524) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:03.609466 <W> <usb_transfer.c:428> Read transfer 0x195abe8 (handle: 0x1964690, submission: 8525) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:03.609471 <W> <usb_transfer.c:428> Read transfer 0x195ac08 (handle: 0x1964720, submission: 8526) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:03.609478 <W> <usb_transfer.c:428> Read transfer 0x195ac28 (handle: 0x1967160, submission: 8527) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:03.609482 <W> <usb_transfer.c:428> Read transfer 0x195ac48 (handle: 0x19671f0, submission: 8528) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:03.610073 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd] 2024-02-26 16:23:06.531701 <W> <usb_transfer.c:428> Read transfer 0x195ac68 (handle: 0x1966160, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:06.531727 <W> <usb_transfer.c:428> Read transfer 0x195ac88 (handle: 0x19661f0, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:06.531731 <W> <usb_transfer.c:428> Read transfer 0x195aca8 (handle: 0x1966280, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:06.531734 <W> <usb_transfer.c:428> Read transfer 0x195acc8 (handle: 0x1966310, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:06.532989 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd] 2024-02-26 16:23:06.533076 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:06.533086 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8534) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:06.533090 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 8535) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:06.533094 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:06.533097 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:06.533101 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:06.534223 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:10.477011 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8549) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.477060 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8550) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.477104 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 8551) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.477114 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.477123 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.477132 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.477140 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.477148 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 8552) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.477157 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 8553) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.477165 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 8554) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:10.479322 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:10.479637 <W> <usb_transfer.c:428> Read transfer 0x195abc8 (handle: 0x1964600, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.479660 <W> <usb_transfer.c:428> Read transfer 0x195abe8 (handle: 0x1964690, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.479670 <W> <usb_transfer.c:428> Read transfer 0x195ac08 (handle: 0x1964720, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.479679 <W> <usb_transfer.c:428> Read transfer 0x195ac28 (handle: 0x1967160, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.479687 <W> <usb_transfer.c:428> Read transfer 0x195ac48 (handle: 0x19671f0, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.479696 <W> <usb_transfer.c:428> Read transfer 0x195ac68 (handle: 0x1966160, submission: 8545) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.479705 <W> <usb_transfer.c:428> Read transfer 0x195ac88 (handle: 0x19661f0, submission: 8546) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.479713 <W> <usb_transfer.c:428> Read transfer 0x195aca8 (handle: 0x1966280, submission: 8547) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.479721 <W> <usb_transfer.c:428> Read transfer 0x195acc8 (handle: 0x1966310, submission: 8548) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.479729 <W> <usb_transfer.c:428> Read transfer 0x195ace8 (handle: 0x1964ad8, submission: 0) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:10.482042 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd] 2024-02-26 16:23:13.895063 <W> <usb_transfer.c:428> Read transfer 0x195abc8 (handle: 0x1964600, submission: 8565) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:13.895088 <W> <usb_transfer.c:428> Read transfer 0x195abe8 (handle: 0x1964690, submission: 8566) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:13.895092 <W> <usb_transfer.c:428> Read transfer 0x195ac08 (handle: 0x1964720, submission: 8567) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:13.895096 <W> <usb_transfer.c:428> Read transfer 0x195ac28 (handle: 0x1967160, submission: 8568) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:13.895100 <W> <usb_transfer.c:428> Read transfer 0x195ac48 (handle: 0x19671f0, submission: 8569) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:13.895103 <W> <usb_transfer.c:428> Read transfer 0x195ac68 (handle: 0x1966160, submission: 8570) for Master Brick [6kLrqd] aborted by stall condition 2024-02-26 16:23:13.897043 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6kLrqd] 2024-02-26 16:23:14.447729 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8555) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.447756 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8556) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.447761 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 8557) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.447765 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 8558) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.447768 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 8559) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.447777 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 8560) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.447780 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 8561) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.447784 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 8562) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.447787 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 8563) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.447790 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 8564) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:14.448334 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:16.998961 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 8581) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:16.998986 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 8582) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:17.001342 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:21.968506 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:21.968531 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:21.968536 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:21.968539 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:21.970349 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:27.074464 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:27.074693 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:27.074795 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:27.074884 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:27.075741 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:30.551991 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:30.552168 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:30.554533 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:31.892155 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:31.893216 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:35.293526 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:35.293964 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:35.294744 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:37.031052 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:37.033476 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:38.273910 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:38.276154 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:41.525715 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:41.526106 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:41.526365 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:41.526623 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:41.529114 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:42.695988 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:42.697747 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:45.254975 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:45.256603 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:49.002708 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:49.003121 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:49.003435 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:49.003688 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:49.005626 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:50.503097 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:50.504328 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:52.795155 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:52.797160 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:54.399587 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:54.401883 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:56.665937 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:56.666353 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:56.666602 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:56.666618 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:56.666629 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:56.668704 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:23:59.781103 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:59.781588 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:59.781851 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:59.782101 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:59.782347 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:23:59.783631 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:00.815429 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:00.815481 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:00.816269 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:03.179621 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:03.179673 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:03.179686 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:03.179696 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:03.179707 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:03.181098 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:04.824835 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:04.825779 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:07.243762 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:07.243786 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:07.244616 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:10.748589 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:10.748641 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:10.748654 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:10.749654 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:12.664740 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:12.666422 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:13.733181 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:13.733232 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:13.733244 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:13.735072 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:15.247072 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:15.247796 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:19.285848 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:19.285881 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:19.286817 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:20.301689 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:20.301741 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:20.303510 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:27.646882 <W> <usb_transfer.c:428> Read transfer 0x1967818 (handle: 0x19655c8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:27.646913 <W> <usb_transfer.c:428> Read transfer 0x1967838 (handle: 0x1963458, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:27.649018 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:35.566066 <W> <usb_transfer.c:428> Read transfer 0x1967858 (handle: 0x1964e38, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:35.566092 <W> <usb_transfer.c:428> Read transfer 0x1967878 (handle: 0x1969d40, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:35.566944 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:46.094333 <W> <usb_transfer.c:428> Read transfer 0x1967898 (handle: 0x19514c0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:46.094358 <W> <usb_transfer.c:428> Read transfer 0x19678f8 (handle: 0x1967570, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:46.096610 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:24:55.395694 <W> <usb_transfer.c:428> Read transfer 0x19677d8 (handle: 0x1967740, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:55.395967 <W> <usb_transfer.c:428> Read transfer 0x19678b8 (handle: 0x19682b8, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:55.396060 <W> <usb_transfer.c:428> Read transfer 0x19678d8 (handle: 0x19674e0, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:24:55.398419 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] 2024-02-26 16:25:00.414345 <W> <usb_transfer.c:428> Read transfer 0x19677f8 (handle: 0x1969408, submission: 0) for Master Brick [6tdoWM] aborted by stall condition 2024-02-26 16:25:00.415597 <I> <usb_stack.c:103> Cleared read endpoint stall for Master Brick [6tdoWM] What I did: connect over brickv -> only one stack shows up initially wait -> second stack shows up Does anybody know what is going on and what might cause my problem?
  5. Dear all, I have been running into the same problem as Cathodion and have trouble connecting two masterbrick stacks to the same raspberry pi 4. Following picture displays the entire setup when both stack are connected via USB: My problem is, that not always both stacks show up and if they both show up then I am having troubles when using the individual bricklets and they are having timeouts. Following questions came up while I tried to troubleshoot this issue: Is the fix mentioned by photron already implemented in the version of brickviewer which I am using (2.4.25)? If no, is the version posted in this thread compatible with my raspberry pi? Where can i access the log file from brickd? Any input is greatly appreciated. Kind regards, Fridolin
  6. Vielen Dank für deine ausführliche Antwort! Deine Antworten und Tipps haben mir beim Troubleshooting sehr gut geholfen und mittlerweile steht die Kommunikation zwischen Bricklet und Servodrive. Wie du vermutet hast handelt es sich um holding register und nicht input register. Ein weiterer Fehler meinerseits waren die Angaben zu Baudrate, Parity und Stop Bits. Da hatte das Servo Drive leider komplett andere Werkeinstellungen als im Datenblatt angegeben waren. Ich hoffe nun, dass wenigstens alle Servo Drives die gleichen Einstellungen haben. Folgende weitere Frage ist noch aufgekommen: Wie viele Slaves kann ich in meinem Modbus haben? Theoretisch sind ja 247 verschiedene Adressen möglich, allerdings habe ich bei einem sehr ähnlichen Servo Drive wie jenem den ich jetzt verwende gelesen, dass maximal 32 Slaves möglich sind: In einem Modbus Grundlagen Datenblatt habe ich ebenfalls von diesen maximalen 32 Slaves gelesen. Ist es lediglich möglich mehr als 32 Slaves zu haben wenn man einem repeater verwendet? Oder kann man den Modbus sternenförmig anordnen wie im Bild unten um mehr als 32 Slaves anzusteuern ohne repeater? Ist die maximale Anzahl Slaves abhängig von der Kabellänge oder Kabelqualität? Für meine Anwendung habe ich folgende Kabel ausgesucht: CAT6 S/FTP, die sind so wie ich verstanden habe ungefähr im Mittelfeld was Qualität und Abschirmung angeht. Passen die, oder sind die Overkill? Die Frage kommt evt. stark auf meine Anwendung und das Umfeld an ;) Freundliche Grüsse Fridolin
  7. Hallo zusammen Das Auslesen der Lasersensoren mit Modbus funktioniert nun tadelos Dank eurer Hilfe! Bei einer anderen Modbus Anwendung bin ich auf neue Herausforderungen gestossen und hatte gehofft hier erneut Hilfe zu finden. Ich würde gerne mehrere Servodrives (Anleitung ist angehängt) mit dem RS-485 Bricklet ansteuern und bin mir wieder nicht ganz sicher ob ich das Bricklet korrekt konfiguriert habe. In der Anleitung findet man folgende Parameter für die Modbus Kommunikation: Die Servodrives sind neu und es sollten die Werkeinstellung aktiv sein. Dementsprechend habe ich das RS-485 Bricklet wie folgt konfiguriert: Fragen zur Modbus Konfiguration: Da nur zwei Signal Kabel bei den Netzwerkkabel angeschlossen sind, gehe ich davon aus, dass der Servodrive über Half-Duplex kommuniziert? Der Parameter "Word Lenght" wird nicht spezifisch im Datenblatt des Servodrives erwähnt. Ist da "8" ein gängiger Wert oder wie findet man da raus was für ein Wert verwendet werden soll? Weiter wenn ich nun ein Register auslesen möchte, würde ich gerne folgendes Beispiel aus dem Datenblatt reproduzieren: Fragen zum Auslesen der Input Register: In diesem Fall sollte "First Input Number" 302833 bzw. 302832 oder 302834 betragen? Wie find ich raus was für einen Wert bei "Number of Inputs" eingetragen werden soll? Muss ich mich um CRC check Werte kümmern? Oder ist das etwas was das Bricklet automatisch macht? Im Moment bekomme ich kein Feedback von dem Drive und ich gehe davon aus, dass das Problem bei Konfiguration liegt. Bei der Hardware gehe ich davon aus, dass ich diesmal alles richtig gemacht habe: Dip Switches auf on-on-on-off ein Netzwerkkabel verbindet mein RS-485 Bricklet mit dem Servodrive (vertauschen der beiden Litzen habe ich getestet, löst das Problem leider nicht) ein Netzwerkkabel führt aus dem Servodrive wieder raus und die beiden Signallitzen sind mit einem 120 Ohm Widerstand verbunden. Ich bin Dankbar für jegliches Feedback! Freundliche Grüsse Fridolin A5 servo driver user manual 2023.pdf
  8. Jetzt scheint es zu funktionieren. Wenn ich das Register 300201 auslese mit "Number of Inputs" 13 bekomme ich eine Antwort. Falls "Number of Inputs" 1 ist gibts ein Fehler. Ist also genau wie du gesagt hast und der Sensor mag es nicht wenn nur ein Einzelwert ausgelesen wird. Vielen dank für eure Hilfe!
  9. Auch dir vielen dank für das Feedback und die Erklärungen! Habe gerade getestet ob das Register 401100 ausgelesen werden kann und in meinem Fall bekomme ich auf Register 401101 die Antwort 0001. Die Kommunikation scheint also soweit zu funktionieren. Beim auslesen des Input Registers bin ich allerdings immer noch nicht erfolgreich und bekomme bei Register 300199, 300200 und 300201 immer den Fehler "Received illegal data address"
  10. Vielen Dank für das schnelle Feedback! Meine DIP-Schalter waren falsch, ich hatte diese auf Half-Duplex Non-Terminated. Das wäre die korrekte Einstellung wenn das Bricklet als Slave betrieben würde? Ich habe sie jetzt auf Half-Duplex Terminated umgestellt. Der Sensor sollte korrekt angehängt sein, siehe Bild unten. Habe die Leitungen trotzdem mal umgehängt jedoch ohne Erfolg. Die Sensoren sind neu die Baudrate und die Adresse sollten also stimmen. Ich habe trotzdem sicherheitshalber die Sensoren auf Werkseinstellungen zurückgesetzt. Leider kann ich immer noch keine Messwerte auslesen. Fällt Ihnen noch etwas weiteres auf was nicht passen könnte? Ansonsten, da anscheinend beim Bricklet soweit alles korrekt eingestellt ist, setze ich mich sonst mit dem Hersteller des Sensors in Verbindung und Frage da nach ;)
  11. Hallo zusammen Ich möchte einen Laserdistanzsensor mit dem RS485 Bricklet auslesen. Allerdings schaffe ich es nicht das Bricklet so zu Konfigurieren, dass ich etwas beim Sensor auslesen kann und hatte gehofft hier Hilfe zu finden. Der Sensor den ich verwende ist von Baumer: OM20-P0120.HH.TXN Folgend der Ausschnitt aus der Anleitung um den Modbus einzurichten: Im Brickviewer habe ich das RS485 Bricklet entsprechend eingerichtet, löse jedoch beim senden einen Fehler aus. Folgende drei Punkte sind für mich unklar und die könnten zu einem Fehler führen: Ist meine Angabe bei "First Input Number" korrekt? Ich würde gerne wie nach Anleitung bei Addresse 200 die Messwerte auslesen, und so wie ich die Tinkerforge Dokumentation verstanden habe hat das Input Register den Prefix 3. In der Anleitung des Sensors geben Sie eine Function ID von 4 an, im Brickviewer kann ich diesbezüglich allerdings nichts konfigurieren. Weiss jemand was dieser Wert bedeutet? Die Sensoren haben zwei Kabel für die Kommunikation und können somit im Half-Duplex Modus betrieben werden. Ist es dann möglich zwei Sensoren an ein RS485 Bricklet anzuhängen, auch wenn ich die Slave Adressen bei den Sensoren nicht ändern kann? Sieht jemand den Fehler beim Einrichten und könnte mir bitte helfen? Bin sehr dankbar für jegliches Feedback. Freundliche Grüsse Fridolin
  12. Vielen Dank für deine Antwort! Jetzt verstehe ich die Callback Funktionen besser! Zusammen mit der Antwort von photron von der verlinkten Seite läuft nun mein Programm wie gewünscht :)
  13. Vielen Dank für deine Antwort! Das ist genau das was ich brauchte, mit deinem Code schaffe ich nun auch eine Abfragerate von über 990 Hz. Das Verarbeiten der Werte (Filter + PID Algorithmus) und das Setzen von einer Spannung auf einem Bricklet schafft das ESP32 locker ohne zu verlangsamen. Mein PID Loop läuft nun mit 991 Hz was etwa sechs mal schneller ist als was ich vorhin hatte und ausreichend ist für meine Anwendung :) Noch ein kleiner Schönheitsfehler in deinem Code bei der Nachricht im Serialmonitor: Frequenz sollte folgend berechnet werden: count*1000/duration
  14. Hallo Jeremy Konntest du das Problem Lösen um die Messwerte in die main() Ebene zu bekommen von den Callbacks? Ich habe momentan das Selbe Problem und kann leider nicht die Simple Lösung mit der Abfrage verwenden, da diese zu langsam ist. Die Funktion, welche Nils erwähnt hat, welche von ...register_callback übergeben wird hilft mir leider auch nicht weiter. Diese gibt ja keinen Wert zurück (return ...) und ich habe auch keinen pointer in der main() Ebene welcher mir den Messwert aufzeigt. Das einzige was die Funktion macht ist, den Messwert in Serial Monitor zu schreiben, was mir nicht viel hilft: tf_hal_printf("Voltage: %d 1/%d V\n", voltage, 1000); (Ich verwende den ESP32 Brick und möchte das Industrial dual analog in Bricklet mit mindestens 200 Hz auslesen können) Kann ich die Funktion welche von ...register_callback übergeben wird irgendwie anpassen, damit der Messwert in der Main() ebene übergeben wird? Freundliche Grüsse Fridolin
  15. Hallo zusammen Bei der Verwendung der API Bindings mit C++ für Mikrocontroller sind einige Fragen aufgetaucht und ich hoffte, dass mit hier bitte jemand helfen könnte. Ich verwende den ESP32 Brick im stand-alone Betrieb um ein Wegsensor via das Industrial Dual Analog In 2.1 Bricklet auszulesen, gebe den gemessenen Wert an ein PID-Algorithmus weiter um dann via Industrial Analog Out Bricklet 2.0 ein Ventil anzusteuern. Als Vorlage verwende ich die "example_callback.c" Datei für das Industrial Dual Analog In 2.1 Bricklet. In Programm "example_driver.ino" rufe ich dann regelmässig den Wert des Bricklets ab: //im Hauptprogramm: //(...) void loop() { example_loop(&hal); } //aus example_callback.c wird dann folgende Funktion aufgerufen void example_loop(TF_HAL *hal) { // Poll for callbacks tf_hal_callback_tick(hal, 0); } Der ausgelesene Wert wird dann im Serial Monitor gezeigt, soweit so gut. Ich möchte nun jedoch den Wert in einer Variabel speichern und nicht im Serial Monitor ausgeben. Kann mir bitte jemand helfen und zeigen welche Funktion ich benutzen soll um an den Messwert des Bricklets zu kommen? Oder welche Funktion ich anpassen soll, damit sie mir den Messwert zurückgibt? Das simple Beispiel (nicht Callback) konnte ich soweit anpassen, damit es mir den Messwert in meine Variable zurück gibt und nicht im Serial Monitor. Allerdings kann ich diese Funktion nicht verwenden, da Sie zu langsam ist für meine Anwendung mit einer Datenrate von 150 Hz. Ich benötige mindestens eine Datenrate von 200 Hz, besser wäre 2kHz. Für Inputs und Hilfe jeglicher Art bin ich sehr Dankbar! Freundliche Grüsse
×
×
  • Create New...