I tried the new firmware and still a no go on the bacnet devices.
I am getting both Bacnet and MODBUS devices working over MSTP. Channels are dedicated of course and I’ve been running at 115kbps on Modbus. Seems I have been able to connect at 38kbps and 115kbps on Bacnet.
I like to also test a device over USB/MSTP dongles often times first to see if they are showing themselves. They are migrating well from there into MSTP under IP connected controllers.
These have all be Temco controllers showing themselves under a Lead Temco IP connected controller, I have not tested generalized bacnet or modbus items so far.
I have a project where there are more than 10k Schneider SE8650 thermostats. They are on a couple of hundred controllers. The customer had a falling out with the company and want them completely out of their buildings. I can see the SE8650’s on the bacnet bus thru Yabe but they dont show up in the system tree. Ive used the T3_LB on a few jobs where I just used the onboard points and it worked well enough.
But time is running out and it looks like i will have to go with Schneider AS-B’s at 5 times the price. The good thing is that the AS_B’s use SVG graphics hosted in the controller itself. But then it is a lot more money.
Just let us know what features we need to work on and we’ll do it… SVG graphics on board? You got it.
Maurice Duteau
2 Likes
I downloaded and installed the new update for T-3000 and T3_LB but it didnt seem to fix the discovery issue with Bacnet devices.
A colleague is working on this (adding third-party equipment), and I believe we will have results soon
1 Like
Thanks Fance.
Im digging into it myself too.
T3 Bacnet Subnet discovery still dosent work…
We’re going to need a little more to work with than that.
For your reference, here is a t3-OEM Bacnet device set to MSTP and connected to a controller on the RS485 subnet. It looks fine under both T3000 user interface and as a quick check, the Yabe user interface.
1 Like
Yes, But it dosent seem to work for third party mstp devices. Only Your mstp devices.
This Honeywell Spider is on an RS485 / MSTP subnet. It shows as on the main network but its in fact connected to one of the T3-BB master controllers. Our team will have a look at fixing that soon.
Would be good if you can turn of third party mstp devices discovery on T3000. It is annoying to have additional 20 devices in device tree if you do not need them.
Sounds like your subnet MSTP devices are showing up, that’s great. We will make a note for a future rev to allow devices to be ignored.
2 Likes
We think you are saying is T3-Nano, our latest rev is 62.x. It is helpful for me if you describe more about the issue. Thanks.
Thru discovery of Bacnet devices via 3rd party sw on a T3-22i, SUBMSK_1…SUBMSK_4 and PROTOCOL do not communicate any data back in BACNet I/P protocol in Firmware Ver 5.0 or 5.1. The data value remains at zero instead of 255.255.255.0 as would be expected. All other data reads. Has this been resolved or is it a known issue?
We’re still having trouble to understand what you mean. The latest firmware for our T3 series controllers is 62.x. Just going from memory we cannot think of any devices that have firmware versions of 5.x
See image for T3-22AI, I just bought 4 more and they have Ver 5.6. Another issue is the Device Instance is not retained on power cycle. We are using the T3 for I/O with ALC controllers, not your controller.
I am not sure what the latest & greatest firmware version is but in general the best bet is to go with the latest version which you can automatically download using the T3000 built in firmware update tool. Losing the Bacnet device instance sounds like an issue from a long ways back. While you’re at it you should also update T3000 itself.
Once you have done that you can show us a few screen shots from the T3000 user interface and perhaps we can pick something up from that. In particular you can pay attention to the network health on IP and RS485 if applicable. If you are still having issues our goto tool is wireshark, you can send on a capture and we’ll look through it for you.
*Here are some programming examples
10 REM THE FOLLOWING ARE EXAMPLES OF READING A SUBNET DEVICE MODBUS ID=1
20 REM WHICH CONNECTED TO A MASTER CONTROLLER ON THE ETHERNET NETWORK WITH ‘PANEL ID?
30 REM READ THE REGISTER UNDER MODBUS RS485 IN MODBUS FLOATING POINT MODE AND SAVE IT
40 VAR100 = 1.2.MB_REG_FLOAT_ABCD33
50 VAR101 = 1.2.MB_REG_FLOAT_CDAB44
60 VAR102 = 1.2.MB_REG_FLOAT_BADC55
70 VAR103 = 1.2.MB_REG_FLOAT_DCBA66
80 REM HOW TO READ BIT MASK REGISTER.
90 VAR104 = 1.2.MB_REG7
100 VAR105 = 1.2.MB_REG7 & 1
110 VAR106 = 1.2.MB_REG7 | 1
120 VAR107 = 1.2.MB_COIL7
130 VAR108 = 1.2.MB_DISINPUT7
140 VAR109 = 1.2.MB_INPUTREG7
149 REM READ OTHER DEVICE USE BACNET PROTOCAL 123456 IS THE DEVICE ID (INSTANCE NUMBER)
150 VAR110 = 123456AI2048
160 VAR111 = 123456AV3
170 VAR112 = 123456AO4
180 VAR110 = 123456BO5
190 VAR110 = 123456BI6
200 VAR110 = 123456BV7
210 VAR1 = MB_BLOCKWRITE ( 1 , 2 , 3 , 111 , 5 , 6 )
220 VAR10 = MB_BLOCKREAD ( 1 , 2 , 3 , 2 , VAR1 , VAR2 )
228 REM Line 230 writes the high level of VAR1 to register 3
229 REM Line 240 writes the low level of VAR1 to register 4
230 1.2.MB_REG3 = VAR1 / 65536
240 1.2.MB_REG4 = VAR1 * 1000 % 65536 / 1000
2 Likes