Easy BACnet- Home
- BACnet points lists
- INVT
- EC-TX107 BACnet/IP communication card (Goodrive drives)
Variable frequency drive communication card (VFD) · BACnet points list
INVT EC-TX107 BACnet/IP communication card (Goodrive drives) BACnet points list
Updated 12 November 2026
The EC-TX107 card puts an INVT Goodrive drive on BACnet IP as 32 Analog Values. AV 0 is the control word and AV 12 the state word; the PZD send and receive words carry whatever the drive's P15 parameters assign to them (for example set frequency in, running frequency out). AV 24-31 are a parameter read/write channel.
This page lists 32 BACnet objects for the INVT EC-TX107 BACnet/IP communication card (Goodrive drives) — 16 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from INVT’s own free documentation, linked below.
- Manufacturer
- INVT
- Model
- EC-TX107 BACnet/IP communication card (Goodrive drives)
- Equipment
- Variable frequency drive communication card (VFD)
- Equipment type
- VFDs & pumps
- BACnet objects
- 32 (16 writable)
- Transport
- BACnet IP
- Firmware
- Not stated
- Default device instance
- 1
- Also known as
- EC-TX107, ECTX107, INVT BACnet IP card, GD300-16 BACnet, Goodrive300-16 BACnet
- Source document
- EC-TX107 BACnet/IP Communication Card Manual
Reference only, provided as-is: verify against INVT’s current documentation and the live device before use. Not official INVT information. Terms of use.
BMS integration notes: INVT EC-TX107 BACnet/IP communication card (Goodrive drives)
Set the drive to take commands and frequency from the communication card (P00.01 = 2, P00.02 = 1 on the GD300-16), assign P15.02 = 1 so AV 1 is the set frequency, and assign the P15.13+ words you want back (running frequency, current, fault code). Then write AV 0 = 1 to run forward and 5 to stop.
Minimum points to map
The short list most integrators start with — enough to run the unit from a BMS. Map more as the job needs.
| Object | Name | Why | Access |
|---|---|---|---|
| AV 0 | CONTROL_WORD | Control word: 1 = run fwd, 5 = stop, 7 = fault reset | Command |
| AV 1 | PZD2_SEND | Set frequency x100 Hz when P15.02 = 1 | Command |
| AV 12 | STATUS_WORD | State word: 1 = fwd run, 3 = stopped, 4 = fault | Read |
| AV 13 | PZD2_RECEIVE | Running frequency x100 Hz when P15.13 = 1 | Read |
Enable & remote start
Run commands and frequency must come from the communication card: P00.01 = 2 and P00.02 = 1 on the GD300-16.
Heartbeat & communication loss
P15.41 sets a communication timeout; 0 (default) disables timeout detection.
Network setup
- Default device number 1, IP 192.168.0.1, mask 255.255.255.0.
- Device number = P15.38 x 1000 + P15.39 (0-4194303); IP address, mask and gateway are set in P16.01-P16.12.
- Map each PZD word in P15.02-P15.23 before using it; unmapped words do nothing.
Watch out for
- Object meaning is set by drive parameters, not fixed; document the P15 mapping with the job.
- Control and state word bit tables in the manual are for the GD300-16; other drives may differ.
INVT EC-TX107 BACnet/IP communication card (Goodrive drives) BACnet objects
Type: AI, AO, AV, BI, BO, BV, MI/MO/MV (multi-state) · Access: Read read-only, Write writable, Command writable with a priority array.
Note: the source document has no read/write column, so access here is inferred from the object type (inputs read-only, values writable). Confirm on the live controller before writing.
| Description | States | |||||
|---|---|---|---|---|---|---|
| AVmin | 0 | CONTROL_WORD | Drive control word (1 = run forward, 5 = decel stop, 7 = fault reset) | Command | ||
| AVmin | 1 | PZD2_SEND | Process data word to the drive; meaning set by P15.02 | Command | ||
| AV | 2 | PZD3_SEND | Process data word to the drive; meaning set by P15.03 | Command | ||
| AV | 3 | PZD4_SEND | Process data word to the drive; meaning set by P15.04 | Command | ||
| AV | 4 | PZD5_SEND | Process data word to the drive; meaning set by P15.05 | Command | ||
| AV | 5 | PZD6_SEND | Process data word to the drive; meaning set by P15.06 | Command | ||
| AV | 6 | PZD7_SEND | Process data word to the drive; meaning set by P15.07 | Command | ||
| AV | 7 | PZD8_SEND | Process data word to the drive; meaning set by P15.08 | Command | ||
| AV | 8 | PZD9_SEND | Process data word to the drive; meaning set by P15.09 | Command | ||
| AV | 9 | PZD10_SEND | Process data word to the drive; meaning set by P15.10 | Command | ||
| AV | 10 | PZD11_SEND | Process data word to the drive; meaning set by P15.11 | Command | ||
| AV | 11 | PZD12_SEND | Process data word to the drive; meaning set by P15.12 | Command | ||
| AVmin | 12 | STATUS_WORD | Drive state word (1 = fwd run, 3 = stopped, 4 = fault) | Read | ||
| AVmin | 13 | PZD2_RECEIVE | Process data word from the drive; meaning set by P15.13 | Read | ||
| AV | 14 | PZD3_RECEIVE | Process data word from the drive; meaning set by P15.14 | Read | ||
| AV | 15 | PZD4_RECEIVE | Process data word from the drive; meaning set by P15.15 | Read | ||
| AV | 16 | PZD5_RECEIVE | Process data word from the drive; meaning set by P15.16 | Read | ||
| AV | 17 | PZD6_RECEIVE | Process data word from the drive; meaning set by P15.17 | Read | ||
| AV | 18 | PZD7_RECEIVE | Process data word from the drive; meaning set by P15.18 | Read | ||
| AV | 19 | PZD8_RECEIVE | Process data word from the drive; meaning set by P15.19 | Read | ||
| AV | 20 | PZD9_RECEIVE | Process data word from the drive; meaning set by P15.20 | Read | ||
| AV | 21 | PZD10_RECEIVE | Process data word from the drive; meaning set by P15.21 | Read | ||
| AV | 22 | PZD11_RECEIVE | Process data word from the drive; meaning set by P15.22 | Read | ||
| AV | 23 | PZD12_RECEIVE | Process data word from the drive; meaning set by P15.23 | Read | ||
| AV | 24 | PKW1_SEND | Task identity (request) | Command | ||
| AV | 25 | PKW2_SEND | Parameter address (request) | Command | ||
| AV | 26 | PKW3_SEND | Parameter value MSBs (request) | Command | ||
| AV | 27 | PKW4_SEND | Parameter value LSBs (request) | Command | ||
| AV | 28 | PKW1_RECEIVE | Response identity | Read | ||
| AV | 29 | PKW2_RECEIVE | Parameter address (response) | Read | ||
| AV | 30 | PKW3_RECEIVE | Parameter value MSBs or error code (response) | Read | ||
| AV | 31 | PKW4_RECEIVE | Parameter value LSBs (response) | Read |
No points match these filters.
Object ID lookup: INVT EC-TX107 point IDs by name
AV0CONTROL_WORDAV1PZD2_SENDAV2PZD3_SENDAV3PZD4_SENDAV4PZD5_SENDAV5PZD6_SENDAV6PZD7_SENDAV7PZD8_SENDAV8PZD9_SENDAV9PZD10_SENDAV10PZD11_SENDAV11PZD12_SENDAV12STATUS_WORDAV13PZD2_RECEIVEAV14PZD3_RECEIVEAV15PZD4_RECEIVEAV16PZD5_RECEIVEAV17PZD6_RECEIVEAV18PZD7_RECEIVEAV19PZD8_RECEIVEAV20PZD9_RECEIVEAV21PZD10_RECEIVEAV22PZD11_RECEIVEAV23PZD12_RECEIVEAV24PKW1_SENDAV25PKW2_SENDAV26PKW3_SENDAV27PKW4_SENDAV28PKW1_RECEIVEAV29PKW2_RECEIVEAV30PKW3_RECEIVEAV31PKW4_RECEIVE
Integration notes
- Object names are generic process-data names; what each PZD word means depends on drive parameters P15.02-P15.12 (to the drive) and P15.13-P15.23 (from the drive), all 0 (invalid) by default.
- There is no read/write column; send words and the control word are marked C, receive words R.
- PZD values are scaled integers, for example set frequency 5000 = 50.00 Hz, running frequency x100 Hz, output current x10 A.
- The object property table lists BI/BO/BV/AI/AO types, but only AV 0-31 are documented as instances.
Check it against the live device. A points list tells you what the controller can expose; the unit in front of you may differ by firmware or installed options. This list is provided as-is for reference only and may contain mistakes — confirming it before you write, map or commission anything is up to you (terms). Easy BACnet scans a network for BACnet IP devices from an Android phone, reads every object on the EC-TX107 BACnet/IP communication card (Goodrive drives) and exports what it actually has to Excel — free. New to BACnet? Start with what a BACnet points list is and what the object types mean.
Questions about the INVT EC-TX107 BACnet/IP communication card (Goodrive drives)
How many BACnet points does the INVT EC-TX107 BACnet/IP communication card (Goodrive drives) have?
This list has 32 BACnet objects: 32 analog values. The exact set on a given unit depends on its firmware, installed options and configuration.
Which INVT EC-TX107 BACnet/IP communication card (Goodrive drives) BACnet points are writable?
16 of the 32 objects accept a write. Points marked Command have a priority array: a write holds until it is released, so release it back to automatic when you are done. The source has no read/write column, so this is inferred from object type.
Where is the official INVT EC-TX107 BACnet/IP communication card (Goodrive drives) BACnet documentation?
The source is EC-TX107 BACnet/IP Communication Card Manual, published free by INVT at https://www.invt.com/uploads/file1/20220826/EC-TX107%20BACnetIP%20Communication%20Card%20Manual.pdf.
What are the minimum BACnet points to integrate the INVT EC-TX107 BACnet/IP communication card (Goodrive drives)?
Start with AV 0 CONTROL_WORD (Control word: 1 = run fwd, 5 = stop, 7 = fault reset); AV 1 PZD2_SEND (Set frequency x100 Hz when P15.02 = 1); AV 12 STATUS_WORD (State word: 1 = fwd run, 3 = stopped, 4 = fault); AV 13 PZD2_RECEIVE (Running frequency x100 Hz when P15.13 = 1).
How do I enable BMS control of the INVT EC-TX107 BACnet/IP communication card (Goodrive drives)?
Run commands and frequency must come from the communication card: P00.01 = 2 and P00.02 = 1 on the GD300-16.
Does the INVT EC-TX107 BACnet/IP communication card (Goodrive drives) need a BACnet heartbeat or have a communication timeout?
P15.41 sets a communication timeout; 0 (default) disables timeout detection.
How do I check these points on the real EC-TX107 BACnet/IP communication card (Goodrive drives)?
Scan the network with a BACnet IP browser such as Easy BACnet, open the device and compare its object list with this table. Anything missing is usually an option that isn't installed or a point that is disabled in the controller's configuration.
Source: EC-TX107 BACnet/IP Communication Card Manual. Object names, instances and units are reproduced as published; descriptions are our own.