Currently testing a NTRIP server configuration with the SNIP Caster. Just after updating both a M+ and a RS2 to dev version 2.23.2, the NTRIP data flows to the caster we no more able to connect as “NTRIP Pushed-in Streams” in the caster app. I had to change both receivers to send their corrections as raw TCP/IP streams to make it work again. I can provide the current caster connection data if someone at EMLID wants to try it out. Thanks.
Further on, reflashed the RS2 and brought it back to 2.22.2 and everything came back to normal. Currently pushing NTRIP streams to the caster but the M+ stays at V2.23.2 for now.
Yes the error is on both RS2 and M+ units with this software revision.
I extracted a full report from my M+ unit just after trying to connect again.
Attached20200302-SystemReport.zip (1.6 MB)
Also, I just configured a M2 that connects okay but it is at Version 2.22.2 (need something that works on this NTRIP caster).
Currently, I can feed the NTRIP caster with a raw TCP/IP input configuration on port 3000 so you may have seen it there but the NTRIP standard is at 2101 or close by and is the same port in and out of the caster for the NTRIP protocol. I will check out if I could temporarily move the NTRIP port above 3000 on the caster but can you confirm it would be a valid workaround?