This topic has been mentioned tangentially in other topics but with little detail.
I have a T3-BB and T3000 software which I am combining with Weintek MT8072iP HMI and EasyBuilderPro software. I use the same PC to run both T3000 and Easybuilder. All devices are capable of BACnet/IP and are connected via an Ethernet switch.
Set-up HMI - PLC link within EasyBuilder by adding a controller device. Weintek has no specific Temco driver so select generic BACnet /IP driver. Then follow downloadable “BACnet/IP Connection guide” document.
Select IP address of the controller (whatever it is). BACnet ID 186740, Port no 47808 which match T3-BB.
There are some setting details where I didnt know what to pick. These depend on how T3000.T3-BB are configured
Maximum APDU length accepted? Options 50, 128, 206 (LonTalk), 480 (ARCNET) =default, 1024, 1479 (ISO8802). After experimentation I used 1024 successfully.
I found I needed to close T3000 in order to Get Tag info successfully. Otherwise a Time-out error occurred (even with very long time-out setting).
Tag info returned was:
Analog values - type 2, corresponding to T3 Variables with analog ranges
Binary Values - type 5, corresponding to T3 Variables with digital ranges
Analog Outputs - type 1, corresponding to T3 Analog outputs
Analog Inputs - type 0, NO individual inputs found
Binary Outputs - type 4, corresponding to T3 Digital outputs 1-12
Binary Inputs - type 3 NO individual inputs found
Attached is a screenshot of part of the expanded Tag list. This shows the Inputs and Digital Outputs - note the difference
It is a BIG PROBLEM that the T3 inputs are not recognised.
Probably I could make them visible by duplicating my 30 inputs (13AI, 17 DI) as Variables - but I should not have to, and I dont have enough variables spare.
It is curious that the Analog and Digital Variables are properly allocated based on units/range (but in a jumbled sequence), but the same does not apply to Inputs. This suggests there is some difference in how the different data are structured within T3.
How can the T3 Inputs be made visible?
Within T3, are the BACnet data held in a special “BACnet table(s)” or does BACnet access the long (Modbus) Register List?
Go with ‘segmentation not supported’. You can always experiment with it on and see what happens but I am pretty sure they are not.
Maximum APDU length accepted? Options 50, 128, 206 (LonTalk), 480 (ARCNET) =default, 1024, 1479 (ISO8802). After experimentation I used 1024 successfully.
Max ADPU is 1024
I found I needed to close T3000 in order to Get Tag info successfully. Otherwise a Time-out error occurred (even with very long time-out setting).
This is becuase only one application can use the Bacnet port 47808 at a time. If you need to run both applications at the same time use a second PC.
It is a BIG PROBLEM that the T3 inputs are not recognised.
Make sure the T3 inputs are configured with a range, otherwise the bacnet object is not yet created on the T3 controller. After you do set the range you will likely need to rediscover from the HMI as it probably doesn’t actively discover newly created objects. If you are still having trouble please shut down the HMI and give it a try with T3000 → tools → Bacnet Tool. This is the open source ‘Yabe’ which is the benchmark for a basic bacnet exploration tool.
(None of the Analog inputs are connected just now)
As you suggested, I opened T3000 > BACnet tool (with HMI off), eventually figured out how to add the T3-BB (user instructions?), and found the BACnet objects.
The Analog inputs and Digital Inputs are listed as ANALOG_INPUT:256 and BINARY_INPUT:256. Clicking on any single input brings up: “ERROR_CLASS_OBJECT:ERROR_CODE_UNKNOWN_OBJECT”
BACnet Property: “ERROR_CLASS_OBJECT:ERROR_CODE_UNKNOWN_OBJECT”
Description / Event State: “BACNET_APPLICATION_TAG_ERROR”
It seems that the problem lies with AI256 and BI256. The total number of AI and BI for BB should be 32. There must be an error in the object list. You can try restarting and see if the problem persists. Alternatively, I can remotely assist you in checking.
Hi Chelsea,
I restarted my PC, Restarted T3000, Checked for T3000 updates, restarted T3_BB, reconnected T3-BB controller to T3000, reopened Bacnet Tool and reattached controller to port 47808.
No change from before to AI or BI - still BACnet Tag ERROR - see screenshot.
This only shows first AI error, but same applies to remaining AI and all BI - if I click on them. The Tag list has 16-AIs and 16-BIs, all initially labelled
ANALOG_INPUT:256 and BINARY_INPUT:256
Clicking on any causes Tag to be replaced by error message
I have already uploaded rev67.6 to FTP, you can update it by T3000 automatically.
T3000->Help->Check For Updates->downlaod firmare and update.
There was an issue introduced last version related to the email functions, which are working properly now by the way. Thanks for the heads up on the Bacnet inputs issue.
As mentioned I was able to load the BACnet tags into the Weintek HMI.
However, I notice that NONE of the “units” for Analog items entered into the T3000 Inputs, Outputs and Variable tables have transferred to the properties appearing in T3000 Bacnet Tool, nor to the HMI. In all case the “Units” property reports “95 No Units”.
Is it possible to report Units information correctly as part of BACnet objects?
I have some more information about this “units” problem.
I have a number of Analog Inputs with units/ranges defined as °C, %, Volts. In BACnet Tools, ALL the AIs report Properties - Units “95 : No Units”
I also have a number of Variables defined as analogs - with range/units selected in Variables table. When I look under BACnet tools
if selected range is °C, BACnet Tools > Properties correctly reports “Units: 62 : Degrees Celsius”
if the selected range is kWatts, Properties correctly reports “Units - 48 : Kilowatts”
for other selected ranges/units (eg flow m3/h (custom range), volume m3, energy kWh BACnet Tools > Properties report “Units 95: No Units”
I see that the units designations in BACnet Tools > Properties are different from those in the Variables table - eg
Range “31 - °C” in Variables table becomes “62: Degrees Celsius” (BNTools)
"Range “39 KWatts” in Variables tables becomes “48: Kilowatts”
I looked up ANSI/ASHRAE Standard 135: 2024 - BACnet (it is available for free on-line viewing). Clause 21.6 (pages 957 to 973) set out the BACnet standard unit designations - a huge list! So, 62 is the standard BACnet designation for degC - which is different from T3000 range number (39 - °C).
kWh has BACnet code 19
m3/h has BACnet code 135
etc, etc
I took a note of the units I am interested in and can advise if that helps.
Obviously, in some - but not all- cases T3000 is able to map to the correct units in BACnet. I think this might be the crux of the problem. I dont think it would be practical for T3000 to adopt the same unit designations as BACnet - there are about 400!
(The BACnet standard units designations are also different from international standard designations - eg Kilowatts should correctly be kW per previous post on that topic. I will have to contact the standard committee!)
