Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84249members
353348posts

[Imported] Issue with printing (crash of ViewX) in ClearSCADA 2014v1.1

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

sbeadle
Janeway Janeway
Janeway
0 Likes
0
272

[Imported] Issue with printing (crash of ViewX) in ClearSCADA 2014v1.1

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: mchartrand, originally posted: 2018-10-25 15:56:18 Id:228
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.

_______

**_AlexKaz:
I have faced with crash of ViewX after trying to print graphic from ViewX.
It happens over time without any sequence (2-3 graphics good then crash, some times 4-5 graphics good and then crash).
All I have noticed is that file with only one picture of my graphic which is sent on printer is rather huge 5-6Mb while simple printscreen of the same graphic is much lighter._**

About system:

1. Printer: HP LaserJet Pro 400 Color M451dn
2. Printer driver: HP LJ300-400 Color M351-M451 PCL6 v 5.3.0.12262
3. System: Windows 7 SP1 x64
4. ViewX version: ClearSCADA2014 R1.1, Build 75.5387

**_Below is an information from "...\\Logs\\Dumps\\SE.Scada.ViewX 2015-11-26 07-12-51.mdmp". Open it with WinDbg. Not sure that it contains a description of printing failure but it's the most likely I could find:_**

_This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(12dc.564): Access violation - code c0000005 (first/second chance not available)
*** WARNING: Unable to verify timestamp for ntdll.dll
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
Unable to load image C:\\Program Files (x86)\\Schneider Electric\\ClearSCADA\\Lib.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Lib.dll
*** ERROR: Module load completed but symbols could not be loaded for Lib.dll
eax=00000000 ebx=00000000 ecx=14713a80 edx=80000000 esi=00f7c468 edi=000004d0
eip=77ebf2cc esp=00f7c420 ebp=00f7c48c iopl=0 nv up ei pl nz ac po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200212
ntdll+0x2f2cc:
77ebf2cc c21000 ret 10h_

**_Any suggestions what can be done to solve problem? Thank you in advance._**

___________________

bevanweiss:
So you're using PCL6 for the print driver, are there other options that you could install and try here?

The reason for the sizes being different is...
Your screen resolution will likely be something like HD 1920x1200, the resolution that a printer advertises could be as high as 2400x1200DPI. That means that if you're printing on an A4 page it might be up to 19848x14028, or 121x more data points than the screenshot.
Not entirely true numbers depending on the printer driver etc of course, but it gives you some idea as to why it *might* be bigger.

I would try the following steps:
1. Try with a different printer driver (but the same printer). If you can use a postscript driver it would be good, or PCL5 if that is available
2. Try it with a different ViewX client. Install this on a different computer / VM and try that with the same printer driver (if you can vary between x86 / x64 and printer drivers that would be best)

I would also raise this with Schneider Tech Support, as a crash is never good, so should be fixed up on the Schneider side. But trying to find what triggers the crash will make this happen faster.