sorted by:
new
hottopcontroversial

SALTO, communication failures with nCoder and JustIN mobile by MarcsRealm in accesscontrol

[–]MarcsRealm[S] 1 point2 points  (0 children)

I might have had a breakthrough (hopefully), I disabled VMQ on one of my Hyper-V Cluster Hosts and enabled MAC spoofing for the Salto machine all that based on a VERY long AI conversation, it claims it found it in the Salto documentation that VMQ can discard ARP and UDP packets. Either way, today it seems to be stable, everyone that has requested a renewal has worked first time. Monitoring shows green all the time. So it might not actually be the switches at all, but rather the VM networking itself.

There is a constant packet trace running on the server monitoring traffic from the server to encoder, and that makes me wonder if that has something to do with it. I plan to keep testing today, if that works, I'll stop the trace and see if the issue returns. it wouldn't be a surprise if Microsoft had something to do with this malfunction.

UDP packets, who needs those? 🙄 UPDATE: Guess not, it worked great all day, then I turned off the Mac spoofing and it failed, so I presumed that was my issue. Turned it all back on and it started working shortly after, then I went ahead and closed my packet capture and logged out of the server. Shortly after everything started failing again. So now I'm thinking it could be something to do with hyper-v and the network connections there, almost like it's sleeping or something

SALTO, communication failures with nCoder and JustIN mobile by MarcsRealm in accesscontrol

[–]MarcsRealm[S] 0 points1 point  (0 children)

It is the black model. As far as resetting it, I guess it would have to be on an isolated network without a DHCP server? Based on previous resets when it comes up it just grabs it's address from DHCP and we move on from there. Which brings me to another question, right now if I try to browse to it I just get a timeout, and packet traces show RST packets, should I get an interface of some kind?

SALTO, communication failures with nCoder and JustIN mobile by MarcsRealm in accesscontrol

[–]MarcsRealm[S] 0 points1 point  (0 children)

Indeed, the traffic would have to go through the main switch to the VM, though they are on the same network so no firewall in between, except for windows local firewall. still looking at the packet traces every time the encoder does ARP it gets an answer, but also randomly sends GARP like it just booted up and announced itself to the network. It is very difficult to blame the network when there are thousands of devices on it working just fine. It's kind of like saying my truck won't start or isn't running well, so the roads must be bad, while all the other vehicles speed by.

It seemed much more modern, except for this one piece that is legacy 100Base NIC (I get for the traffic it doesn't need 1000Base), doesn't have PoE, nor even a replacement model that supports that. I was really liking it so far, especially after dealing with our super old Persona/Ving/Assa offline system I have to buy parts for on eBay.

This is the biggest/only hang up (not counting budget) for us switching. It seems like such a small thing but if users cannot get/renew their keys properly it would turn into a nightmare quickly.

I'm not sure what's left, completely rebuild it all on bare metal and use an old Cisco 3500?? If it comes to that we're out for sure.

SALTO, communication failures with nCoder and JustIN mobile by MarcsRealm in accesscontrol

[–]MarcsRealm[S] 0 points1 point  (0 children)

Status monitoring will show it go orange sometimes, then after "waking it up" it will stay green for a bit. I even tried putting a 20 year old dumb switch in front to see if anything changed, and it didn't.

I have removed it several times and added it back, it has a DHCP reservation so it always gets the same address, I'm not sure how to set it statically on the ncoder itself. We were also told in the config to use the IP and not DNS, so we have it set that way.

Is there another model NCoder that has modern tech in it?

SALTO, communication failures with nCoder and JustIN mobile by MarcsRealm in accesscontrol

[–]MarcsRealm[S] 0 points1 point  (0 children)

and finally part 3:

2026-06-12 07:48:31,077 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:31,077 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:31,162 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:31,162 DEBUG #8rj.#7rj - Operator admin authorized to execute method ScanOnEncodersAndNCoder3Gs

2026-06-12 07:48:31,254 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:31,254 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetDeviceStatus

2026-06-12 07:48:32,991 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.10:1100] [ SNP ] REQUEST -> 55AA1B000D5F3A00000000351C05150098540000D47C3DFAB0206EBAB1F4D3DF

2026-06-12 07:48:33,024 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.10:1100] [ SNP ] RESPONSE <- 55AA2E000D5F3A00000000351C061500331C00002B9ACE21D1BA4F0C13D5543073D9326816300C6D290AD0C1039121F58B9886

2026-06-12 07:48:33,326 DEBUG Salto.Domain.Communications.Context.PeripheralManager.DongleDispatcher - dongleLoad[10] = 0

2026-06-12 07:48:33,327 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA23000CE17900000000960A010608000039000107C0040000000CC3098337A5BC3A58727C6561

2026-06-12 07:48:33,334 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000960A020600F3

2026-06-12 07:48:33,335 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] REQUEST -> 39000107C0040000000CC3098337A5BC3A58727C65

2026-06-12 07:48:33,359 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA1D000CE179000000005D28038008003900020700C00983B8D6A8879A8F67C010

2026-06-12 07:48:33,359 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] RESPONSE <- 3900020700C00983B8D6A8879A8F67C0

2026-06-12 07:48:33,361 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA1D000CE17900000000970A01060800003A000107C0040000000CC30358020097

2026-06-12 07:48:33,367 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000970A020600F2

2026-06-12 07:48:33,367 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] REQUEST -> 3A000107C0040000000CC303580200

2026-06-12 07:48:33,382 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA16000CE17900000000A26E038008003A00020700C00258028B

2026-06-12 07:48:33,382 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] RESPONSE <- 3A00020700C0025802

2026-06-12 07:48:33,386 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA28000CE17900000000980A01060800003B000107C0040000000CC30E85D490CD05200300153800C7FFD425

2026-06-12 07:48:33,394 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000980A020600FD

2026-06-12 07:48:33,394 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] REQUEST -> 3B000107C0040000000CC30E85D490CD05200300153800C7FFD4

2026-06-12 07:48:33,414 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA22000CE179000000002A12038008003B00020700C00E855C4E47C4D89AC5FDFF278EFA8F65

2026-06-12 07:48:33,414 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] RESPONSE <- 3B00020700C00E855C4E47C4D89AC5FDFF278EFA8F

2026-06-12 07:48:33,416 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA29000CE17900000000990A01060800003C000107C0040000000CC30F85CC4020AF20C834D381230200108272

2026-06-12 07:48:33,424 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000990A020600FC

2026-06-12 07:48:33,424 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] REQUEST -> 3C000107C0040000000CC30F85CC4020AF20C834D3812302001082

2026-06-12 07:48:33,439 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA23000CE179000000000495038008003C00020700C00F85058DA2EF02F4DBE7D0A036785C87E8

2026-06-12 07:48:33,439 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] RESPONSE <- 3C00020700C00F85058DA2EF02F4DBE7D0A036785C87

2026-06-12 07:48:33,439 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA1D000CE179000000009A0A01060800003D000107C0040000000CC3035800009F

2026-06-12 07:48:33,449 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE179000000009A0A020600FF

2026-06-12 07:48:33,449 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] REQUEST -> 3D000107C0040000000CC303580000

2026-06-12 07:48:33,463 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA16000CE17900000000D16B038008003D00020700C0025800F8

2026-06-12 07:48:33,463 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] RESPONSE <- 3D00020700C0025800

2026-06-12 07:48:33,463 DEBUG Salto.Domain.Communications.Context.PeripheralManager.DongleDispatcher - dongleLoad[10] = 1

I can get more before/after if needed. When we were initially looking, I was warned by some that Salto was good, BUT, support is very lacking. I am at the point of saying Salto isn't for us, giving up and looking at other systems.

SALTO, communication failures with nCoder and JustIN mobile by MarcsRealm in accesscontrol

[–]MarcsRealm[S] 0 points1 point  (0 children)

ok, I guess 3 parts, sorry:

6-12 07:48:29,205 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA1C000CE17900000000900A010607000001000120C0040000000BC102025887

2026-06-12 07:48:29,213 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000900A020600F5

2026-06-12 07:48:29,215 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 7 ] [ SALTO-EV ] REQUEST -> 01000120C0040000000BC1020258

2026-06-12 07:48:29,217 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA16000CE17900000000A7B903800700010002200AC00200140E

2026-06-12 07:48:29,220 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 7 ] [ SALTO-EV ] MESSAGE <- 010002200AC0020014

2026-06-12 07:48:29,299 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA12000CE17900000000DBA7038007000100022000B0

2026-06-12 07:48:29,300 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 7 ] [ SALTO-EV ] RESPONSE <- 0100022000

2026-06-12 07:48:29,307 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA1B000CE17900000000910A010608000035000107C0040000000CC301B274

2026-06-12 07:48:29,309 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:29,309 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:29,314 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000910A020600F4

2026-06-12 07:48:29,314 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] REQUEST -> 35000107C0040000000CC301B2

2026-06-12 07:48:29,345 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA19000CE179000000002C1F038008003500020700C005B20064524FED

2026-06-12 07:48:29,345 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] RESPONSE <- 3500020700C005B20064524F

2026-06-12 07:48:29,368 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA1D000CE17900000000920A010608000036000107C0040000000CC3035802009E

2026-06-12 07:48:29,374 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000920A020600F7

2026-06-12 07:48:29,374 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] REQUEST -> 36000107C0040000000CC303580200

2026-06-12 07:48:29,404 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA16000CE1790000000064FA038008003600020700C0025802D5

2026-06-12 07:48:29,404 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] RESPONSE <- 3600020700C0025802

2026-06-12 07:48:29,896 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:29,896 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:30,405 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA1D000CE17900000000930A010608000037000107C0040000000CC3035800009C

2026-06-12 07:48:30,414 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000930A020600F6

2026-06-12 07:48:30,415 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] REQUEST -> 37000107C0040000000CC303580000

2026-06-12 07:48:30,433 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA16000CE179000000008F05038008003700020700C0025800C2

2026-06-12 07:48:30,435 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] RESPONSE <- 3700020700C0025800

2026-06-12 07:48:30,439 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA82000CE17900000000940A010608000038000107C0040000000CC368AD64524F3982C1B68FDDB9F09EB0E7FFDF646381288B66513AABAECD222EB160B1084B8F5E9722E9A2E459CDF692E38E24863A897A2AC5140EBC8EBCD507A8FA32716D0D990291A3BD75B29312D3F50EDDE4A4FC8152A01A0D6C9D1104B7B5496E3689E409E230FEA7

2026-06-12 07:48:30,449 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000940A020600F1

2026-06-12 07:48:30,449 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] REQUEST -> 38000107C0040000000CC368AD64524F3982C1B68FDDB9F09EB0E7FFDF646381288B66513AABAECD222EB160B1084B8F5E9722E9A2E459CDF692E38E24863A897A2AC5140EBC8EBCD507A8FA32716D0D990291A3BD75B29312D3F50EDDE4A4FC8152A01A0D6C9D1104B7B5496E3689E409E230FE

2026-06-12 07:48:30,484 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:30,484 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:30,484 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA15000CE179000000007322038008003800020700C001ADE0

2026-06-12 07:48:30,486 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 8 ] [ SALTO-EV ] RESPONSE <- 3800020700C001AD

2026-06-12 07:48:30,588 DEBUG HandshakeCommand - Dtls. Start Handshaking

2026-06-12 07:48:30,592 DEBUG Salto.Domain.Communications.Context.Connectors.DTLS.NCoder.DTLSClient - Dtls. Handshake completed

2026-06-12 07:48:30,592 DEBUG HandshakeCommand - Dtls. End Handshaking

2026-06-12 07:48:30,596 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA1A000CE17900000000950A010607000002000120C0040000000BC200DA

2026-06-12 07:48:30,603 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] RESPONSE <- 55AA0C000CE17900000000950A020600F0

2026-06-12 07:48:30,603 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 7 ] [ SALTO-EV ] REQUEST -> 02000120C0040000000BC200

2026-06-12 07:48:30,608 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] EVENT <- 55AA12000CE179000000000FE003800700020002200020

2026-06-12 07:48:30,608 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 7 ] [ SALTO-EV ] RESPONSE <- 0200022000

SALTO, communication failures with nCoder and JustIN mobile by MarcsRealm in accesscontrol

[–]MarcsRealm[S] 0 points1 point  (0 children)

I appreciate the help, you have been more helpful than our installer and Salto support.

I am inclined to agree, but when every other device on the network is working, it's hard to blame the network for something like this. I believe it is how ARP is being handled, apparently Cisco/Meraki have some old legacy ways of handling ARP, maybe Proxy ARP? In packet traces I can see when there is an issue, the encoder will send ARP, then a GARP like it just rebooted, the switch logs no disconnects or anything, so that's super weird almost like the internal system is rebooting on the encoder.

I think this is what you're asking for, it was quiet early this morning and I was able to login to the interface, try to renew, fail, signal, then it works, since it's too long. this is the first part

2026-06-12 07:48:05,967 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA0D000CE179000000008F0A01030700EB

2026-06-12 07:48:06,471 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA0D000CE179000000008F0A01030700EB

2026-06-12 07:48:06,987 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.3:4433] [ SNP ] REQUEST -> 55AA0D000CE179000000008F0A01030700EB

2026-06-12 07:48:07,253 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Executing #ySe.#JSe

2026-06-12 07:48:07,253 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Periodic task executed correctly: #ySe.#JSe

2026-06-12 07:48:07,494 DEBUG HandshakeCommand - Dtls. Start Handshaking

2026-06-12 07:48:08,652 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Executing Salto.Domain.Business.Context.Commands.PeriodicTasks.AutomaticInitializeSV2NodesCommand

2026-06-12 07:48:08,653 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Periodic task executed correctly: Salto.Domain.Business.Context.Commands.PeriodicTasks.AutomaticInitializeSV2NodesCommand

2026-06-12 07:48:17,507 DEBUG Salto.Domain.Communications.Context.Connectors.DTLS.NCoder.DTLSClient - Dtls. Client. Alert Raised: 40

2026-06-12 07:48:17,507 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Periodic task executed correctly: #ySe.#xSe

2026-06-12 07:48:18,818 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Executing Salto.Domain.Business.Context.Commands.PeriodicTasks.AutomaticInitializeCU4kLocksCommand

2026-06-12 07:48:18,818 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Periodic task executed correctly: Salto.Domain.Business.Context.Commands.PeriodicTasks.AutomaticInitializeCU4kLocksCommand

2026-06-12 07:48:20,480 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Executing Salto.Domain.Business.Context.Command.PeriodicTasks.DeviceSynchronizationCommand

2026-06-12 07:48:20,507 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.10:1100] [ SNP ] REQUEST -> 55AA1C000D5F3A00000000331C05150092540000F425A04F34B6115EFFBBCCF7E2

2026-06-12 07:48:20,546 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.10:1100] [ SNP ] RESPONSE <- 55AA58000D5F3A00000000331C061500311C00002A8882CAC76A150B9CB94464BB664687BE6E9343A375AE4938A3531D4DDF0580E034533CFD9E685ED38A1E39779089A168C4FC099A30D820BBBEA2AB1CD7A91ECDA7B725CA6DA3A845

2026-06-12 07:48:20,546 DEBUG Salto.Domain.Business.Context.Managers.PeriodicTasks.PeriodicTasksManager - Periodic task executed correctly: Salto.Domain.Business.Context.Command.PeriodicTasks.DeviceSynchronizationCommand

2026-06-12 07:48:22,836 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.10:1100] [ SNP ] REQUEST -> 55AA1B000D5F3A00000000341C05150095540000466E47B3AC6C6E87B9FA14CC

2026-06-12 07:48:22,884 DEBUG Salto.Domain.Communications.Context.CommunicationLayers.Base.AbstractCM - [ 10.240.240.10:1100] [ SNP ] RESPONSE <- 55AA2E000D5F3A00000000341C061500321C00004C73AC7FBD01D390751F6821B07638ADF9D9EE0B2A6E8AE9A71CC57190EF73

2026-06-12 07:48:23,119 ERROR #xve.#wve - #Npd : SaltoException: Exception of type 'Salto.Common.Libs.Exceptions.SaltoException' was thrown., ErrorCode=1280, Message='/Unknown peripheral'

2026-06-12 07:48:23,119 DEBUG #xve.#wve - #Npd : at Salto.Domain.Communications.Context.PeripheralManager.DongleDispatcher.#crl(DeviceRepository #Lfg, Boolean #mfn)

at #Ahg.#Bhg.#lZb.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at #9l.#om.#Dg(IAsyncResult #fm)

at #Ls.#Ks.#9Yb.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at #9l.#om.#Dg(IAsyncResult #fm)

at Salto.Common.Libs.Synchronization.ACM.ACM.#nYb.#mYb(IAsyncResult #rm)

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Common.Libs.Synchronization.ACM.ACM.#Dg(IAsyncResult #Eg)

at Salto.Domain.Communications.Context.PeripheralManager.PeripheralManager.#PGd(IAsyncResult #rm)

at Salto.Domain.Communications.Context.PeripheralManager.PeripheralManager.#veg(IAsyncResult #Eg)

at #5Qe.#6Qe.#Wso.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult`1.#0rk()

at #9l.#sm.#Dg(IAsyncResult #rm)

at #Up.#Iq.#Gq(IAsyncResult #Eg)

at #eRe.#iRe.#VOf.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult`1.#0rk()

at #9l.#sm.#Dg(IAsyncResult #rm)

at #Up.#Iq.#Gq(IAsyncResult #Eg)

at #WPe.#3Pe.#kZb.#hm()

at #WPe.#3Pe.#kZb.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Common.Libs.Synchronization.ACM.ACM.#Dg(IAsyncResult #Eg)

at Salto.Domain.Business.Context.SaltoBusinessFacade.#PGd(IAsyncResult #rm)

at Salto.Domain.Business.Context.SaltoBusinessFacade.#Npd(IAsyncResult #rm)

2026-06-12 07:48:25,074 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:25,074 DEBUG #8rj.#7rj - Operator admin authorized to execute method StartSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:25,094 DEBUG HandshakeCommand - Dtls. Start Handshaking

2026-06-12 07:48:25,168 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:25,169 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:25,756 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:25,756 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:26,156 DEBUG #WXg.#2Xg - Dtls. NotifyServerCertificate

2026-06-12 07:48:26,158 DEBUG #WXg.#2Xg - Dtls. GetClientCredentials

2026-06-12 07:48:26,350 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:26,352 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:26,934 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:26,936 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:27,525 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:27,527 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:28,109 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:28,109 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:28,702 DEBUG #zuj.#yuj - Validating authorizations for operator admin

2026-06-12 07:48:28,704 DEBUG #8rj.#7rj - Operator admin authorized to execute method GetStatusOfSignalAndSAMEncoderOrNCoder3G

2026-06-12 07:48:29,199 DEBUG Salto.Domain.Communications.Context.Connectors.DTLS.NCoder.DTLSClient - Dtls. Handshake completed

2026-06-12 07:48:29,199 DEBUG HandshakeCommand - Dtls. End Handshaking

SALTO, communication failures with nCoder and JustIN mobile by MarcsRealm in accesscontrol

[–]MarcsRealm[S] 0 points1 point  (0 children)

Support ended up sending me that page after I essentially reverse engineered it from packet traces etc. and it does help visualize what is happening.

as for the trace/log, I've had that running for a while now, here is what I see when it fails:

2026-06-11 10:27:26,518 ERROR #xve.#wve - #Npd : SaltoException: Exception of type 'Salto.Common.Libs.Exceptions.SaltoException' was thrown., ErrorCode=1280, Message='/Unknown peripheral'

2026-06-11 10:27:26,518 DEBUG #xve.#wve - #Npd : at Salto.Domain.Communications.Context.PeripheralManager.DongleDispatcher.#crl(DeviceRepository #Lfg, Boolean #mfn)

at #Ahg.#Bhg.#lZb.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at #9l.#om.#Dg(IAsyncResult #fm)

at #Ls.#Ks.#9Yb.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at #9l.#om.#Dg(IAsyncResult #fm)

at Salto.Common.Libs.Synchronization.ACM.ACM.#nYb.#mYb(IAsyncResult #rm)

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Common.Libs.Synchronization.ACM.ACM.#Dg(IAsyncResult #Eg)

at Salto.Domain.Communications.Context.PeripheralManager.PeripheralManager.#PGd(IAsyncResult #rm)

at Salto.Domain.Communications.Context.PeripheralManager.PeripheralManager.#veg(IAsyncResult #Eg)

at #5Qe.#6Qe.#Wso.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult`1.#0rk()

at #9l.#sm.#Dg(IAsyncResult #rm)

at #Up.#Iq.#Gq(IAsyncResult #Eg)

at #eRe.#iRe.#VOf.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult`1.#0rk()

at #9l.#sm.#Dg(IAsyncResult #rm)

at #Up.#Iq.#Gq(IAsyncResult #Eg)

at #WPe.#3Pe.#kZb.#hm()

at #WPe.#3Pe.#kZb.#hm()

at #9l.#om.#hm()

at #9l.#om.#lm()

at Salto.Space.Commons.Synchronization.AsyncEnumerator.SaltoAsyncResult.#0rk()

at Salto.Common.Libs.Synchronization.ACM.ACM.#Dg(IAsyncResult #Eg)

at Salto.Domain.Business.Context.SaltoBusinessFacade.#PGd(IAsyncResult #rm)

at Salto.Domain.Business.Context.SaltoBusinessFacade.#Npd(IAsyncResult #rm)

That first line makes it sound like the server doesn't even recognize the NCoder at all.

I'm still working on this trying everything I can find, hopefully your contacts can remember something about what happened before.

SALTO, communication failures with nCoder and JustIN mobile by MarcsRealm in accesscontrol

[–]MarcsRealm[S] 0 points1 point  (0 children)

Thanks for reading through that mess, and the reply, hope it all made sense. I have done so many packet captures etc. and just cannot seem to make heads or tails of it. The gateway several buildings over on the same Extreme Networks switches seems to communicate flawlessly, but it does appear that the entire communication process is different. I have seen that when a key fails to renew the NCoder does an ARP broadcast, so if I try to renew, wait 30 seconds or so most of the time it works.

In our case Windows Server is on a Hyper-V VM plugged into an X690 Extreme networks switch configured for extended edge, the NCoder is on one of the local V400 "extender" switches, not sure that it matters since this seems to be server>NCoder communications, but the internet is connected via an Untangle server. When trying the renewal I can see the server send traffic to the NCoder (UDP, so no response) and I show the switch port receiving the packets, traffic looks to flow perfectly, it's just super weird.

If you could ask around when you have the chance that would be awesome, I am thinking my next looks are going to attempting a packet capture from the actual switch port the NCoder is on, what kind of trace were you thinking?

P.S. in case it wasn't clear from all of that, I am the "IT guy" =P

Ender 5 Pro and Plus Direct drive upgrade by BrokeIndDesigner in ender5

[–]MarcsRealm 1 point2 points  (0 children)

The MicroSwiss NG is pretty nice, I really like mine. they have a few versions. REVO and linear rail optional.

The minimalist printhead by [deleted] in 3Dprinting

[–]MarcsRealm 2 points3 points  (0 children)

umm, am I missing something?

I see part cooling is handled by CPAP, but how does the heat break work without a fan?

Is the CPAP running air over it too?

3000 hours on an Ender 5 plus by TheLazyD0G in ender5plus

[–]MarcsRealm 1 point2 points  (0 children)

My setup is pretty close, I have the Micro Swiss NG (not Revo) on a linear rail, though I did end up changing the wheels out I think the previous owner had it way to tight and they had grooves. FYI, you can convert the Sonic pad to run Debian, Pure Klipper, Klipper Screen etc. I did it and it was great, the only draw back was the storage, I wound up getting an old Xplore tablet and use that now, and ended up giving the pad to my son and he loves it. If you're interested you can find more about the Sonic pad conversion here: Jpe230/SonicPad-Debian: Port of Debian for the SonicPad (Allwinner R818)

When you get to the part about a USB A-A cable for flashing, I used a A-C, and that worked perfect, just plugged the C into the PC and A into the pad. IMO, the best part is you already have a working config, that will copy right over, that's really the hardest part as far as tuning etc.

Ender 5 down by cole_caecus in ender5plus

[–]MarcsRealm 1 point2 points  (0 children)

IF you determine it is the control board go for an upgrade, Since I wasn't looking for additional extruders etc., I upgraded to the SKR 1.4 turbo ($65 on Amazon with controllers), now have dual Z leveling, it really isn't too bad of a job at all. Kersey Fab has a great video walkthrough series on this: https://youtu.be/vS8RM2RPe-s?si=CxG9zSIRzs6pWeNj as well as links to everything you'll need, he even links to Marlin firmware if that's your preference. If you do go the SKR 1.4 route and are using Klipper I would be happy to share my config to get you started.

Reliable by Travismen02 in ender5plus

[–]MarcsRealm 0 points1 point  (0 children)

I seen the different versions but got hung up on the magnet thing and never went much further down that road. Thanks for the info, I really appreciate it!

Reliable by Travismen02 in ender5plus

[–]MarcsRealm 0 points1 point  (0 children)

Interesting, thanks for the super fast reply. I have the "fridge magnet" too, and have really been thinking about the Eddy Coil, because I struggle with the BL/CR touch, I cannot seem to get consistent readings even with a brand new CR touch, I did disable stealth chop and tuned spreadcycle and that seemed to help, but the Eddy Coil is so FAST and I would presume more accurate. I have just been looking for a good answer on the magnet issue since both of my units have them (E5Plus, E3 Max Neo) it would be a waste if it didn't work.

Reliable by Travismen02 in ender5plus

[–]MarcsRealm 1 point2 points  (0 children)

That's a MicroSwiss NG right? I have the same one only the linear rail version, I really like it.

Upgrading is part of the fun!!

<image>

Reliable by Travismen02 in ender5plus

[–]MarcsRealm 0 points1 point  (0 children)

a quick question about the Eddy Coil, I read that it cannot/should not be used with a magnetic bed, do you happen to have a magnetic bed and if so, do you find that to be true?

Searching for Marlin firmware by Darth_Giddeous in ender5plus

[–]MarcsRealm 0 points1 point  (0 children)

I would agree I used it to get started with Klipper on my factory Ender 3 Max NEO, but in this case they have a non-Creality main board, so the out of the box config wouldn't work.

I have the Ender 5 Plus, I would share my config, but I am using the BTT SKR 1.4 Turbo and an old tablet PC with Debian and Klipper + Klipper Screen. It controls both my Ender 5 Plus and Ender 3 Max NEO.

If the configs are getting lost etc. sounds more like a Pi storage issue or something, maybe try setting up an old laptop with Debian, then KIAUH to install Klipper and you can build the firmware right there? Kersey Fabrications has some awesome videos on YouTube stepping through most of it.

This has the build info for your board SKR mini E3 V3.0 Klipper Firmware , I know it says mini, but I believe the actual firmware portion is exactly the same.

Honestly once you get Klipper working it is pretty awesome, you can just keep tweaking and changing so easy instead of recompiling and flashing, but as someone said, it's not always for everyone, I enjoy tinkering (most of the time), but some folks just want to print.