[LAT on Tru64]

[BG Jeong]

I'm BG Jeong in south of Korea.
we used Tru64 4.0D which comunicate with PLC by LAT protocol.

a few days ago, server is upgraded DS15 + Tru64 5.1B.

Our application that is communicate with PLC is running normal.

but some times it did not communicate with PLC.
so we need restart application and waiting some time.

our old system that is runnig 4.0D is not appear that situation.

we are testing LAT session and service status.
# latcp -d -S
# latcp -d -P
it's ok.

but when we are running after 10 minutes ago,
below errors occurred.

/dev/tty03 port attached error

do anyone know that LAT port reset or clear mathod?

[Michael Schulte zur Sur]

Hi,

/dev/tty03 is not a LAT device. These are in /dev/lat.

greetings,

Michael

[Al Licause]

RE: tty03 not a LAT device......until recently I would have said the same thing but someone pointed out that if you make the LAT devices using /dev/MAKEDEV lat, then tty0x starting at tty02 can be LAT devices. You need to check the major number of the device against the device types on the system.

You can use strsetup -c to show the mappings and ls -l /dev/tty* will show the major and minor devoce numbers.

If you create the devices using latsetup then they may go into /dev/lat depending on the type of device you requested.

RE: the original problem....you might want to start by using tcpdump to monitor a single LAT mapped conversation then check to see which end was last to speak. This may give a clue as to which end to look at first.

[Michael Schulte zur Sur]

Thanks Al,

I would have never suspected that there too. Strange though.

Michael

[BG Jeong]

Thanks,
I remaked LAT devices by the chance that LAT device might use same minor number.
device numbers are correct.

I have to monitor LAT connection.

I'll post the monitoring result.