Full marks for your ingenuity and tenacity, @JPB
.
I can see from your screenshot that you are receiving valid NASA data from the MIM on COM2, so all you need to do is configure SNET to connect to COM2. I’ve decribed the details elsewhere e.g. Samsung ASHPs: Review of NASAmonitor – an Alternative to SNET-Pro2, but in a nutshell:
- Execute the SNET software so you see
and click on “Settings” (the blue button top left). - Clicking on “Serial Port” should show the available COM ports like this:
. (You may only see COM2 in your list, but select it in any case). - When setting up SNET for the first time, click on the “Option” button at the bottom right to select your preferences (e.g. units of measure, logging sampling frequency, and auto-logging on startup), then hit “Connect”.
- Click on the “Set Layer (F1/F2)” button, and after a couple of seconds you should see an address appear in the “Control Unit” box (e.g. “10.00.00”). If you do, this will be followed a few seconds later by the normal SNET display, and you’re well away.
- If the Control Unit box remains blank, you may have fallen victim to the (as yet unexplained, but easy to fix) data corruption problem noted in the above NASAmonitor review thread. This often occurs when SNET is first executed. Look at the VCOM data at the moment of SNET startup:
. Prior to SNET connecting the data packets mostly began with (the correct) FD…, but after connecting they mostly start with 7D… That missing lead bit causes CRC failure, so SNET won’t read the data. The only fix I’ve found is to hit the SNET “Disconnect” button, power the RS485 adapter down and up again (confirm that you now have the FD… data packets again on VCOM), and Connect SNET again. You may have to repeat this process once or twice, but once SNET is going it will stay going until you choose to Disconnect again. - SNET does take a little while to explore. The operating manual https://samsung-files.s3.us-east-1.amazonaws.com/Tech_Files/SNET+Pro+and+SNET+Pro+2+Service+Software/Snet+Pro+Service+Software_SNET+Pro+2+Instructions.pdf is slightly helpful (and appears to be written in Korenglish, as we expect from Samsung). Personally I find SNET’s logging capability brilliant for after-the-event analysis, but for watching live data (time trended) I prefer NASAmonitor.
Good luck with SNET!


