-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IP address on control board #1096
Comments
@bzeiss Is this something that you had on your roadmap? |
It's a good idea. However, before working on new features, I want to check whether the 'break-in' problem of the rotary is something that can be solved. I suspect it's a problem inherent to the fact that the rotary goes through the multiplexer, usage of python for timing sensitive events as a rather slow language and the raspberry pi os doing a lot of other things besides looking for rotary encoder events. |
@bzeiss I'm looking for stale tickets and have stumbled upon this one. Any news on this? |
I don't know about 'stale' but it is a project that is still available
for people to build .
…------ Original Message ------
From "Uwe Seimet" ***@***.***>
To "PiSCSI/piscsi" ***@***.***>
Cc "levo-man" ***@***.***>; "Author"
***@***.***>
Date 16/10/2023 22:56:52
Subject Re: [PiSCSI/piscsi] IP address on control board (Issue #1096)
@bzeiss <https://github.com/bzeiss> I'm looking for stale tickets and
have stumbled upon this one. Any news on this?
—
Reply to this email directly, view it on GitHub
<#1096 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADVWGAMEKDUL3OPZUUKYWA3X7WUSJAVCNFSM6AAAAAAUY45JKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGMZTSNJSHE>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Yes, fair question. My current impression is that there is little interest in the control board and I'm not sure whether it's worth spending a lot of time investigating a problem that is probably better solved with a different hardware design. Rotarys over I2C multiplexer are probably just not a very good idea at the end of the day (especially if the operating system is doing different things like scsi emulation at the same time). To be honest, we should probably think about removing the control board code. |
Or , maybe just do a redesign of the control board . I do like the
functionality of it and will be doing a blog on a build soon .
…------ Original Message ------
From "Benjamin Zeiss" ***@***.***>
To "PiSCSI/piscsi" ***@***.***>
Cc "levo-man" ***@***.***>; "Mention"
***@***.***>
Date 17/10/2023 09:13:18
Subject Re: [PiSCSI/piscsi] IP address on control board (Issue #1096)
Yes, fair question. My current impression is that there is little
interest in the control board and I'm not sure whether it's worth
spending a lot of time investigating a problem that is probably better
solved with a different hardware design. Rotarys over I2C multiplexer
are probably just not a very good idea at the end of the day
(especially if the operating system is doing different things like scsi
emulation at the same time). To be honest, we should probably think
about removing the control board code.
@akuker ***@***.*** <https://github.com/rdmark>
—
Reply to this email directly, view it on GitHub
<#1096 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADVWGAMXJMM3KV2UQSXJYRLX7Y4Z5AVCNFSM6AAAAAAUY45JKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVHA4TQMBZGU>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I don't think the control board is dead. There haven't been many recent updates, because its relatively simple and works. A re-design of the controller board would be good. It should have its own microcontroller to handle the rotary encoder so the Pi doesn't have to deal with it. |
Yes I think tha that might be the way to go , if a rotary is definitely
needed . The trouble is that I am stacked with things to repair , and
projects to do at the moment .
Something I would definitely be willing to look at in the future .
alan .
…------ Original Message ------
From "Tony Kuker" ***@***.***>
To "PiSCSI/piscsi" ***@***.***>
Cc "levo-man" ***@***.***>; "Mention"
***@***.***>
Date 18/10/2023 02:47:14
Subject Re: [PiSCSI/piscsi] IP address on control board (Issue #1096)
I don't think the control board is dead. There haven't been many recent
updates, because its relatively simple and works.
A re-design of the controller board would be good. It should have its
own microcontroller to handle the rotary encoder so the Pi doesn't have
to deal with it.
—
Reply to this email directly, view it on GitHub
<#1096 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADVWGAJQL2Q7LUKTBXJHERTX74YKFAVCNFSM6AAAAAAUY45JKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXGQ3TONJYGA>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Info
Looking for a way to display the IP address of the Pi with the control board software.
Describe the issue
Looking for a way to display the IP address of the Pi with the control board software. Either as a menu item , or at the bottom of the list of drives ( like the OLED software does ) .
If as a menu item would it be possible to show the IP for any interface that is connected wlan0 or eth0 but only if it has an IP assigned.
The text was updated successfully, but these errors were encountered: