Teco Westinghouse A510 VFD comms

wolf3000

Member
Join Date
Dec 2010
Location
Hawley, PA
Posts
7
Hello:
I am confused about the A510 modbus addressing scheme. According to Teco's communication addendum the modbuss register addresses start at 2500H which is equivalent to 9472 dec. I have never seen this before. I was under the impression that modbus holding register addresses started at 4000. Can someone enlighten me as to how the Teco addresses work?
 
Modbus addresses start wherever the device manufacturer says they start. There is nothing that says that any vendor's mapp has to start with Holding Register (4)0001 (there's never a (4)0000 in one-based addressing). I've seen lots of devices with register maps that do not start at the 'low end' of the memory area addressing.

comm manual here:
https://www.tecowestinghouse.com/PDF/A510_comm_addendum.pdf

page 1-2
"Function Code 03H: read the register contents"

That tells me that the registers listed are Holding registers (not Input registers) which are read by Function code 0x03

Register 0x2500 is hex and hex addresses are always zero-based address numbering (numbering starts at zero, not one).

Many, many master use "memory area" addressing which uses a leading numeral in front of the indexed register value to indicate what type of register it is. The numeral (4) is always used to indicate Holding Registers. Memory area addressing is one-based, where the first register (whether it is used or not) is one, which for Holding Registers is (4)0001 or (4)00001. Problem is, sometimes the master data entry 'assumes' the (4)xxxx format and the user enters only the indexed value, not the leading numeral (4).

For any hex register in the table, add 40001 to the decimal equivalent to get the memory area based, onebased register value.

0x2506 (Analog output value) = decimal 9478 (zero based), which equates to (4)9479 (5 digit addressing) or (4)09479 (6 digit addressing)
 
Thanks my man, that is super generous of you to respond in great detail.

I moved to the weintek zero based addressing modbus driver and I at least have comms established. I will bash my way through it and figure it out now.

Many thanks!
 

Attachments

  • weintek driver options.png
    weintek driver options.png
    156.4 KB · Views: 4

Similar Topics

Anyone have some info for how to control a TECO EQ7 series VFD via Modbus RTU? We originally installed a pair of Yaskawa GA800s at the remote...
Replies
3
Views
355
Looking for help programming LS electric XGB plc to communicate with a TECO A510 vfd using modbus 485.
Replies
0
Views
674
Hi guys, I've never used a Teco PLR like this and I'm hoping someone might know what I'm up against here. I need to connect a chain of wall...
Replies
0
Views
1,208
Hello all, I am completely new to PLC programming and automation in general. I am working for a company that wants to use a TECO SG2 PLC to...
Replies
0
Views
1,522
Hi All, I am looking for any information on a communication option for a TECO VSD, Part Number JN5-CM-TCPIP. The VSD manual makes reference to...
Replies
4
Views
3,239
Back
Top Bottom