Activity for Silver Shield PM Control for Linux
-
xypron modified a comment on discussion Help
I would suggest using -D as it will guarantee stability even if after a restart USB are enumerated in a different sequence. Best regards Heinrich
-
I would suggest to use -D as it will guarantee stability even if after a restart USB are enumerated in a different sequence. Best regards Heinrich
-
Michael Gabler posted a comment on discussion Help
Hi I found that there is already a function -D and -U existing in the sispmctl command. I will give it a try and check if it will increase the stability. BR, Michael
-
Hi I have a Raspberry Pi for controlling almost every aspect of a greenhouse with tomatoes. I need reliability in the controlling of several pumps and lights. The powerplugs are connected via USB to the Pi. As long as I'm working with only one EG-PMS2 it seems to work fine. But when I connect a second plug it seems to come sometimes to connection(?) issues which seems to make one plug unresponsive for short time. I'm not sure what is causing this problem but it has a heavy impact on the control of...
-
Hi I have a Raspberry Pi for controlling almost every aspect of a greenhouse with tomatoes. I need reliability in the controlling of several pumps and lights. The powerplugs are connected via USB to the Pi. As long as I'm working with only one EG-PMS2 it seems to work fine. But when I connect a second plug it seems to come sometimes to connection(?) issues which seems to make one plug unresponsive for short time. I'm not sure what is causing this problem but it has a heavy impact on the control of...
-
Hi I have a Raspberry Pi for controlling almost every aspect of a greenhouse with tomatoes. I need reliability in the controlling of several pumps and lights. The powerplugs are connected via USB to the Pi. As long as I'm working with only one EG-PMS2 it seems to work fine. But when I connect a second plug it seems to come sometimes to connection(?) issues which seems to make one plug unresponsive for short time. I'm not sure what is causing this problem but it has a heavy impact on the control of...
-
Hi I have a Raspberry Pi for controlling almost every aspect of a greenhouse with tomatoes. I need reliability in the controlling of several pumps and lights. The powerplugs are connected via USB to the Pi. As long as I'm working with only one EG-PMS2 it seems to work fine. But when I connect a second plug it seems to come sometimes to connection(?) issues which seems to make on plug unresponsive for short time. I'm not sure what is causing this problem but it has a heavy impact on the control of...
-
Add AppStream metadata
-
Silver Shield PM Control for Linux released /sispmctl/sispmctl-4.12/sispmctl-4.12.tar.gz
-
Prepare release-4.12
-
Prepare release-4.12
-
sispm_ctl: always use original control data
-
Add favicon.ico
-
man/sispmctl.1: mention /etc/sispmctl/password
-
snapcraft: use local source for building
-
index.html: fix typo
-
webpages 2023-06-28
-
index.html: fix typo
-
Hello Erik, The "Gembird Production Catalogue 2004" has these descriptions: Gembird SIS-MS (Silver Shield with master slave function): The slave sockets are automatically switched on and off according to the device connected to the master socket. Gembird SIS-PM 4 sockets are manageable from the computer via USB port. The sad news is: The SIS-MS cannot be controlled by software. The usage idea behind the product is that when you power on your computer the peripherials (printer, monitor) will be powered...
-
Hello Erik, The "Gembird Production Catalogue 2004" has these descriptions: Gembird SIS-MS (Silver Shield with master slave function): The slave sockets are automatically switched on and off according to the device connected to the master socket. Gembird SIS-PM 4 sockets are manageable from the computer via USB port. The sad news is: The SIS-PM cannot be controlled by software. The usage idea behind the product is that when you power on your computer the peripherials (printer, monitor) will be powered...
-
Erik Andrén posted a comment on discussion Help
Hi, I have bought a Gembird SIS-MS in a thrift shop. It is very similar to a SIS-PMS in that it has 4 + 1 power outlets and has a usb connection. When connecting the usb (and powering on the device) to a computers no usb-enumeration occurs and no usb-id is found. Is the SIS-MS supported? Thanks in advance, Erik
-
Ralf Grabow posted a comment on discussion Help
My GEMBIRD runs with no problems under Windows 10. But with amd64, arm64 and under different Distributions a delay occured. And it happens always longer. Now it seems to happen a timeout. I do not understand the magic. I use only debian-bookworm and ubuntu-jammy. ii libc6:arm64 2.36-9+deb12u1 ii libusb-0.1-4:arm64 2:0.1.12-32 ii libusb-1.0-0:arm64 2:1.0.26-1 ii sispmctl 3.1-3 What can I do?
-
snapcraft.yaml: update to version 4.11
-
-
Bump version number to 4.11
-
Oliver Smith updated merge request #2
Add Debian packaging
-
As discussed via mail: Hilko Bengen packaged 4.10 now and put it into Debian unstable: * https://salsa.debian.org/debian/sispmctl * https://tracker.debian.org/pkg/sispmctl Closing.
-
examples/passwordsetup.sh: create /etc/sispmctl/
-
README.md: correct list of devices
-
process: avoid output to stdout
-
=> https://salsa.debian.org/xypron/sispmctl/-/merge_requests/1
-
Thanks for the quick reply! The best place to host Debian packaging is https://salsa.debian.org/. This is what Debian maintainers are using. So you prefer not having it be part of the main repository? I'm not sure what's the best practice here, some projects appear to have the debian directory upstream. I can push the patches to salsa.debian.org too. Please, have a look at this branch https://github.com/xypron/sispmctl/tree/debian. You merge request does not include setting up udev rules and adding...
-
See also: https://mentors.debian.net/package/sispmctl/
-
Hello Oliver, thank you for looking into Debian packaging. The best place to host Debian packaging is https://salsa.debian.org/. This is what Debian maintainers are using. Please, have a look at this branch https://github.com/xypron/sispmctl/tree/debian. You merge request does not include setting up udev rules and adding a user group. Best regards Heinrich
-
Add Debian packaging
-
Heinrich Schuchardt committed [0a813c] on Git
snapcraft.yaml: update metadata
-
ldconfig must be executed to update the cache for libraries. /tmp/locals/lib is none of the paths used by Raspbian to load libraries. Have a look ad LD_LIBRARY_PATH.
-
snapcraft.yaml: use core22
-
Kubuntu 22.04
-
USB set configuration could not set config 1: Protocol error
-
Heinrich Schuchardt committed [576a81] on Git
Makefile.am: include artwork in dist file
-
snapcraft.yaml: update to version 4.10
-
-
Bump version number to 4.10
-
Heinrich Schuchardt committed [e2d849]
configure.ac: allow linking sispmctl statically
-
Heinrich Schuchardt committed [a064c0]
snap: add source-code and issues fields
-
Heinrich Schuchardt committed [30b925]
Create folder with artwork
-
Provide a snapcraft.yaml file
-
passwordsetup.sh: fix build issue
-
Heinrich Schuchardt committed [5adf70]
passwordsetup.sh: fix build issue
-
I keep getting: usb 1-1.5.3: usbfs: USBDEVFS_CONTROL failed cmd sispmctl
-
Adam van Gaalen posted a comment on ticket #28
Hi xypron, No way to trigger it... I just wrote and ran a script to check the logfiles every 10 minutes or so. I did find out, that one of the sispm's serial-number appeared to be incremented a couple of times every hour... I took the USB-cable of that sispm away from the hub that is was connected to and plugged it into a free port on the Pi. That seems to have solved the problem (fingers crossed now). When unplugging I noticed that the plug was kind of loosely connected to the hub-port that it had...
-
The numbering of device numbers depends on the sequence in which they are discovered by the Linux kernel. Every time you unplug and plug in again these numbers change. So this is nothing to rely on. What stays constant is the serial number of the SisPM powerstrip. So specify this number to address one of your devices, e.g. sispmctl -D 01:01:48:0a:d1 -g all Did you find any reproducible way to trigger the "usbfs: USBDEVFS_CONTROL failed" message?
-
I noticed, in the output above, that the devices were not 'nicely' numbered... I did a reboot and now the output looks like: Bus 001 Device 010: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 009: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 007: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 006: ID 04b4:fd13 Cypress Semiconductor...
-
Oops, I missed your posting, sorry for that. lsusb now says: 8:46 mainsberrypi: Command? lsusb Bus 001 Device 010: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 053: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 017: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket Bus 001 Device 006: ID 04b4:fd13 Cypress Semiconductor Corp. Programmable power socket...
-
Add script to create password file.
-
examples: disable ProtectClock in sispmctl.service
-
The command 0xA1 (161) is used to read the serial number (function get_serial()). 71 is EPROTO (protocol error). What is the output of command 'lsusb'?
-
web-interface not working correctly
-
printf("Accessing Gembird #%d USB device %s\n", devnum, dev->filename ); is only executed if invoking with -v. It does not output to the socket but to console. I am closing the issue at it is not reproducible.
-
I keep getting: usb 1-1.5.3: usbfs: USBDEVFS_CONTROL failed cmd sispmctl
-
V M posted a comment on ticket #27
OMG, worked as a charm) Thanks
-
Vitaly Repin posted a comment on ticket #27
The root cause is one of these lines (either in src/process.c or src/main.c): printf("Accessing Gembird #%d USB device %s\n", devnum, This line goes before headers and modern browsers do not recognize this as a proper HTML. Therefore they show it as a text. Workaround for the users is to run the server in a quiet mode (-q switch): E.g.: sispmctl -q -d 0 -L
-
Hi, tried to email you directly, but it bounced back: Your message wasn't delivered to xpyron.glpk@gmx.de because the address couldn't be found or is unable to receive email. Well anyway if I follow TCP stream in wireshark - I'm getting this in Chrome: GET / HTTP/1.1 Host: 192.168.1.222:12341 Connection: keep-alive Cache-Control: max-age=0 Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36 Accept:...
-
web-interface not working correctly
-
Thanks for reporting the issue. What can be seen in the screenshot are the headers and the content of index.html. I am not able to reproduce the issue on using Windows 10, Chrome Version 93.0.4577.63 (Official Build) (64-Bit). We will have to look at the traffic between Chrome and the browser. In Chrome you could open the developer tools and go to the network tab. Open the sispmctl URL. Right click on index html and select clear cache. Press F5 to reload. Right click on index.html and choose "Download...
-
web-interface not working correctly
-
-
-
-
Bump version number to 4.9
-
Bump version number to 4.9
-
src/sispm_ctl.c: correct display of serial number
-
src/sispm_ctl.c: correct display of serial number
-
I merged the patch after adding empty lines after the variable declaration and limiting commit line length to 75 characters.
-
src/schedule.c: fix build with gcc 4.8
-
src/schedule.c: fix build with GCC 4.8
-
Fabrice Fontaine created merge request #1
src/schedule.c: fix build with gcc 4.8
-
-
-
-
process: sleep for 2 seconds on wrong password
-
Bump version number to 4.8
-
main: alert on -b with invalid argument
-
main: skin directory must be provided as an absolute path
-
-
-
Install example files and README.md
-
sispmctl.service: enhance security
-
schedule: correct copyright notice
-
sispmctl.service: enhance security
-
schedule: correct copyright notice
-
Bump version number to 4.7
-
Implement scheduling for EG-PMS2
-
Implement scheduling for EG-PMS2
-
man: list supported models
-
main: remove undocumented usage of 7 as 'all'
-
sispm_ctl: enlarge buffer for reading schedule
-
doc: document schedule format of EG-PMS2
-
main: reformat code
1 >