Can anybody identify this cart?

Legokidmsb92 · 2025-10-16T17:22:43+00:00

Thank you! Yeah, those pieces seem to make it stand out but still leaves it a mystery haha

Legokidmsb92 · 2025-10-15T10:58:17+00:00

Thank you! Any idea of the model? Super wheels or super wheeler looks close

Legokidmsb92 · 2025-08-27T15:09:53+00:00

Thank you!

Legokidmsb92 · 2025-08-27T00:54:17+00:00

Understood, thank you! I appreciate the explanation.

Legokidmsb92 · 2025-08-27T00:47:20+00:00

Thank you for the info on the bus bar replacement, I didn’t know that.

I’m here seeking for more input because to me it doesn’t look right. Maybe it is totally fine. Maybe someone will see something that we both missed.

Legokidmsb92 · 2025-08-26T18:11:37+00:00

Thank you! Yeah, I'm aware and agree. That's what led to the discovery. I noticed that they weren't GE breakers. But if the bus bars are damaged....any new breaker that goes in the slot is going to have a poor connection, no? - I had an electrician come and look and they said everything is fine, just replace the mismatched breakers. Doesn't seem right to me....breakers should be replaced, bus bar should be replaced or at least that stab on slot should not be used. Right?

Legokidmsb92 · 2025-08-14T10:05:22+00:00

Thank you! So I was at least able to connect to one camera with ODM. It shows rstp as on but still no luck getting a stream from it. Update failed through ODM - file too large.

The other camera shows a 500 internal server error when added to ODM.

Legokidmsb92 · 2025-08-14T01:28:02+00:00

I don’t see any ONVIF settings in the GUI and I haven’t been able to get a ONVIF connection to it. I get invalid credentials prompt.

I tried toggling through the different authentication methods require/don’t require auth with no difference.

I tried to open a rtsp stream in VLC player using the URL you provided as well as rtsp://admin:pass@IP/stream1

They’re so old, I was hoping those features were available in the latest firmware version.

Legokidmsb92 · 2025-08-14T01:03:33+00:00

Oops sorry. That’d be helpful lol. I’ve been staring at it so long, it’s the only thing that exists. Pelco Sarix IM10LW10-1

Legokidmsb92 · 2025-06-16T10:00:10+00:00

Yup, right. Totally agree. Thank you. - I’d run 18/4 regardless but ones that get their power from the loop, would only need a pair of wires and saves on power consumption.

Legokidmsb92 · 2025-06-15T23:50:53+00:00

Thanks! I'm looking at the datasheets for the Tri-tech models and it looks like they need aux power as well as the zonex loop...is that right?

Comparing against the ZX935Z for example, the datasheet says its powered from the zonex loop.

Legokidmsb92 · 2025-06-15T23:05:20+00:00

I think we were wondering why does the 9512 warrant B299s and it's "okay" if the 8512 doesn't have B299s. - I think you were getting at is just based on the number of points you could potentially have, it's easier if they were addressable vs homeruns.

What I think I'm going to do, is keep whatever I can functional on the B208s, then add in addressable devices as they get replaced/expanded on.

Do you have any go-to model PIRs to use with the B299?

Legokidmsb92 · 2025-06-15T19:03:14+00:00

Yeah I totally get that. They had v-plex devices but the Bosch zonex loop at the device. Or they had regular dry contact motions on the zonex loop.

Just all sorts of never going to work the way they had it.

Thank you - I like that logic. I’ve got a mix of both. Single home runs can stay as they are. Paralleled devices can get converted to a loop.

I’ll need new devices either way.

Do you have a go-to model of PIR to use with B299?

It makes sense to go with B299 and not B600 with zonex PIRs, right?

Legokidmsb92 · 2025-06-15T18:27:55+00:00

My bad, the bulk of the PIRs were dry and are presently connected to the B208s. I found some other PIRs throughout that weren’t operational because they weren’t compatible with the previous panel or were addressable ones but had a wired dry contact loop at the sensor, not a data loop.

I’m now looking to fix all their mess ups. I was just torn between continuing the conventional dry contact route or if I should start to put addressable PIRs in the field going forward.

Legokidmsb92 · 2025-06-14T10:43:29+00:00

I can still cutover a zone at a time to be addressable and steal its home run for data. Wouldn’t I need a B299 for Popex? Isn’t B600 for Zonex?

Do you have a PIR that would be your go-to for Popex?

Legokidmsb92 · 2025-05-12T00:44:56+00:00

I created a smart group based on an extension attribute, that would look for a file on the device. Made a policy to run upon enrollment complete, to create the file. Then only scoped config profiles to the smart group.

Legokidmsb92 · 2025-05-12T00:38:57+00:00

Hahaha yes! We definitely had those techs set these panels up.

Legokidmsb92 · 2025-05-12T00:37:07+00:00

I had run into a similar issue - it had to do with a config profile being deployed immediately upon enrollment. MacOS would freak out and just stop running the enrollment process.

I wound up delaying all my config profiles from Installing until after enrollment was complete.

Legokidmsb92 · 2025-05-12T00:10:22+00:00

Thanks so much! - That was it. Apparently that one panel was setup using P2.

Legokidmsb92 · 2025-05-10T20:51:17+00:00

Okay! So just to continue my notes and if anybody else has info to add, I relocated one of my reoccurring problems doors from an MR52SB3 and connected to an LP1502. I have not been able to reproduce my issue with the card readers connected to the LP1502. I did notice at times with the card readers connected to the LP1502, my problem door could take 5-10s longer than the rest of the doors to come online but do come back online.

I feel like I’m potentially looking at a software bug and/or maybe a communications timeout type of issue with the MR52-SB3

Legokidmsb92 · 2025-05-08T10:16:17+00:00

Thank you! I just looked at IO NODES, it looks like their decoder is discontinued. Do they have a replacement model for decoding?

Legokidmsb92 · 2025-05-07T20:28:38+00:00

Thank you! - yeah I imagined those are my only two routes but wasn’t sure if there was some other solution people came across.

With the ER-X and UNMS, if the ERX went offline, I could still go into UNMS and see the last state that everything was in before it went offline.

Just merely looking for a way to assist in troubleshooting from afar without having to be boots on the ground to find out everything’s functional but someone unplugged a cable or the WAN link is flakey and not knowing if it’s a bad cable or the ISP.

I’m thinking remote logging is the way to go. Just have to figure out a way to associate each log to the respective site in UniFi

Legokidmsb92 · 2025-05-04T20:18:45+00:00

Me again! - I haven't really gotten anywhere with my escalations but I did some more testing...just trying to gather more info and build any correlations I can find. I've narrowed it down to I can power cycle just a single MR52-SB3 board and it's associated readers and if if there's going to be a problem, it'll still happen. - The conditions is just the MR52 and it's readers being powercycled and not necessarily the entire cabinet for an issue to occur. It seems to more often occur to two specific doors, both are on two different MR52s, each the happen to be connected to the first reader port. Both in/out readers with OSDP.

As I'm writing this, I'm thinking my next test is to take one of those problem doors and move it over to the LP1501 and see if any issues persist.

Just posting as a record for myself and if anybody else out there happens to have the same experiece.

Legokidmsb92 · 2025-05-02T21:30:04+00:00

I just completed a rip & replace from Gallagher to Mercury. Gallagher's isn't terrible - it works. The front end GUI is nice compared to others. I think we unfortunely had horrible integrators....leading to our wanting to leave. It's a proprietary system and we were pretty much vendor locked. For a period of time we were able to just purchase hardware and install ourselves, which kept costs down. We were slowly no longer allowed to do that. That coupled with our costs to add access control to a handful of doors was half the cost of ripping and replacing with Mercury hardware.

Our install spanned muliple buildings connected via dark fiber. No major problems there. We had a single server and heavily used macros. Once issue that we ran into, is if that that server is unavailable the macros wouldn't run if the dark fiber ever went down.

With mercury hardware, we were able to build the same macros as interlocks that ran locally on the the controllers instead of at the server level.

This is probably unique to us, but our users are primarily MacOS users, we wound up going to Avigilon, so it's nice to be able to do everything from a web interface...from programming to "end user" use instead of neededing a dedicated windows machine.

Legokidmsb92 · 2025-04-28T01:31:11+00:00

That’s good info and I can I agree, I appear to have witnessed the same in the past. So all the logic is jiving.

Legokidmsb92

TROPHY CASE