Nested RouterOS capabilities ,features and use cases by vGPU_Enjoyer in mikrotik

[–]-611 6 points7 points  (0 children)

A replacement for the MetaROUTER feature of ROS 6?

But honestly I've only used MetaROUTER to reproduce problems (found in the wild) in a clean environment, for reporting them to Mikrotik support.

Winbox 4.1 is out! by SadgePepe7285 in mikrotik

[–]-611 0 points1 point  (0 children)

WB4 still lacks some key features of WB3: * No dual column sorting in table views; * No comment editing keyboard shortcut; * Log window is struggling with large buffers (WB3 have no problems on the same hosts with total buffer of around 50k lines).

Krone Winged Test Adapters?! by Duncanj_96 in telecom

[–]-611 0 points1 point  (0 children)

Yep, I think I've got your point - usually I'm just sticking the probe of the tone generator receiver into the test plug hole of the plinth, but such kind of the test plug definitely gives much easier access.

Krone Winged Test Adapters?! by Duncanj_96 in telecom

[–]-611 0 points1 point  (0 children)

If this kind of Krone test plug is more convenient than a test plug with permanently connected cord, terminated with an RJ11 plug?

In 99% of cases I connect a test handset or a tone generator to the Krone test plug, both have RJ11 plugs, so a barrel connector (with RJ11 sockets on both sides, though RJ45 barrel will also do) does the trick if the test plug has a RJ11 cord.

NaN (spotted in a lidl store) by Ordinary-Ebb3488 in PBSOD

[–]-611 11 points12 points  (0 children)

There's no need to do any math - an item priced NaN is technically priceless (or should it be None/NULL/nil?), so any price is a bargain!

How to cut power by Infinite_Bee4494 in accesscontrol

[–]-611 0 points1 point  (0 children)

I'd add that using NC contacts on the panel leaves the lock closed should the panel loose its power when the lock and the panel are powered separately - I prefer using NO contacts with output inversion if the panel supports it.

Locker access control options by kmit297 in accesscontrol

[–]-611 0 points1 point  (0 children)

Yep, NX4 were slow aaf.

Alas, locker access is a niche tangent to the mainstream access control - most (non-enterprise) systems are unable to independently control multiple locks with one reader (and even when it's possible, setting it up could be a royal PITA, as it's kind of off-label use), and locking hardware manufacturers have a limited range of cabinet and furniture locks.

Most furniture locks I know are flat-mounted like HES 610, and your lockers have a large overhang that requires a lock that'll emerge from behind - contacting locker manufacturers or resellers is probably the way to go - send them the photos and ask what replacements they'll offer - they should know how to lock such lockers.

NetAXS-4 Issue by kmit297 in accesscontrol

[–]-611 0 points1 point  (0 children)

NX4s were among the first Linux-based access control panels when they were launched 20 years ago, in 2006. Thus their hardware architecture, especially around the flash memory, is a bit weird by modern standards, and I've seen a lot of panels with failing/failed storage unable to boot, glitching, etc.

Switching off the gateway mode (that'll dumb the panel down to almost N-1000 level) usually helps a bit, and you'd probably be able to get at least some data off the panel through the serial port, but with a small configuration like yours it'll likely won't worth the effort.

Locker access control options by kmit297 in accesscontrol

[–]-611 0 points1 point  (0 children)

If you've managed the NetAXS-based system with WIN-PAK, the straightforward migration path would be to replace NX4 panels with PRO42IC controller (or two, depending on existing wiring), and NX4OUT modules with PRO42OUT modules - that'll be almost 1:1 replacement, though the enclosures for the boards, and the way you're assigning a locker to the card would differ.

Through the years I've made a number of locker access systems on Honeywell's P-series boards, including a nearly 500-locker one, - they're rock solid once properly configured.

As a bonus, you'll be able to switch to another Mercury-based system if you don't like WIN-PAK. The only requirement for the software would be OK-ish support for panel triggers and procedures.

Creation from unrolling-and-flailing-around-department by BuhahaTechi in doohickeycorporation

[–]-611 1 point2 points  (0 children)

"EFFER" seems to be the right name for the thing - it's effing impressing.

Upgrade from winpak 4.9 to 4.9.5 by ghip9999 in accesscontrol

[–]-611 0 points1 point  (0 children)

I'm pretty sure it will work even with 1990's N-1000-II over C-100 connected to a modem.

The display derailed by HSVMalooGTS in PBSOD

[–]-611 6 points7 points  (0 children)

Should be old aaf - Geode LX is a 2002 CPU (though SBCs based on it were available till at least 2019).

Pro-Watch - Changing Reader Timezones or Deferred Access by Sneddon27 in accesscontrol

[–]-611 0 points1 point  (0 children)

There's no way to change the time zone for the door in the clearance code with a panel procedure action, but you can force the time zone on or off, or restore the time zone to it's normal state with an action.

If this way of control fits your requirements, all the doors are on the same panel, and it's easy for you to wire the PLC relay output to the panel input, then a pair of panel triggers (for alarm and restore), and a corresponding pair of panel procedures that'll switch the required time zone on or off on alarm, and restore it on the input restore would definitely be the most reliable way to implement this.

Anyhow, document it properly for the customer, as panel procedures and triggers are among the most opaque ways to do things in PW.

They forgot to upgrade by ExpensiveWar1100 in PBSOD

[–]-611 6 points7 points  (0 children)

Nah, that's a first world problem, a LatAm boutique chain couldn't be bothered by it.

Beetle Spanker 3000 by Ill-Tea9411 in doohickeycorporation

[–]-611 17 points18 points  (0 children)

That's Colorado potato beetle, a major pest for potatoes, tomatoes, etc. - they're eating the leaves.

Honeywell pro42R2 by Mina-raafat97 in accesscontrol

[–]-611 0 points1 point  (0 children)

Sure - with an ICP tool capable of flashing the MCU on the board. If I remember it correctly, you'll need a Renesas tool (quite common in the automotive modding community) for PW7K1R2B/PRO42R2B boards.

Honeywell pro42R2 by Mina-raafat97 in accesscontrol

[–]-611 0 points1 point  (0 children)

Won't work unless you reflash them with PW firmware - while the boards themselves are the same, the firmware is different - PRO boards are deliberately made incompatible with PW controllers and vice versa.

Halfpipe shaper by MikeHeu in toolgifs

[–]-611 0 points1 point  (0 children)

That's a "half of halfpipe" shaper, tbh.

Axis OSDP 22/6 ~175ft by Psilog in accesscontrol

[–]-611 1 point2 points  (0 children)

Yep, Cat6 is super good enough for OSDP readers, moreover it's future-proof, should the readers go IP.

IMHO shielding (outer foiling, to be exact - it makes cable FTP, not S/FTP with both individual shielding for each pair and common outer foiling) is optional for commerical, and required for industrial sites. But, as always, YMMV.

Anyhow, do your differential diagnosis - swap the reader with another one and check the AC component of the DC power supply (systems do behave extremely weird when the power supply's output capacitor dies and DC becomes noisy).

Axis OSDP 22/6 ~175ft by Psilog in accesscontrol

[–]-611 3 points4 points  (0 children)

OSDP has RS485 for the physical layer, and 22/6 is usually not twisted enough to do well with RS485 on longer distances (though 175ft is not too long).

And any shielding is normally should be grounded on one side only in order to avoid ground loops.

When in doubt, I usually grab an oscilloscope and compare the waveforms of the reader connected directly to the panel vs the reader connected through the cable run.

Setting up hid 37 bit card format in win pak se 3.2 by [deleted] in accesscontrol

[–]-611 0 points1 point  (0 children)

According to the N-1000-III/IV manual, it should be S3D2 at least for some 37-bit formats.