Works great Have a look : http://www.emastercam.com/cgi-bin/ultimate...t=006787#000000

but you can save MCX Than convert it to Iges

wELCOME TO THE FORUM U can use file->save some function

I have a project kind of like that. How are you going to finish that once you've machined it? ~~~~~~~~~~~~~~~~~~ ????

Check for flow control Xon -Xoff settings on both ends (pc and machine ). You also can have not full cabling (4 wires instead of 8 ) and will not be able to set hardware flow control ~~~~~~~~~~~~~~ Software flow control Both software and hardware flow control need software to perform the handshaking task. This makes the term software flow control somewhat misleading. What is ment is that with hardware flow control, additional lines are present in the communication cable which signal handshaking conditions. With software flow control, which is also known under the name XON-XOFF flow control, bytes are sent to the sender using the standard communication lines. Using hardware flow control implies, that more lines must be present between the sender and the receiver, leading to a thicker and more expensive cable. Therefore, software flow control is a good alternative if it is not needed to gain maximum performance in communications. Software flow control makes use of the datachannel between the two devices which reduces the bandwidth. The reduce of bandwidth is in most cases however not so astonishing that it is a reason to not use it. Two bytes have been predefined in the ASCII character set to be used with software flow control. These bytes are named XOFF and XON, because they can stop and restart transmitting. The bytevalue of XOFF is 19, it can be simulated by pressing Ctrl-S on the keyboard. XON has the value 17 assigned which is equivalent to Ctrl-Q. Using software flow control is easy. If sending of characters must be postponed, the character XOFF is sent on the line, to restart the communication again XON is used. Sending the XOFF character only stops the communication in the direction of the device which issued the XOFF. This method has a few disadvantages. One is already discussed: using bytes on the communication channel takes up some bandwidth. One other reason is more severe. Handshaking is mostly used to prevent an overrun of the receiver buffer, the buffer in memory used to store the recently received bytes. If an overrun occurs, this affects the way newcoming characters on the communication channel are handled. In the worst case where software has been designed badly, these characters are thrown away without checking them. If such a character is XOFF or XON, the flow of communication can be severely damaged. The sender will continuously supply new information if the XOFF is lost, or never send new information if no XON was received. This also holds for communication lines where signal quality is bad. What happens if the XOFF or XON message is not received clearly because of noise on the line? Special precaution is also necessary that the information sent does not contain the XON or XOFF characters as information bytes. Therefore, serial communication using software flow control is only acceptable when communication speeds are not to high, and the probability that buffer overruns or data damage occur are minimal. Hardware flow control Hardware flow control is superior compared to software flow control using the XON and XOFF characters. The main problem is, that an extra investment is needed. Extra lines are necessary in the communication cable to carry the handshaking information. Hardware flow control is sometimes referred to as RTS / CTS flow control. This term mentions the extra input and outputs used on the serial device to perform this type of handshaking. RTS / CTS in its original outlook is used for handshaking between a computer and a device connected to it such as a modem. First, the computer sets its RTS line to signal the device that some information is present. The device checks if there is room to receive the information and if so, it sets the CTS line to start the transfer. When using a null modem connection, this is somewhat different. There are two ways to handle this type of handshaking in that sitiuation. One is, where the RTS of each side is connected with the CTS side of the other. In that way, the communication protocol differs somewhat from the original one. The RTS output of computer A signals computer B that A is capable of receiving information, rather than a request for sending information as in the original configuration. This type of communication can be performed with a null modem cable for full handshaking. Although using this cable is not completely compatible with the original way hardware flow control was designed, if software is properly designed for it it can achieve the highest possible speed because no overhead is present for requesting on the RTS line and answering on the CTS line. In the second situation of null modem communication with hardware flow control, the software side looks quite similar to the original use of the handshaking lines. The CTS and RTS lines of one device are connected directly to each other. This means, that the request to send query answers itself. As soon as the RTS output is set, the CTS input will detect a high logical value indicating that sending of information is allowed. This implies, that information will always be sent as soon as sending is requested by a device if no further checking is present. To prevent this from happening, two other pins on the connector are used, the data set ready DSR and the data terminal ready DTR. These two lines indicate if the device attached is working properly and willing to accept data. When these lines are cross-connected (as in most null modem cables) flow control can be performed using these lines. A DTR output is set, if that computer accepts incomming characters. ~~~~~~~~~~~~~~~~~~~~~~~~ http://www.lammertbies.nl/comm/info/RS-232_flow_control.html HTH BR

Mastercam art can do it. The function is called textures Use this dialog box to apply a randomized textures operation to closed contours you select in the graphics window. You can apply the texture to the inside and outside of one or more chained boundaries, as well as between nested chains. All randomized textures are built from arrayed ellipses that you modify using the fields in this dialog box. The ellipses can be stretched, overlapped, randomized, and offset to make many new and interesting textures. You can choose from a list of standard pre-defined texture styles, including those resembling stones, hand-carving, spheres, elongated ellipses, cords in a vertical or horizontal orientation, and others. Or, you can create your own texture by modifying an existing texture style to achieve a specific pattern, and then saving your settings to a preset file. Tip: All of these parameters work together to produce the randomized textures Art surface operation. Try using the default settings for a standard Texture Style first, and view the resulting effect. Then use the Art Manager to edit the operation's parameters, and regenerate the Art model. Repeat until you get the desired result.

It would have no effect ,I consider . This is appropriate fluctuation ,JMHO

I would not advice high RPM . At least not more than 20000 . I would consider such a mill extra long and unrigid For mill 0.005 mm on copper taking 0.001 mm height I would run it s20000 F3 or S8000 F2 (METRIC)

hARDMILL . tHIS PLACE ROCKS . Jay . I will download ASAP Many thanks rof all yoru repyl !

I mostly looking not omly for the parts ,but for ideas Last time my 5 axes works turn to become more complex Example of 5 axes fixture

Thank you .guys

From what I heard Agie is more accurate than ONA I used And it was reasonably accurate too . BTW I think your opeartor means your cuts get not completly vertical . In this case you have ways to setup your upper and lower nozles .

Hi ,folx ! I am looking for various jacks designs and other fixture elements like bi- directional clamps and so on. I would be glad if you `ll recommend internet sites and catalogs . Messing up now with lot`s of complex fixtures ,were trivial decisions are not a way

Besides, working at home is much better. They won't allow me to drink beer at work. [Wink] ~~~~~~~~~~~~~~~~~~` Drinking at fishing is much better . And it is usually vodka

Looks like you have a lot of spare time

Well ,I am sorry . As for yelling ,I was not . I was in the opposite caps lock !

Ok . So what does it prooves ? That I am only human/inhuman/ , not ideal ,as all of you . Rather funny ,though ! Randy ,dig more !

ze, you can/t take a little ribbing, can you, always right and never wrong... ~~~~~~~~~~~~~~~ I never said I always right . I may be always wrong

I UNDERSTAND WHAT ? ThIS QUESTION RElated to ver 9

You can mill STL file as it is without conversion ,do you know ?

Thank you ,Pete ! I starting use hide heavilhy now . Never used before Alt+ and Alt- looks good for me

You can not make successful hides ,I`ve checked

I can do it now ,creating temporal group . I want to make less unnessesary steps

That`s what I need . I like to have an option to make hide couple of times in succession . Like leave on screen all entities of specific color , Then leave all arcs than leave some of them Unhide will ubhide all the entities as it is now

This was my last reply to the thread . I said enough . Anyway I dont think I`ve done with X . I will migrate in appropriate time . I don`t see a problem with migrating to X . I play with from time to time . I simply do not wish to do it now .