VERICUT Users' Forum

vhubbard

Beta User

From: Dallas, TX

Registered: 2004-11-11

Posts: 222

Website

Printer simulation support.

In our control definitions we have all the macro B variables defined.  We are able run probe simulations exactly.  This is extremely valuable when debugging complex probing and measuring programs.

The problem we run into is that the FANUC print utilities are not supported in the .ctl file or macro routines and we have to debug these at the machine. 

We need these to be run in Vericut also.  All we can do is to define these commands as BEGIN_COMMENT or IGNORE so Vericut will process them without causing  errors.

POPEN in Vericut should be able to be mapped to opening a file or message display, as desired.  In the control it opens a memory chanel, RS232, Memory stick, etc.

DPRNT and BPRNT need to be supported and their data output needs to be sent to the file or message screen defined by POPEN.

DPRNT and BPRNT both have similar formatting rules.   These are essentially simple formated print commands.

DPRNT is Ascii
BPRNT is binary

DPRNT needs a xx format definition after a variable to define leading-trailing digits from decimal
BPRNT needs a x format definition that defines number of trailing decimals

Example if #1 is 334.1234567
DPRNT [*VALUE*IS*#1[34]]   prints " VALUE IS 334.1234"
DPRNT [*VALUE*IS*#1[23]]   prints " VALUE IS 34.123"

Valid values used within the [] are:

A-Z

0-9

Macro B addresses for the variable values, #1-33, #100-xxxxx and so on. These should be predefined in the control.

* is interpreted as a space

/+- are special characters supported. 

NULL variable values cause control alarms

PCLOSE should close the file or message port opened by POPEN.   

See Fanuc Macro B programming sections in the Fanuc manuals for details

jsmillett

Member

From: Chatsworth, CA

Registered: 2005-02-25

Posts: 42

Re: Printer simulation support.

We also use printer output to capture probing results on machines with FANUC and other controls.   Vericut macros to support printing would help considerably! 

In our control definitions we have all the macro B variables defined.  We are able run probe simulations exactly.  This is extremely valuable when debugging complex probing and measuring programs.

The problem we run into is that the FANUC print utilities are not supported in the .ctl file or macro routines and we have to debug these at the machine. 

We need these to be run in Vericut also.  All we can do is to define these commands as BEGIN_COMMENT or IGNORE so Vericut will process them without causing  errors.

POPEN in Vericut should be able to be mapped to opening a file or message display, as desired.  In the control it opens a memory chanel, RS232, Memory stick, etc.

DPRNT and BPRNT need to be supported and their data output needs to be sent to the file or message screen defined by POPEN.

DPRNT and BPRNT both have similar formatting rules.   These are essentially simple formated print commands.

DPRNT is Ascii
BPRNT is binary

DPRNT needs a xx format definition after a variable to define leading-trailing digits from decimal
BPRNT needs a x format definition that defines number of trailing decimals

Example if #1 is 334.1234567
DPRNT [*VALUE*IS*#1[34]]   prints " VALUE IS 334.1234"
DPRNT [*VALUE*IS*#1[23]]   prints " VALUE IS 34.123"

Valid values used within the [] are:

A-Z

0-9

Macro B addresses for the variable values, #1-33, #100-xxxxx and so on. These should be predefined in the control.

* is interpreted as a space

/+- are special characters supported. 

NULL variable values cause control alarms

PCLOSE should close the file or message port opened by POPEN.   

See Fanuc Macro B programming sections in the Fanuc manuals for details

---

Jerry Millett

RobD

Member

From: Connecticut

Registered: 2005-02-07

Posts: 20

Re: Printer simulation support.

I have also been using Vericut to simulate probing.  I find it very useful because it allows me to create (mostly  :wink: ) good probing routines before I get to the machine.   I agree that simulating a printer or creating an output file would also be very useful, because some of the people I work with would like to know what the machine probing results are over time, and debugging my print statements on the machine is not exactly value added activity.

vhubbard

Beta User

From: Dallas, TX

Registered: 2004-11-11

Posts: 222

Website

Re: Printer simulation support.

Vericut 6.2 now supports POPEN/PCLOSE and writes data to a text file.