today i got a call that the front door latch wasn't working right.
I came to the space and checked it out, and it's definitely getting sticky -
trying to open the door right after activating the latch release sometimes
doesn't work. Trying a second time works.
I fiddled with the solenoid latch and tried to identify the problem but i can't
see anything specific that's going wrong.
This latch was just purchased a couple of months ago and i'm guessing it was
hundreds of dollars. It's a really fancy thing. Maybe it has a warranty?
I don't see a good place to put in lubricant, and sometimes that makes things
worse. So especially since this thing was fancy and expensive, i think we
should be careful and do the right thing.
Hopefully it's not going to get worse, but I expect that since it was fine
before and now it's not, it's just going to produce more complaints. We might
have to put up a sign or something.
Next time I work on the front door, i'll put a louder speaker on the access
system so that people can better hear the beep indicating that they should pull
the door open.
-jake
the front door computer is unreachable, because some network switch between
it and the server is not working right i guess... either one of the switches
upstairs (in the "public computer lab") or something in the network cage.
I had to leave before i was able to figure out what was wrong and I can't
access the front door computer from theh network, so I don't know whether card
access will work although now that i think about it, it probably does work.
the wifi was being really really really slow tonight (thursday night) and
Arthur and I were trying to figure out what was wrong, and Yar and Marc helped
remotely, but we never figured out where the problem was, and I didn't realize
until i had to leave that the front door computer is entirely inaccessible.
$ ping 100.64.64.11
"No route to host"
even though i power cycled it and it's getting a link light. I don't actually
know where the other end of its ethernet cable is but since the front door
computer is important to security and accessibility, this worries me.
Can someone who understands the building's network please try to fix this ASAP?
-jake
Hi Helen,
I put two cards in an envelope for you in the FNB mail slot, next to the
wheelchair elevator.
One is labeled HELEN and the other labeled K, for the other person you
mentioned. The K one is not activated but the HELEN one is.
Who is the 2nd card for?
Please test your new card and let me know if you need anything else, you can
reach my by phone anytime if you can't get the door to work, and i can control
it remotely.
Thank you
-jake
(415)555-1212
On Sun, 13 Feb 2022, Helen Finkelstein wrote:
> Could I get the new card today (=Sunday)? I would like to use it early
> tomorrow morning.
>
> Helen
>
> On Sun, Feb 13, 2022 at 1:20 AM Jake <jake(a)spaz.org> wrote:
>
>> Hi Helen,
>>
>> can I give you a new card? that will help a lot.
>>
>> President jake
>> (415)555-1212
>>
>>
>>
>> On Sat, 12 Feb 2022, Yardena Cohen wrote:
>>
>>> Thanks for the bug report Helen. I'm copying Jake and Marc who are
>>> more able than me to help with the hardware issues.
>>>
>>> On Thu, Feb 10, 2022 at 6:42 AM Helen Finkelstein <hefinkel(a)gmail.com> wrote:
>>>>
>>>> The card key reader does not work reliably. Sometimes it takes many
>>>> swipes to get it to work; sometimes it does not work at all.
>>>>
>>>> Helen
>>>
>>
>
[ removing omni-discuss and adding access control list in addition to two other
"admin" lists i didn't know about ]
this is something that has happened before. Something about the beaglebone
periodically randomly disables the ethernet port until it gets restarted. We
have never logged into the beaglebone (through its TTL serial port console for
example) in order to diagnose why, we just power cycle it and it comes back up.
would be interesting to save logs to a microSD card (we keep the built-in eMMC
in read-only mode most of the time to prevent wear) so that we could get a clue
as to what's happeneing. Or perhaps make a process to watch for the ethernet
port being powered down and restart it if that happens for whatever reason.
-jake
On Sun, 14 Mar 2021, robb wrote:
> the beaglebone (BB) & switch to BB were sending (green lights on eth ports)
> but the BB wasn't receiving (orange light...) so i rebooted the BB & it's
> pinging now
>
> On Sun, Mar 14, 2021 at 6:51 PM Yardena Cohen <yardenack(a)gmail.com> wrote:
>
>> Did something happen to the omni door computer? I can't reach it over
>> the network, even from within the building. It appears to be working,
>> letting people in. I tried looking at the box, but couldn't make sense
>> of the mess of cables. Maybe an ethernet got disconnected somewhere?
>>
>> The rest of the network is fine. Other devices on that subnet and that
>> interface are reachable, but:
>>
>> $ ip neigh | grep 100.64.64.11
>> 100.64.64.11 dev enp3s2 FAILED
>> _______________________________________________
>> discuss mailing list
>> discuss(a)lists.omnicommons.org
>> https://omnicommons.org/lists/listinfo/discuss
>>
>
Omni door electronic latch is not letting people in, building is locked and
people are
trying to get in for a class
can someone with a key go there and let them in?
-jake
I notice sometimes when i log into the front door computer that the command
prompt is showing that the disk is in read-write mode. I'm worried that if too
much activity happens to the eMMC disk of the beaglebone black that runs the
door, that we might have a disk failure.
either way I think we should have a backup of the door computers' filesystem,
maybe an image of the whole disk, that we can automatically maintain so that if
it ever gets corrupted or flooded or whatever we can easily replace it.
is anyone on this list willing to take that on? I'm not an expert at this and
I feel like others might have an easier time with it.
also I think we should consider migrating the entire system to an SD card
instead of using the soldered-on eMMC chip on the beaglebone (which eventually
dies and ruins everythinng)
here's the disk situation:
/dev/disk/by-uuid/6b3e6ea0-eba5-402a-ae7a-ec2c7555affb on / type ext4
(6b3e6ea0-eba5-402a-ae7a-ec2c7555affb == mmcblk1p2 AKA the eMMC)
/dev/mmcblk1p1 on /boot/uboot type vfat
/dev/mmcblk0p1 on /mnt/sd_card type ext4 (this is the actual sd card)
the SDcard that's in there now is empty so it seems like someone could try
copying the system to it (whether for backup or to boot from it) but I have no
idea how to make a BBB boot from SDcard instead of built-in eMMC although i'm
sure it's no big deal...
anyway this is just a heads-up so that we make it easy to fix in case something
happens to the door system disk. It's been extremely reliable for years but we
can't take that for granite* and it's important infrastructure.
-jake
I can't reach the omni's door computer. A couple people swiped new
cards tonight but I can't approve them. If the computer is off, that
also means we lost their swipes and they have to try again :/
