Need Help!- HAAS MEMORY

[hoff]

HAS ANYONE BEEN ABLE TO INSTALL EXPANDED MEMORY IN A HASS MACHINE WITHOUT PAYING HAAS TO DO IT?

[serviceman]

you can really only do it on the older processors that have sockets unless you are good at soldering surface mount chips.

[Digitech]

Hi,

You can get USB-RS232 product which can be used on any serial interface & you can activate drip feed mode.

It is simpler & safer way.

Or else, go for DNC Software

Regards,

Deepak Bodhani
www.digitech-engineers.com

[Rocko1]

What would be considered an older processor like one on a 98 VF3?

[Digitech]

Originally Posted by Rocko1 What would be considered an older processor like one on a 98 VF3?

Hi,

If 98 VF-3 supports drip feed, you can go for DNC Software. Connect any PC to RS-232 port of VF-3 (The top side D connector) through one Opto-Isolator. You can read more on Opto-Isolator on our web site digitech-engineers.com

If drip feed is not supported by your machine, go for the other option.

- Deepak

[gar]

080131-0809 EST USA

DNC (drip feed) existed on 1993 machines, but Xmodem did not.

.

[Digitech]

Originally Posted by gar 080131-0809 EST USA DNC (drip feed) existed on 1993 machines, but Xmodem did not. .

Hi,
HAAS drip feed mode will work with either RTS/CTS or X-on/Xoff
You do not need Xmodem any way. You can use our WIN-COM Software.
- Deepak

[Digitech]

Originally Posted by gar 080131-0809 EST USA DNC (drip feed) existed on 1993 machines, but Xmodem did not. .

You need to enable parameter no. 55 in HAAS for DNC.
- Deepak

[gar]

080201-0804 EST USA

True that drip feed (DNC) works with either XON/XOFF or RTS-CTS.

The major point of XMODEM is that it is an error detection and correction means that provides some advantage over simply using single parity bit checking on a character by character basis with no correction of any type.

Suppose you use single bit parity and the system receiving the character halts on a parity error. This has probably protected you from a potential crash, but the program stops.

Also suppose for whatever reason you lose a whole character and no parity error, and it was a decimal point. Now you may have a major crash. We have a customer with this kind of problem. XON/XOFF or RTS-CTS does nothing for you. These simply modulate the flow of data and nothing to do with noise induced errors.

XMODEM is a communication protocol that sends a fixed and known block of characters including a checksum. A data block is sent from a source to a destination and at the destination there must be a checksum match. If the match is good, then an OK acknowledgement is sent to the source and the source sends the next block, and so on. If the match is wrong, then a NOT OK message is sent to the source and the source resends the block. There is a count limit on the number of retries on the same block. When this is exceeded all communication is halted.

XMODEM will catch missing character errors as well as other random errors. Furthermore, XMODEM checks more of the system from some place within the source computer to some place within the destination. Usually the block of data goes into some buffer memory in the destination to have its checksum verified. The nearer this is to the final memory the better. A simple parity error check is usually only between the source and destination UARTs. Thus, more circuitry is checked with XMODEM than with a simple parity check.

The simple form of XMODEM used by HAAS does not have powerful error checking, but it is much better than the simple parity check between the UARTs.

.

[Digitech]

Originally Posted by gar 080201-0804 EST USA True that drip feed (DNC) works with either XON/XOFF or RTS-CTS. The major point of XMODEM is that it is an error detection and correction means that provides some advantage over simply using single parity bit checking on a character by character basis with no correction of any type. Suppose you use single bit parity and the system receiving the character halts on a parity error. This has probably protected you from a potential crash, but the program stops. Also suppose for whatever reason you lose a whole character and no parity error, and it was a decimal point. Now you may have a major crash. We have a customer with this kind of problem. XON/XOFF or RTS-CTS does nothing for you. These simply modulate the flow of data and nothing to do with noise induced errors. XMODEM is a communication protocol that sends a fixed and known block of characters including a checksum. A data block is sent from a source to a destination and at the destination there must be a checksum match. If the match is good, then an OK acknowledgement is sent to the source and the source sends the next block, and so on. If the match is wrong, then a NOT OK message is sent to the source and the source resends the block. There is a count limit on the number of retries on the same block. When this is exceeded all communication is halted. XMODEM will catch missing character errors as well as other random errors. Furthermore, XMODEM checks more of the system from some place within the source computer to some place within the destination. Usually the block of data goes into some buffer memory in the destination to have its checksum verified. The nearer this is to the final memory the better. A simple parity error check is usually only between the source and destination UARTs. Thus, more circuitry is checked with XMODEM than with a simple parity check. The simple form of XMODEM used by HAAS does not have powerful error checking, but it is much better than the simple parity check between the UARTs. .

Yes. Xmodem is always better. If your older HAAS does not have Xmodem I do not think, any other external software will give you the same effect.

[gar]

080102-0817 EST USA

Digitech:

That is correct for any problem causing the error within the CNC system.

I believe that usually the whole character loss problem can be attributed to problems within the CNC. Likely a buffer or interrupt problem.

.

[HuFlungDung]

I was researching this "Xmodem" on wikipedia the other day to try to discover what it was that makes it better.

Xmodem appears to have begun without any standard except a dead simple communication protocol without any checking at all. So how or what standard of Xmodem is 'the good one' and how would one know what one is getting by selecting it?