Member Login
Search
Jump to a Date
Sponsored Communities
Cool stuff
Neat Stuff

Visit our shop for nerds in control lifestyle products.
Thermal Overload
The threads that wouldn't die...
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
Fortune
Eggheads unite! You have nothing to lose but your yolks.
-- Adlai Stevenson
-- Adlai Stevenson
RSS Feed
www.control.com/rss/
To get a personalized feed, become a member at no cost.
A client of ours has TDC3000. They used to supply us with their schematic DX (not DS) files, that could be generated in the picture editor after loading a schematic using a command something like this 'PRINT NET>SCHEMATICS> DEBUG'. Before the upgrade, this command resulted in a DX file placed into the NET>SCHEMATICS folder.
Customer is remotely located and I have only some feedback on the behavior after the upgrade, however the client claims he can output the file to a printer but not a file. Honeywell claims they do not support nor did they ever support this feature. (I think there is a misunderstanding between Honeywell and a client.)
Could you please advice on how to remedy the situation and/or offer alternatives such as where/how could we convert the DS files into a DX files.
Thank you,
Rudy
rud y . ha rag a @ psa engi neeri ng .co m
Customer is remotely located and I have only some feedback on the behavior after the upgrade, however the client claims he can output the file to a printer but not a file. Honeywell claims they do not support nor did they ever support this feature. (I think there is a misunderstanding between Honeywell and a client.)
Could you please advice on how to remedy the situation and/or offer alternatives such as where/how could we convert the DS files into a DX files.
Thank you,
Rudy
rud y . ha rag a @ psa engi neeri ng .co m
Hi,
It is still suported. Add a file name.
'PRINT NET>SCHEMATICS>MYFILE DEBUG'
Regards.
It is still suported. Add a file name.
'PRINT NET>SCHEMATICS>MYFILE DEBUG'
Regards.
Hi,
What will also work is:
MPRINT NET>FILE_LOCATION>FILE DEBUG
Where FILE is a text file which includes all schematics you want to print. The file need the extension .EL this extension is NOT part of the command!
Regards
What will also work is:
MPRINT NET>FILE_LOCATION>FILE DEBUG
Where FILE is a text file which includes all schematics you want to print. The file need the extension .EL this extension is NOT part of the command!
Regards
From Control Engineering magazine...
Related articles from Control
Engineering magazine- Signal conditioners support universal input, feature detachable display
- Motion control: Omron selects EtherCAT as its next motion bus system
- Wireless: Adoption trends in factory automation
- Tutorial: Instrumentation / DCS integration languages, part 2: FDT
- Connectivity: Embedded LAN module with minimum programming
- New 1-1/8 in. M23 connectors provide 19 pins
- Hatching distributed automation architectures
- Quatech expands Airborne wireless line
- Ethernet drives industrial network growth
- Wireless networks: ISA creates wireless factory automation standard working group
Above articles copyright 2009 Reed Business Information.
Subject to its Terms of Use.
Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2009 Control Technology Corporation. All rights reserved.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Patronize our advertisers!




