Search found 91 matches
- 25 Nov 2024, 17:55
- Forum: Software
- Topic: revpi connect4 device tree source files
- Replies: 3
- Views: 4159
- 29 Oct 2024, 08:50
- Forum: Software
- Topic: Uhrzeit-Puffer defekt
- Replies: 3
- Views: 15968
Re: Uhrzeit-Puffer defekt
Hallo Kristian,
mit dem Befehl sudo hwclock kannst du die Uhrzeit direkt vom Uhrenbaustein (RealTimeClock, RTC) abfragen. Wenn dieser Befehl Fehler oder falsche Werte anzeigt ist davon auszugehen, dass die RTC nicht richtig funktioniert. Wenn der Gold-Cap defekt ist, sollte die Uhrzeit nur bei ...
mit dem Befehl sudo hwclock kannst du die Uhrzeit direkt vom Uhrenbaustein (RealTimeClock, RTC) abfragen. Wenn dieser Befehl Fehler oder falsche Werte anzeigt ist davon auszugehen, dass die RTC nicht richtig funktioniert. Wenn der Gold-Cap defekt ist, sollte die Uhrzeit nur bei ...
- 21 Mar 2024, 08:21
- Forum: Software
- Topic: installing Update via USB
- Replies: 2
- Views: 5456
Re: installing Update via USB
Hi user123,
there is no straight forward way to install an update with an usb drive.
As our systems are based on RaspiOS/Debian it should be possible to create an usb driver with a package repo to update the device. This is not straight forward and we have no documentation on the process. If you ...
there is no straight forward way to install an update with an usb drive.
As our systems are based on RaspiOS/Debian it should be possible to create an usb driver with a package repo to update the device. This is not straight forward and we have no documentation on the process. If you ...
Re: C++
PiControl doesn't use C++ and we don't provide a C++ library.
PiCOntrol provides a device file:
/dev/piControl
To work with piControl you need to open the device file and interact with the process image. We have an example program to show how this is done:
https://github.com/RevolutionPi/revpi ...
PiCOntrol provides a device file:
/dev/piControl
To work with piControl you need to open the device file and interact with the process image. We have an example program to show how this is done:
https://github.com/RevolutionPi/revpi ...
- 22 Feb 2024, 08:42
- Forum: Hardware
- Topic: does RevPi Connect S support Using RS485 as a Serial Console?
- Replies: 5
- Views: 9007
Re: does RevPi Connect S support Using RS485 as a Serial Console?
Hi Peter,
it should be possible to use the RS485 as console. But be aware, that the RS485 on the Connect(+/S) is connected via USB. This has some impact on some minor use-cases. So you only get output from the console after the USB subsystem is initialized. This is later in the kernel startup. But ...
it should be possible to use the RS485 as console. But be aware, that the RS485 on the Connect(+/S) is connected via USB. This has some impact on some minor use-cases. So you only get output from the console after the USB subsystem is initialized. This is later in the kernel startup. But ...
- 19 Feb 2024, 08:50
- Forum: Hardware
- Topic: Location of Connect 4 "Watchdog Jumper"?
- Replies: 1
- Views: 4421
Re: Location of Connect 4 "Watchdog Jumper"?
The RevPi Connect 4 has no watchdog jumper anymore. The watchdog jumper was needed on older Connect models.
Best regards,
Philipp
Best regards,
Philipp
- 31 Jan 2024, 11:21
- Forum: Software
- Topic: RevPi connect 4 CPU Usage
- Replies: 3
- Views: 4489
Re: RevPi connect 4 CPU Usage
Hi underhood,
if you don't use any extension modules (DIO, AIO, ...) and you don't use any revpi specific tooling (revpimodio2, Node-RED-RevPi-Nodes, ...) you can disable the piControl kernel module:
In /etc/modules should be an entry for piControl. You can remove or comment this entry out. But ...
if you don't use any extension modules (DIO, AIO, ...) and you don't use any revpi specific tooling (revpimodio2, Node-RED-RevPi-Nodes, ...) you can disable the piControl kernel module:
In /etc/modules should be an entry for piControl. You can remove or comment this entry out. But ...
- 18 Jan 2024, 10:19
- Forum: Hardware
- Topic: No communication between Connect+ and DIO Module after distribution upgrade to bullseye
- Replies: 7
- Views: 10436
Re: No communication between Connect+ and DIO Module after distribution upgrade to bullseye
Hi Chris,
thanks for the feedback. It would be great if we could get as much information about your setup as possible. If you don't want to share this in public you can send this to support@kunbus.com. Please put a link to this forum post, then we know it is related to this conversation.
A full ...
thanks for the feedback. It would be great if we could get as much information about your setup as possible. If you don't want to share this in public you can send this to support@kunbus.com. Please put a link to this forum post, then we know it is related to this conversation.
A full ...
- 17 Jan 2024, 08:51
- Forum: Hardware
- Topic: No communication between Connect+ and DIO Module after distribution upgrade to bullseye
- Replies: 7
- Views: 10436
Re: No communication between Connect+ and DIO Module after distribution upgrade to bullseye
A different idea, we released the 6.1 kernel for RevPi a short while ago. We needed to change how the communication between RevPi and IO modules is implemented. We didn't get any bug reports about it, but you might test the 5.10 kernel.
sudo apt install raspberrypi-kernel=1:9.20230926+1-5.10.152-1 ...
sudo apt install raspberrypi-kernel=1:9.20230926+1-5.10.152-1 ...
- 17 Jan 2024, 08:40
- Forum: Hardware
- Topic: No communication between Connect+ and DIO Module after distribution upgrade to bullseye
- Replies: 7
- Views: 10436
Re: No communication between Connect+ and DIO Module after distribution upgrade to bullseye
Hi,
this looks pretty strange. Could you temporarily flash an up to date image?
create an image from your device
flash a current image
test if this also happens with this image
reflash your old image
This way we could check if this might be an H/W issue (unlikely, but possible) or if this ...
this looks pretty strange. Could you temporarily flash an up to date image?
create an image from your device
flash a current image
test if this also happens with this image
reflash your old image
This way we could check if this might be an H/W issue (unlikely, but possible) or if this ...