Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ccdubs

Pages: 1 ... 4 5 [6] 7 8
76
Technical support / Re:Java Updates
« on: May 18, 2008, 02:12:54 PM »
Hi Support,

When I referred to running the exe every time TL Server was started I was suggesting a way that you could avoid complications for users (like me) who upgrade Java and then have problems.

I don't believe (and may be wrong) that the help you suggested is documented anywhere except this forum.

77
Technical support / Re:Java Updates
« on: May 13, 2008, 06:23:56 PM »
I'm not sure which version of java it was but I just upgraded to 1.6.0.50 and TLServer wouldn't start.

I ran the exe like you suggested and everything seems to be back to normal.

Can't this exe be run everytime TLServer is started?

78
Technical support / Re:Java Updates
« on: May 12, 2008, 01:45:37 PM »
I don't want to dwell on this too much but when TL server no longer worked I did just as you said and reinstalled TriLogi a couple of times and the problem was the same.

The only way to fix it was to uninstall Java and reinstall 1.4.2.

My concern is with other applications that may require more recent java.

79
Technical support / Java Updates
« on: May 11, 2008, 05:57:08 PM »
Hi all,

A couple of months ago I installed all the java updates but then couldn't get TLServer to start. When I uninstalled Java and reinstalled the version on the TriLogi disk, all was OK again.

Should I be installing Java updates as they come through?

Thanks

80
Technical support / Re:T100MD-888 Timers
« on: April 05, 2008, 11:28:18 PM »
Thanks support,

So to clarify (sorry) I am certain that we have exceeded 1 million cycles and it is unlikely that I will be able to change the code for a while yet. So it is likely I have "worn out" the eeprom on a number of units.

The only time those eeprom addresses are read is on the first scan so it would require a power interruption for the PLC's to reset (unlikely considering they are all battery backed up). If the EEPROM is worn out would there be any issues on an EEPROM read at reboot? Can any other issues be expected during normal operation.

The value being written to eeprom isn't'a changing value, does this extend eeprom life at all?

Finally, assuming the data I am storing in EEPROM is uninmportant how urgently do i need to stop writing to eeprom on each scan.

Thanks again for feedback and responding so late at night!


81
Technical support / Re:T100MD-888 Timers
« on: April 05, 2008, 06:22:18 PM »
Hi Support,

I have been writing to eeprom on each cycle of a plc scan, obviously unaware that eeprom has limited life.....what happens when the EEPROM lifespan is exceeded?

Will it be just that memory location that has issues or the whole thing?

I have been using save_EEP DM[51],1. Where DM[51] is only changed once a month or so by manual command.

82
Technical support / Re:Hysteresis on T100MD-888 Digital Input
« on: March 29, 2008, 06:14:05 PM »
Thanks support.

If I measure the voltage on a disconnected DI on the PLC it only reads 9V so if I had a simple micro connected to the input I would never exceed the 10.5V.

The PLC is being run at 12V and has the link in place. If this makes a difference, what does the input OFF level become? Actually it would be really useful to know the ON, OFF and hysteresis values and if a function of input voltage how this all relates.

I have managed to get around theissue by connecting 2 diodes in series between the DI and the 5V. This pushes the off voltage up to ~6.5V which seems to work OK with the PLC for switching both ON and OFF (FYI, if I use 4 diodes I intermittantly can't switch on).


83
Technical support / Hysteresis on T100MD-888 Digital Input
« on: March 28, 2008, 02:28:06 PM »
Hi all,

Is there a hysteresis on the T100MD-888 digital input? I have an application where a DI will typically have 5V on it and when a switch is closed it gets pulled to 0V. When the switch is released it is pulled back up to 5V.

The interesting thing is when the PLC is started the input at 5V reads OFF, when the switch is closed the input reads ON. But when the switch is reopened the input still reads ON.

Is there anyway that I can make this switch more definitively? Anyone know what the switching levels are for the DI's?

84
Technical support / Re:STATUS(2) and MODBUS
« on: February 21, 2008, 11:55:13 AM »
Hi Support,

It turns out that the problem was with the communications medium, radio. If I connect directly to the PC the communication was good.

I have found a workaround to this using the PC and PLC as modbus masters and slaves so that I can then check data was received using two way communications.

Thanks.

85
Technical support / STATUS(2) and MODBUS
« on: February 20, 2008, 02:55:19 PM »
Hi All,

I am having difficulty with the status(2) command. I am using the writemb2 (RTU) command to send data to a PC. The PC receives the data correctly but it seems that the PLC is not sending STATUS(2) = 1.

Is is possible that the PC receives the datagram but the PLC thinks there was a transmission fault?

Thanks

86
Technical support / Re:MODBUS RTU and PLC address
« on: February 08, 2008, 11:58:23 AM »
Thanks Support.

I have written some code that sets the protocol from MODBUS (default as set on 1stScan) to AUTO when a certain MODBUS code is sent. This then times out back to MODBUS after 5 mins.

It works well and is a good solution that has made the comms far more robust.

Thanks

87
Technical support / Re:MODBUS RTU and PLC address
« on: February 07, 2008, 10:56:20 AM »
What do you mean by "what character is being sent to the PLC?". As far as I know all I am sending is a typical MODBUS RTU readholding register command. With a typical format of: \x0D\x03\x04\x4C\x00\x0A\x05\xE6. This is as monitored on the tx port of the PC in HEX. I note that there is a x05 charecter in this string and according to the T100MD manual and what it shows as the MODUBS RTU structure this would be the 1st byte of the CRC. This may explain why certain addresses are problematic as the rest of the datagram is the same for all other PLC's.

FYI, the response from the PLC's when "faulted" was 005.

Does this mean that if I was to send a MODBUS set function and transmit a value of 5 to the PLC that the PLC will interpret the communication as something other than modbus?

88
Technical support / Re:MODBUS RTU and PLC address
« on: February 06, 2008, 08:07:09 PM »
After much testing I have come to the following results which I hope make some sense to you.

It seems that the PLC is interpreting datagrams meant for addresses: 1,2,4,5,7,8,11,13,14 (DECIMAL) as something other than MODBUS. When any of these addresses are transmitted to, all PLC's try and respond. Address numbers higher than this seem to be unaffected.

If I force a PLC to only use MODBUS via the setprotocol command the PLC does not respond to any address request apart from its own. This may sound like a solution but I would like to be able to program the PLC's via radio and hence don't want to force MODBUS.

The above also holds when I try and communicate with a TriPLC rather than the SCADA package.

Do you have any idea why these address values seem to be problematic?

89
Technical support / Re:MODBUS RTU and PLC address
« on: February 06, 2008, 12:31:13 PM »
I have since spoken to the radio supplier who is adament that the radio is just a transparent link. He did mention that some modbus devices allow group addressing. I haven't seen any mention of this in the TriPLC manual.

Is this something that may be causing the issue?

90
Technical support / Re:MODBUS RTU and PLC address
« on: February 06, 2008, 10:24:35 AM »
Hi Support,

All the addresses entered in the SCADA are in decimal and I have queried the SCADA suppliers who have said it makes no difference as far as MODBUS is concerned. To prove this I monitored the port with HEX coding and the addresses being requested were 0A, etc.

The PLC's are all connected via radio, when I poll addresses 0D and 0E all PLC's try and respond. I can tell this by the transmit light on all the radios going on. If I disconnect a PLC from the radio, the transmit light no longer flashes when 0D or 0E are polled.

I will be talking to the radio supplier today but everything seems to be pointing to the PLC's. Under what conditions will a PLC force data down com1?

Many thanks.

Pages: 1 ... 4 5 [6] 7 8