Hi

I have a few questions regarding videofunctions in NS Designer (and NS8 Screen). I have a system that contains:
1xNS8 Display
1xOmron PLC
1xVideo module (4channel)
2xCameras connected to videomodule
1xCF-Card connected to NS8

I would like to have a screen that contains a videodisplay (fullscreen 640*480). On this screen i would like to have some command buttons so that i can:
-Switch screen to a new screen that contains another videodisplay (other video-channel)
-Switch screen to Menu
-Save image to CF-Card

Is it possible that buttons overlap the videoscreen. Can images also overlap videoscreen? I have read the manual, but i dont really understand what the manual says...

When using the "save to CF-card" feature, is it possible save multiple images to the CF-card? It only seems like i can save 4 different images (1 image/channel)? I would like to save multiple images of one videochannel. But i cant find a way to change the filename after each save...

This is a feature i am also missing with the alarm logg. I would like to be able to save multiple alarmlogs, but that not possible (or is it?)

Regards
Loogi

I do not think you can have buttons on top of the video display. I have some screens set up with buttons behind the video and they work, but you can not see them.

Hope this will help, and maybe someone can offer a better solution.

The NS-CA001 video input card does not allow objects to be superimposed on the video area.

The NS-CA002 2 port video input card does allow objects to be sumperimposed on the video area.

Thanks Jay!

Though it was not the answer i would like to hear... i have the NS-CA001 video module...

I must say that even though the ProFace screens are harder to program, the have more capability once you learn... I am a bit disapointed in Omron-screens...

how could i then use the feature save to cf-card? I would like my user to manually save that, but if i have a fullscreen picture, then i cant have a button for this... If i have a split-picture, then its hard for the user to see so good... Anyone got any suggestions?

Thanks

System bit #24 in the PLC System bits will trigger a video capture. Looks like you will have to use a PLC input.

Video Capture ($SB24)

$SB24 captures the image being displayed and saves it as BMP format on a Memory Card. When

$SB24 is turned ON, the captured data will be output to \LOG\CAPTURE under the Memory Card directory

as XXX_VideoXX_XXX.bmp. If an error occurs during the operation, $SB24 will turn OFF and

$SB47 will turn ON.

The following rules will be used for saving captured data.

The screen number, position of the image, and the file number will be automatically added to the file

name when executing the video capture.

9999 _ VideoLT _ 999. bmp

File Number

The file number will be automatically numbered in order from 001 to 999.

If all numbers are used, the oldest numbered file will be deleted and the newest file will be

saved. (Same procedure as the command button.)

Position of the Image

The position of the image when executing the video capture.

Upper left or none: VideoLT

Bottom left: VideoLB

Upper right: VideoRT

Bottom right: VideoRB

Screen Number

The normal screen number when the video capture was executed will be automatically added

(0000 to 3999).

THANKS Jay! (yay!)

Great info! Is it perhaps possible to do the same thing (save multiple files) with the alarm/history-log?

Helps to read the manual!

Save Alarm/Event History ($SB33)

$SB33 saves alarm and event history data. When $SB33 is turned ON, the alarm and event history

data is saved to the Memory Card as a CSV file. Once the data has been saved, the system automatically

turns OFF $SB33.

Alarm data is output to log\Alarm.csv (classified into high, middle, and low level alarms) and event data

is output to \log\Event.csv files on the Memory Card. The file names are fixed, and files previously output

to the Memory Card will be overwritten.

If no alarms have accumulated, alarm data will not be saved. ($SB33 will turn OFF and $SB47 will not

turn ON.)

If no events have accumulated, event data will not be saved. ($SB33 will turn OFF and $SB47 will not

turn ON.)

If an error occurs during the save operation (e.g., the Memory Card is not in place, there is insufficient

free disk space, or the Memory Card is damaged), $SB33 will turn OFF and $SB47 will turn ON.

No error message will appear on the screen, however, when an error occurs.

If $SB32 and $SB33 turn ON simultaneously, initialization will be executed first. For this reason,

Alarm.CSV and Event.CSV files will not be created.