Activity for steve
-
steve modified a comment on discussion Runtime 🇬🇧
Hi
-
Hi, I'm having problems using the softmotion functions with my servos connected via I2C on a adafruit PWM board. Where do I get the missing "SM3_Drive_Servo, 4.0.0.0" or how can make it work without it? Will be grateful for any hints, thanks. Steve
-
Hi, I'm having problems using the softmotion functions with my servos connected via I2C on a adafruit PWM board. Where do I get the missing "SM3_Drive_Servo, 4.0.0.0" or how can make it work without it? Will be grateful for any hints, thanks. Steve
-
Hi, I want to use an external PostgreSQL Database to log production events. Will any of the above libraries work fort that, or will I have to use MySQL for it to be compatible? Would be very grateful for a hint. Greetings Steve
-
.
-
.
-
Removing the termination resistance at the end from the modbus improved the problem with the 00 bytes mostly, but not completely. One in five packages is still affected and causes errors. Does nobody have a hunch what causes this kind of effect? Does it look rather like a hardware or a software problem?
-
edit 2: I narrowed the problem down to a "padding with zero bytes". For example, the raspberry sends: 01040000000131ca and the PiXtend responds: 00 0104020080b890 00 which would be a correct response, without the two 0 bytes surrounding it. Does somebody have an idea what could cause this? Wrong serialization by the Dongle? Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils...
-
edit 2: I narrowed to problem down to a "padding with zeros". For example, the raspberry sends: 01040000000131ca and the PiXtend responds: 000104020080b89000 which would be a correct response, without the two 0 bytes surrounding it. Does somebody have an idea what could cause this? Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 115200, 1 stop, 8 data, no parity. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0" In the scenario on the...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 19200, 1 stop, 8 data, even parity bit, default settings. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0"...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 19200, 1 stop, 8 data, even parity bit, default settings. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0"...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 19200, 1 stop, 8 data, even parity bit, default settings. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0"...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 19200, 1 stop, 8 data, even parity bit, default settings. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0"...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 19200, 1 stop, 8 data, even parity bit, default settings. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0"...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 19200, 1 stop, 8 data, even parity bit, default settings. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0"...
-
Hi, I connected a "PiXtend eio digital one" to a RaspberryPi 4 via a USB Dongle and am communicating with it using modbus 19200, 1 stop, 8 data, even parity bit, default settings. I can write coils and set the digital outputs but all responses (presumably from the digital input reads) have a CRC_response_fail. Everything is up to date. Does somebody have any ideas what the problem could be, or how to best debug it? dmesg yields: "usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB...