Hello,
I have a Samsung NASA to BACnet MS/TP intesis gateway. I am able to get the intesis Map software to connect and configure the device. My problem is the BMS does not discover the device. When I plug the BACnet buss into the intesis unit my buss voltage are wrong. once unplugged they return to normal levels. This is the end of the loop so i turned on the terminating resistor. Tested with the resistor off and same problem. Any ideas?
Thanks,
Do you have voltage biasing on? Have you tried reversing the wiring?
Deryck
tried reversing wiring and biasing is off
Have you connected with MAPS and downloaded a configuration? Do you see any bacnet communications back and forth in the Diagnostics tab?
Deryck
I was able to download a configuration. I see little to no traffic and the TxRx LEDs on the intesis device never flash.
I did not have the comms button checked. Now i see traffic
It looks like the coms are working on the backnet side. Do you have the address info configured correctly?
Is the Samsung side configured? It looks empty in the config you shared.
Deryck
The BACnet side does look correct, I was just asking if it is valid for your Network.
The Samsun NASA side looks like it still isnt setup this could be the reason for you issues.
I would think i should be able to discover the devices without one side configured but ok. So when i go to do the bus scan it just says “Unable to start samsung scan process”
Make sure the Samsung side is connected and that the Indoor and outdoor units (IU and OU) have manual addresses set. The scan will not work if they are not manually set.
Deryck
I was told that they units have been set up already the start up tech could not remember this particular units address but said they were all done.
I would strongly recommend you double check that these are set. Most of the time this is the reason the scan fails.
Hello,
So i confirmed the addressing was set and i was able to get data to populate in the intesis maps software. I am still unable to see the intesis device on the bacnet network though.
Thanks,
Jared
Hi @jderosa,
This might be something on the bacnet side. The logs you previsously sent showed it talking on the bus. Here is a snipit from the log, we can see both Rx and Tx traffic.
2021/07/28 14:22:55.3914 - > > 0BS:[Tx] 55 FF 01 46 0A 00 00 96
2021/07/28 14:22:55.3914 - > > 0BS:[ ] HaveToken? Y
2021/07/28 14:22:55.3914 - > > 0BS:[Tx] 55 FF 00 08 0A 00 00 41
2021/07/28 14:22:55.3914 - > > 0BS:[Rx] 55 FF 00 0A 08 00 00 63
2021/07/28 14:22:55.3914 - > > 0BS:[Tx] 55 FF 01 47 0A 00 00 1F
2021/07/28 14:22:55.3914 - > > 0BS:[ ] HaveToken? N
2021/07/28 14:22:55.3914 - > > 0BS:[ ] HaveToken? Y
2021/07/28 14:22:55.3914 - > > 0BS:[Tx] 55 FF 00 08 0A 00 00 41
2021/07/28 14:22:55.3914 - > > 0BS:[Rx] 55 FF 00 0A 08 00 00 63
2021/07/28 14:22:55.3914 - > > 0BS:[Tx] 55 FF 01 48 0A 00 00 E1
2021/07/28 14:22:55.3914 - > > 0BS:[ ] HaveToken? N
2021/07/28 14:22:55.3914 - > > 0BS:[ ] HaveToken? Y
2021/07/28 14:22:55.3914 - > > 0BS:[Tx] 55 FF 00 08 0A 00 00 41
2021/07/28 14:22:55.3914 - > > 0BS:[Rx] 55 FF 00 0A 08 00 00 63
2021/07/28 14:22:55.3914 - > > 0BS:[Tx] 55 FF 01 49 0A 00 00 68
2021/07/28 14:22:55.3914 - > > 0BS:[ ] HaveToken? N
2021/07/28 14:22:55.3914 - > > 0BS:[ ] HaveToken? Y
2021/07/28 14:22:55.3914 - > > 0BS:[Tx] 55 FF 00 08 0A 00 00 41
2021/07/28 14:22:55.9019 - > > 0BS:[Rx] 55 FF 00 0A 08 00 00 63
2021/07/28 14:22:55.9019 - > > 0BS:[Tx] 55 FF 01 4A 0A 00 00 F0
2021/07/28 14:22:55.9019 - > > 0BS:[ ] HaveToken? N
To verify the device can you connect to it via a usb to serial (RS485) and YABA Yet Another Bacnet Explorer download | SourceForge.net This would help verify the device is working removing the bus from the equation.
Deryck