News:

  • March 29, 2024, 12:36:30 AM

Login with username, password and session length

Author Topic: EBC100 and T1F-14THM Problem!  (Read 6559 times)

bjwela

  • Newbie
  • *
  • Posts: 2
EBC100 and T1F-14THM Problem!
« on: May 16, 2008, 12:39:31 PM »
Hi,

I have the following setup [T1K-01AC8]-[T1H-EBC100]-[T1F-14THM].

The T1F-14THM is jumpered according to the manual and setup for thermocouple type R in Celsius.
 
The T1H-EBC100 is connected to a PC with a crossover cable. I have found the EBC100 in NetEdit3 and changed the IP address to 192.168.1.2 and the PC address is set to 192.168.1.1. The communication is working with both IPX and TCP/IP protocols.
In NetEdit3, when I right-click the EBC100 and select Show Base Contents I will get the following response:

Base 0 : Slot 1 - Module Type 25 - Analog Input
    16 - Double word inputs    (Modbus 584/984 - Input registers 30001-30032)
 
So far everything is working (I assume)...

However, when I try to communicate over modbusTCP with the EBC100 I will only receive 0's on addresses 30001 - 30032. (I have been using my own modbus implementation as well as modscan32 without any success). I have tried different inputs with different R type thermocouples, even tried a calibrator, but no luck, only 0's. I have tried reading the numbers as floats, doubles, hex, binaries, but still 0's.
If I try to read 37001 - 37006 (OS Version etc.) I will get the correct data.

I tried installing CTRIO and the program finds the controller, but no installed modules?? So I can not do anything in the program.

I am not sure what to do next? Anyone please feel free to advice me!

Best regards,

Bjorn Larsson 

MikeS

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 254
    • Host Engineering, Inc.
Re: EBC100 and T1F-14THM Problem!
« Reply #1 on: May 16, 2008, 03:09:25 PM »
Bjorn,

I set that up here and it works fine for me using MDBus.Exe (not modscan32).

Assuming you have the wiring correct, the required ext 24V connected and the external CJC board attached, probably the easiest way to see if the problem is a modbus issue or a hardware issue, is to download our Ethernet DSK and use the demo vb6 program EtherTIO to see if you can read the modules correctly.

If the VB6 program works, it's probably a modbus addressing issue.

If the VB6 program doesn't work either, it's most likely a hardware problem.
Good design costs a lot. Bad design costs even more.

bjwela

  • Newbie
  • *
  • Posts: 2
Re: EBC100 and T1F-14THM Problem!
« Reply #2 on: May 16, 2008, 07:01:22 PM »
It is working now.
My problem was a combination of Modbus software and Windows Firewall issues.

Thanks,

Bjorn