You are not logged in.
Pages: 1
Offline
Chigishev,
One more hit eh? 8)
Why did you decide to build this your own? Isn´t it natively supported by VERICUT? (I really don´t know: We just got our first machine with Heidenhain and Probing so I need to know how difficult it will be...)
I think CGTech has some sort of support for these cycles as Heids are very common for them... my question: what else your CME is offering that the regular options don´t offer?
The last question is: what is range of cycles you are covering and are you licensing them?
Tks
Daniel
Daniel Santos
Offline
Hello, Daniel!
Yes, one more but not last, not final. I have a wish to insert into my DLL ALL probing cycles of Heidenhain, SIEMENS, FANUC or RENISHAW etc.
Why I did it? Try to use standard control for probing - no one cycles NO WORKING. For word TCH - NullMacro.
Offline
And, Daniel - this forum for you and me? No any members?
Offline
And, Daniel - this forum for you and me? No any members?
Too bad CGTech forum is a ghost town... - I'm a member since 2005 and it has always been like that... :cry:
eMastercam is simply fantastic in terms of interaction... TopSolid forum is even worse than this place...
But lets keep doing our part... who knows we start to write more interesting stuff and then people chime in... Perhaps the problem is that we are boring :wink: - Or maybe the fact some posts are never answered (Despite we had a CGTech employee saying he patrols the forum from time to time looking for unanswered posts) and then people don't have big expectations coming here anymore...
I think in any type of community (virtual or real) the way and frequency members interact with each other defines the volume of activities of this community. We're too shy here... :oops:
Anyway, I'll check with CGTech how far they can go with Heid cycles... depending on their answer, we may be interested in licensing this stuff from you...
Cheers,
Daniel
Daniel Santos
Offline
My first thought also was - Isn't this covered by default macros?
But anyway. Which programming language is used when creating CME DLL:s for Vericut?
Best regards,,
Svante
Svante Eriksson
System owner
GKN Aerospace Engine Systems Sweden
Vericut 7.2.1, 7.3.4, 7.4 - NX 9.0.3
Offline
To create a CME-API dll you can use either C or C++... As about the Heidenhain probing cycles we are currently working to support Heidenhain original cycles directly with no need to create any CME-API... Stay tuned
Mustapha
Offline
VERICUT V731(pre-release) now supports Heidenhain Probing Cycles (from 408 to 431), check this video http://youtu.be/cynF3ptXTuw showing cycles 420 to 431...
Mustapha
Offline
If you run the sample "samples\Probing\hei530_probing_offset_setting.vcproject", the first nc program shows TCH PROBE 417 which updates the Work Offset #5. This Work Offset is then used at line "10 CYCL DEF 7.1 #5".
Then all next nc programs shows you how Work Offsets are updated after probing with corresponding cycles.
Tip: Display the Driven Point Zero axis and see how it moves
Mustapha
Offline
Yes reading from a table, like "FN 18: SYSREAD Q7 = ID500 NR1 IDX4" is not supported yet with "standard" VERICUT requieres a specific DLL. Please contact your local CGTech support for more information. But TCH PROBE 412 is supported
Mustapha
Offline
Any progress with hei530_probing FN 18: SYSREAD Q7 = ID500 NR1 IDX4
Offline
I believe it is supported, if you MDI "FN 18: SYSREAD Q7 = ID500 NR1 IDX4" in a Heidenhain sample you will not get any error. However no value is returned into Q7. We will need a sample to do testing
Mustapha
Offline
How should I send a sample and to whom? I really would like to get further on the sysread and syswrite sooner than later. Please assist.
Offline
Go to https://www.cgtech.com/vericut_support/ => if not in the USA, select the appropriate country from the selection drop-down at the top right-hand corner of the page => use one of the available support request options displayed on the page.
Stefan Pendl
Systemmanager CAD/CAM
Windows 10 x64 Edition, Vericut 9.0
Offline
Pages: 1