LinkBack URL
About LinkBacks
Reply With QuoteTried Titan via the same interface on a different pc? Only common thing left in the equation apart from the cable (damaged, too long etc)
Tecom Serial Interface Hey Gang,
Can anyone think of a reason why connecting titan to panel via a serial interface card would have a crazy slow transfer speed? Runs at normal speed when connected to J15.
At first there seemed to be no connection then replaced with new panel, replaced serial interface card... and now this...
You know the difference between you and me? I make this look GOOD.
Tried Titan via the same interface on a different pc? Only common thing left in the equation apart from the cable (damaged, too long etc)
Before I replaced the panel and serial interface card I tried to connect with my laptop and no good.Originally Posted by Drift
I'm using the same pc to connect via serial interface card and via J15, with the same cable... the only common thing I can think of is the RAM and the programming...
Weird one hey.
You know the difference between you and me? I make this look GOOD.
check youve wired the serial interface card up right.
thats a prime culprit for slow tranfer speeds
I have found them to be very slow anyway. i have found if you dont have titian running all the time it has to download history once this has occured the speed is better i dont have titan running all the time and that is how i discovered it
You know you can tick ignor challenger events.
When I say slow, I mean ridiculous. You know how when you first connect it does a bit of transfer (asking for version or what eva) which usually takes about 3 seconds, it takes about 30 with the serial interface card.
Not related to event history at all.
You just can't wire these things up wrong.... it's 3 wires. and if you get it wrong, it doesn't work at all..
You know the difference between you and me? I make this look GOOD.
3 wires plus the loop between CTS and RTS on the interface card ah?
Wade (04-02-12)
CLICK! This should be done at the DB9 end... which it probably is...
but the tech who first attended (when there was no comms at all) installed a USB to rs232 converter, believing that the physical com port could be faulty.
Maybe the converter has an issue with how the DB9 is configured.
One more thing to try out.
Cheers
You know the difference between you and me? I make this look GOOD.
I was always a three wire to the DB9, with Tx, Rx and GND but loop in the blue blocks on the Challenger serial interface card CTS RTS.
This worked with USB to serial converters also.
Posting Permissions
Bookmarks