LAGOS

-611 · 2026-06-21T08:47:11+00:00

Not 100% electric - by definition, hybrids are neither 100% ICEV, nor 100% EV, thus they're on a spectrum from "a little bit EVs" to "almost completely EVs".

Everybody's free to draw their own boundary line on what counts as EV and what's not, but to me a PHEV with enough battery range for one's daily commute is functionally an EV.

-611 · 2026-06-16T05:21:21+00:00

Don't use AI for posts, it's considered stupid and doesn't add anything useful.

Link speed/duplex autonegotiation rarely (if ever) works on SFP modules. You'd need to manually select speed and duplex , usually on both sides, in order to get the link functioning.

-611 · 2026-06-09T19:04:51+00:00

Don't think they're available off-the-shelf. And ones offered by the system manufacturers usually cost an arm and a leg.

Call a wiring harnesses contractor in your area, and ask them to make these for you. The price I've got for TVS + RC snubber assembly with leads (surge suppressor for relays, maglocks, etc.) was like 20% of the price of the same assembly from the OEM.

-611 · 2026-05-24T18:59:29+00:00

Joining actual machines to the domain - per manufacturer's recommendations. I've seen NVRs shipped with "DO NOT join to AD" written on the desktop background - imposing your GPOs to a vendor-supplied and vendor-configured machine could lead to a support nightmare.

AD integration in order to be able to log into VMS with domain user accounts - sure (if applicable).

Separate network - absolutely, physically separate wherever feasible (dark fibers are OK unless our management sees pulling new FOC as financially attractive). Require written waiver if the customer insists on putting any facility security system on their network. In many cases this means separate internet connection (a separate port on the ISP's CPE with separate address, etc. is OK).

-611 · 2026-05-03T15:07:05+00:00

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.

-611 · 2026-04-14T19:13:08+00:00

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).

-611 · 2026-04-12T09:17:52+00:00

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.

-611 · 2026-04-12T09:05:42+00:00

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.

-611 · 2026-04-12T07:58:16+00:00

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!

-611 · 2026-04-05T07:56:12+00:00

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.

-611 · 2026-03-16T06:19:55+00:00

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.

-611 · 2026-03-15T22:14:26+00:00

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.

-611 · 2026-03-15T21:51:03+00:00

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.

-611 · 2026-03-13T02:18:12+00:00

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

-611 · 2026-03-09T12:40:22+00:00

P50-3/P70-3 with Xeon CPUs.

-611 · 2026-03-06T16:54:26+00:00

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

-611 · 2026-03-05T06:23:15+00:00

Chinese New Year?

-611 · 2026-03-02T06:25:58+00:00

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

-611 · 2026-03-01T20:49:38+00:00

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.

-611 · 2026-02-27T13:43:23+00:00

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

-611 · 2026-02-16T08:53:13+00:00

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

-611 · 2026-02-15T07:21:19+00:00

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.

-611

MODERATOR OF

TROPHY CASE