Search results

Jump to navigation Jump to search
Results 1 – 32 of 32
Advanced search

Search in namespaces:

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

Page title matches

  • {{Project|name=Tool Access Control|created=1 May 2011|members=[[User:Russ|Russ]] [[User:jasperw|jasperw]] [[Us ...a couple of dangerous/expensive bits of equipment which we need to control access to, both for safety reasons and to stop untrained people damaging them. At
    3 KB (420 words) - 21:33, 4 August 2018
  • ...he owner of a presented rfid card has access to the tool and what level of access they have. The codebase lives on our [https://github.com/londonhackspace/ac `/var/log/nginx/acserver_1234_access.log`: logs from the port 1234 listener on nginx, useful for checking what n
    2 KB (290 words) - 00:30, 18 November 2018
  • == Tools== ...wart || 00:1A:B6:02:B2:18 || 10.0.40.3 || In Service || SSR || eeprom || /tool/hull ||
    5 KB (644 words) - 16:28, 15 October 2020
  • ...scope out the different projects that work together as part of the Access Control Network. ...that sit on the tool or door that is being controlled and manage physical access by reading the rfid card.
    2 KB (270 words) - 16:45, 4 August 2018
  • #REDIRECT [[Project:Tool Access Control]]
    41 bytes (5 words) - 02:03, 14 November 2011
  • #REDIRECT [[Project:Tool Access Control/ACNode-cl]]
    51 bytes (6 words) - 01:59, 17 May 2015
  • 624 bytes (113 words) - 22:36, 25 March 2013
  • (ACN refers to Access Control Node, a physical node attached to a tool) * allow different control outputs (relay, Darlington, servo control etc)
    4 KB (619 words) - 04:45, 18 July 2014
  • #REDIRECT [[Project:Tool Access Control/ACNode-cl/Documentation]]
    65 bytes (7 words) - 01:59, 17 May 2015
  • ...ools acnodes currently each have their own access control lists, which are controlled by maintainers. These lists are held on the acserver. There is at present no 'open access' acnode configuration, all users need to be individually added by maintaine
    3 KB (445 words) - 14:09, 25 August 2020
  • 150 bytes (27 words) - 01:59, 17 May 2015

Page text matches

  • {{Project|name=Tool Access Control|created=1 May 2011|members=[[User:Russ|Russ]] [[User:jasperw|jasperw]] [[Us ...a couple of dangerous/expensive bits of equipment which we need to control access to, both for safety reasons and to stop untrained people damaging them. At
    3 KB (420 words) - 21:33, 4 August 2018
  • #REDIRECT [[Project:Tool_Access_Control]]
    41 bytes (5 words) - 16:40, 4 August 2018
  • #REDIRECT [[Project:Tool_Access_Control]]
    41 bytes (5 words) - 13:40, 8 October 2014
  • #REDIRECT [[Project:Tool_Access_Control]]
    41 bytes (5 words) - 13:40, 8 October 2014
  • #REDIRECT [[Project:Tool Access Control]]
    41 bytes (5 words) - 02:03, 14 November 2011
  • ...duction/training in case we introduce [[Project:Tool Access Control|Access Control]] in the future.
    980 bytes (127 words) - 11:44, 23 May 2017
  • ...ou come with a project in mind, and need a little bit of help or access to tools we may have. To store things, to borrow tools, ...
    26 KB (3,972 words) - 12:37, 17 July 2017
  • ...he owner of a presented rfid card has access to the tool and what level of access they have. The codebase lives on our [https://github.com/londonhackspace/ac `/var/log/nginx/acserver_1234_access.log`: logs from the port 1234 listener on nginx, useful for checking what n
    2 KB (290 words) - 00:30, 18 November 2018
  • ...scope out the different projects that work together as part of the Access Control Network. ...that sit on the tool or door that is being controlled and manage physical access by reading the rfid card.
    2 KB (270 words) - 16:45, 4 August 2018
  • ...ools acnodes currently each have their own access control lists, which are controlled by maintainers. These lists are held on the acserver. There is at present no 'open access' acnode configuration, all users need to be individually added by maintaine
    3 KB (445 words) - 14:09, 25 August 2020
  • * Tools are always broken (and: people use tools without knowing how to do it properly) * People don't return keys for tool access control
    4 KB (665 words) - 14:03, 19 October 2012
  • |name=Woodworking Hand Tools Cupboard |image=Playwood Tools Cupboard.jpg
    1 KB (244 words) - 08:42, 11 February 2022
  • ...//github.com/mentarus/acserver ACServer] part of the [[Project:Tool_Access_Control/ACNet]].
    2 KB (283 words) - 02:49, 10 February 2018
  • Having the amazing tools we do is a privilege that we can always expand on, with the new lasercutte ...a wider cross-section of society can participate - if there is sufficient access.
    20 KB (3,440 words) - 14:24, 6 April 2018
  • * better control on entering people (tail-gaters, padlock not properly closed, code passed o ...sibly assisted by Jan S. and Jasper W. where needed ([[Project:Tool_Access_Control]]).)
    6 KB (1,030 words) - 20:06, 24 April 2016
  • === Tool Access Control === * Description: [[Projects/Tool_Access_Control]]
    7 KB (1,025 words) - 18:54, 21 October 2021
  • ...ecifically, the table saw, planer and band saw require an induction before access is granted through the ACNode card reader system. ...s been put into laying the new electricity cables, constructing the ACNode access system, refurbishing the machinery, writing wiki pages and managing pledges
    9 KB (1,499 words) - 14:21, 7 March 2016
  • ...he name of the HP-All-in-One PC that you can use in the 3D printer room to access the Octoprint web interfaces if you don't have a laptop with you. ...ase do not share access to any untrained individuals as you will lose your access as well.
    4 KB (582 words) - 07:49, 2 December 2022
  • |status=[https://london.hackspace.org.uk/members/tools.php View tool status] https://london.hackspace.org.uk/members/tools.php
    13 KB (2,101 words) - 18:00, 10 October 2022
  • (ACN refers to Access Control Node, a physical node attached to a tool) * allow different control outputs (relay, Darlington, servo control etc)
    4 KB (619 words) - 04:45, 18 July 2014

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)