helloWorld . deskProto + BIESSE .

I'm super excited for my new... "BIESSE ROVER A 1332 5-AXIS CNC MACHINING CENTER" arrival .

SO some questions for you guys ( the Biesse support is horrific ) :

Do you know of any problems to expect regarding the connection process with deskProto ?

Will the exported tool-path code just .. work ?

Will the biesse program give me the option to check the path to avoid a possible crash ?

Any tips/tricks you want to share ?

Has anyone altered his Post Processor to Better fit his Rover A ??
(if so - can you post it - in your reply ? )


Thanks guys

Hi Inigo,

As you will have seen in the DeskProto trial version there is no Biesse in the list of machines that you can choose from.
In most cases then the best you can do is select the machine called "ISO standard G-codes" (and automatically also that postprocessor), as almost any CNC machine will accept some G-code dialect.

Though when I just checked the Biesse website I could not find any remark about G-codes. You will have to try if you can find some import option in the Biesse software. As we have never seen that software I also cannot tell you about any checks that it may offer.

In case needed you can later fine-tune the postprocessor in DeskProto: the Help function will assist you, and you can of course also ask us for help.

Best Regards, Lex.

BUT -
I have found this file notes about the correct way to edit the standard iso code.
( i have more info - should you need it )

see if you can add a biesse "PP" out of this info :
I hope my 5Axis will work with your program..so we can buy Deskproto asap.

===================


NOTES ON THE STRUCTURE OF XNC LIST FILES:


The list is an ASCII file with the following characteristics:
The first line must be "[DISTINTA : RIGHE]".
The lines end with a line feed.
The fields are separated by a comma.
AAA,ALFA,1,0,$ A=50 $,
| | | | |
| | | | |
| | | | COMMENT field
| | | |
| | | PIECE COUNTER field
| | |
| | QUANTITY field
| |
| PROGRAM field
|
LABEL field
Example
[DISTINTA : RIGHE]
AAA,ALFA,1,0,$ A=50 $,
,PANCA,1,0,,
,ITALY,1,0,,
,GATTO1,1,0,,
,COLUMBIA,1,0,,
,TORO,1,0,,
,JMP AAA,9999,0,,


NOTES ON THE STRUCTURE OF XNC PROGRAM FILES :

The structural specifications of a CNI program are listed below.
Please see the programming manual for the syntax in the program to be run.
Program, subprogram or fixed cycle files all have the same structure.
They are divided into paragraphs, and each paragraph finishes where the next one begins. The beginning or end of a paragraph is determined by the presence of the character [ in the first column of the line.
All the lines, which must never be longer than 2000 bytes, must end with \n (line feed) and not with \r\n (return/line feed).
The beginning of a paragraph must start from the first character on the line, and it must only contain the name of the paragraph in brackets [ ] .
The names of paragraphs and the key words must all be in capital letters, and must be the only ones on the line.
The first paragraph of the file is obligatorily the comment; it must start at character 0 of the file.
Comment string is a comment inside the file. It must not start with [ and it must be one line only.
Example:
[COMMENTO]
Comment string
The second paragraph contains the list of sections present and their address within the file. There will be a paragraph of this type for each centre.
Example:
[CENTRO01] PARAMETRI=000000213 UTENSILI=000000309 LABELF=000001414 LABELC=000001401 FORATURA=000000343 CONTORNATURA=000000324
TABELLEFORI=000000882
CONFASSIST=000001427
ATTREZZAGGIO=000001444

[CENTROnn]

This is the name of the paragraph that defines the addresses of the various sections in the program.
nn are the two figures that indicate the centre number to which the list of sections refers.
The first centre is 01; if the machine is a single centre one, there will only be one list.
The section is a paragraph in the program containing machining information.
The word section is used as a synonym for paragraph.
Each of the sections must always be present in the file, even if it is empty.

The list of sections has the following structure:
CHIAVE=OFFSET where
CHIAVE is the name of the section
OFFSET is the order number of the character with which the section starts, that is to say the address of each section in bytes starting from the beginning of the file, where the first character has offset 0. It is a fixed length numeric string of 9 characters with significant figures on the right and 0 on the left. It points to the start of paragraph character [.
The paragraphs pointed by this address are identified by the name, which is written as follows: CHIAVEnn in which nn is the centre number.


SIGNIFICANCE OF EACH SECTION IN RELATION TO CENTRE 1:
Parameters section
[PARAMETRI01]
N10 G71 HC=1 LY=560 LZ=18BLO=0 ACC=0 RUO=0 PRS=1 LX=704
%
Contains the panel dimensions and in general the first program step. It can contain fixed cycle call-ups.
It must all be on a single line, and must contain a second line with %.
If the program is for a multiple centre machine, this section must be repeated with the same contents for all centres.


Tool section:
[UTENSILI01]
.
.
%
Contains the names of the tools used for the various tool change operations carried out during running of the program and any subprograms that may be called up by it.
Each line contains the name of a single tool.
This section can be empty only if the machine haven’t the Multistore magazine.
Profiling section:
[CONTORNATURA01]
.
.
% Contains the ISO instructions that define machining of the piece.
Each step must be on a single line.
The section must end with %.


Profiling section:
[CONTORNATURA01]
.
.
% Contains the ISO instructions that define machining of the piece.
Each step must be on a single line.
The section must end with %.
Boring section:
[FORATURA01]
%
This section is for use by CNI only. It must be present and empty for programs produced externally.



Bore table section:
[TABELLEFORI01]
%
This section is for use by CNI only. It must be present and empty for programs produced externally.
Profiling label section:
[LABELC01]
.
.
%
Contains the labels used by the jumps of internal subroutine call-ups, present in the profiling section.
The labels are made up of numbers between 1 and 49.
The format is as follows:
label1=OFFSET1
label2=OFFSET2
in which offset is the displacement in bytes starting from the beginning of the section.
The first character in the section is the [ of CONTORNATURA01.
Boring label section:
[LABELF01]
% This section is for use by CNI only. It must be present and empty for programs produced externally.


Assisted editor configuration section
[CONFASSIST01]
%
Contains the instructions in A.E.P.L. defining any data request box.
For further clarification of the language structure, please see the relevant manual .
Tooling configuration section:
[ATTREZZAGGIO01]
%
Contains the section with any mobile tables tooling associated with the program .
It will vary according to the machine configuration.
This section can be empty.
Customization section:
[CUSTOMSEZ01]
%
Contains the section for information about particular application.
This section can be empty.


Closing file
The file is closed with [ ] .





Example of a file for single centre machine.

[COMMENTO]
EXAMPLE PROGRAM
[CENTRO01]
PARAMETRI=000000212
UTENSILI=000000280
LABELF=000000605
LABELC=000000586
FORATURA=000000553
CONTORNATURA=000000305
TABELLEFORI=000000568
CONFASSIST=000000618
ATTREZZAGGIO=000000635
[PARAMETRI01]
N10 KA=1 LX=1000 LY=600 LZ=18 HC=1 G71 PRS=1 Z=PRK
%
[UTENSILI01]
PNT1
PNT2
%
[CONTORNATURA01]
N20 PAN=1 ST1="PNT1" L=PCUA
N30 PAN=2 ST1="PNT2" L=PCUA
N40 X5 Y5 Z=PRK TP=1 PRF=5 G40 L=PON M55
N50 L:1
N60 L=POFF
N50 X200 Y200 Z=PRK TP=1 PRF=5 G40 L=PON M55
N60 L:1
%
:1
N70 XI100 G1
N80 YI100 G1
N90 XI-100 G1
N100 YI-100 G1
%
[FORATURA01]
%
[TABELLEFORI01]
%
[LABELC01]
1=174
%
[LABELF01]
%
[CONFASSIST01]
%
[ATTREZZAGGIO01]
%
[ ]



==============

http://tinyurl.com/biesseFile001

http://tinyurl.com/biesseFile003


The first File is an example a biesse approved gCode .
The second pdf file is an explanation on the dxf(2D) layer formalism .. ( I wish this too will be an exporting option inside deskProto :)

Hope these will help .

Have a nice day
I.Montoya

Hi Inigo,

I am afraid that this will be a very complicated job.

The "NOTES ON THE STRUCTURE OF XNC LIST FILES" did not help much: in an NC program file I expect to find a large series of movement commands, one command per line, with on each line a number of coordinates to define the movement. The XNC file does not show anything of the kind, only somewhere halfway a section with remark "Contains the ISO instructions that define machining of the piece."

Same for the sample file on your later post (5AxesBiesseRover_gCodeSample.ISO): only after line 700 I see a few familiar lines, like
N290 G1 Y=22.459 Z=-22.745 B=-40.685
so after 700 lines of completely unknown stuff.

This is not something that we can configure in the DeskProto configurable postprocessor, sorry about that.
Just copying the first 700 lines without a clue about their meaning does not seem like a good idea.

You could try if you can find any users combining a Biesse machine with a standard CAM program, and ask how they do it. Though I know that some machine suppliers force that their machines can be used only with their own software. In my opinion not wise, however that is of course their decision.

Lex.

I understand you are looking for a different information.
Can I send you some more PDF files regarding the subject - and you will find the info you need ?

The thing is - I think The DeskProto program is the easiest to answer my needs but I obviously cant edit a new PP on my own.

So - Is it OK to privately send you all the links (pdf+iso codes) - and you'll find the correct info ?

If so - please mail me to 890890 at gmail dot com

Thanks

I.

Hi Inigo,

In DeskProto it is possible for any user to create and change postprocessors. This is called a 'configurable postprocessor', and can be done in the Library of postprocessors (Options menu).

My problem is not so much the lack of information. It is that the structure of the Biesse files is so completely different from the structure of standard NC files that it would cost us many days to understand it and find out if it is possible to write such files from DeskProto.

As Biesse created this problem, and as the Machine will be about 100 times as expensive as the lowcost DeskProto program, I feel that it is up to Biesse to solve this issue for you. If they have a good set of instructions for connecting a standard CAM program to their machine then I can give it a try.

Lex.

Hi Inigo,

Have you talked to Biesse about the new BSolid software??