Heidenhain 151B Drip Feed Problems

[jmccracken]

I'm completely lost ...

I continue to have trouble drip feeding my Heidenhain 151B. Note that I have no problem communicating from PC to controller, and vice-versa, when the controller / TNCServer on the PC are configured as follows:

* Heidenhain 151B controller is set to EXT mode (baud rate has always been set to 2400)
* TNCServer (running on PC) is set to FE (see attached picture of TNCServer set to FE mode)
* Machine Parameter:
M71: 515
MP218: 17736
MP219: 16712
MP220: 279
MP221: 5382
MP222: 168
MP223: 1
MP224: 4

Also, I have no trouble communicating when both the Heidenhain controller and TNCServer are both in ME mode.

My symptoms are that I get a "BLOCK FORMAT INCORRECT" error (see attached picture) when drip feeding a large program, screen says TRANSFER BLOCKWISE, a large program. Specifically it gives this error on line 1221 every single time regardless of whether I am running the program during transfer or not.

Running a program of less than 1221 lines behaves fabulously.

From reading other posts, I see that the Heidenhain controller should be set to FE mode. When I do this, the TNCServer simply says "stopped" as soon as I attempt to either upload, from the PC running TNCServer, or download from the Heidenhain controller. In other words, FE mode (reached by pressing the MOD key) on the Heidenhain controller doesn't seem to work.

What in the world is it doing? What should it do? What should I do to drip feed this (and other) large programs?

Thanks again!

[awemawson]

What cable wiring are you using? Sounds like a handshaking issue. MP222 = 168 equates to software handshaking so in theory it should work with a 3 wire link. I assume it is getting to the point where in internal buffer overflows and gives you the error, however the handshaking should stop it before that. I seem to remember that the software hankshaking uses 'ack' and 'nak' however the values that represent 'ack' and 'nak' are alterable in the parameters (sillly really as they are standardised ascii characters)

[jmccracken]

Thanks for responding. My cable checks out as follows:

(25pin TNC) - <9pin PC>
(2) - <2>
(3) - <3>
(4) - <8>
(5) - <7>
(6) - <4>
(7) - <5>
(20) - <6>

I've confirmed this by ringing out my cable with a multimeter.

Also note that, within TNCServer, I have an ability to "short circuit hardware handshake" (see attached picture). I have tried both with and without this box checked with no difference.

Can you suggest the appropriate machine parameter settings?

[awemawson]

Sadly I no longer have my Interact so I can't just have a looksee and am remembering from about 4 years ago!

You need to download a copy of the TNC151 Interface Description from the Heidenhain site and look at the parameter descriptions. On page 60 it refers to all the ascii control characters being able to be changed by parameter, and I suspect that may be your issue. I do have a copy of my parameters from my TNC151B that I saved years ago if you want to bang me an email at andrew(at)mawson(dot)org(dot)uk I'll send you a copy but remember the machine side of things will differ although the comms side should be the same.

[John Bennett]

Cable should be (DB9-PC to DB25-Control) 2 - 2, 3 - 3 and 5 - 7 (only three wires are needed but you can also have a shield ground if required on one end of cable only). You can look at Cadem.com under DNC for wiring and settings, but they do not support drip feed under cademlite.

[jmccracken]

I wanted to try to give a definitive guide to setting up drip-feeding a Heidenhain 151B based on my (epic) saga of the last few days. I can't say that there aren't other ways to make this work, but the following steps work on my machine.

1. Communications pertinent machine parameter

M71: 515
MP218: 17736
MP219: 16712
MP220: 279
MP221: 5382
MP222: 168
MP223: 1
MP224: 4

2. Cable between PC (9-pin serial / DB9) and Heidenhain 151B controller (25-pin serial / DB25). This equates to a DB9-DB25 null modem cable.

(25pin TNC) - <9pin PC>
(2) - <2>
(3) - <3>
(4) - <8>
(5) - <7>
(6) - <4>
(7) - <5>
(20) - <6>

3. Install TNCServer from Heidenhain website. Setup TNCServer to 'FE' mode and 9600bps (baud). See attached screenshots:

4. Press the MOD key on the Heidenhain 151B controller. By pressing the up or down arrow, find "RS-232-C-INTERFACE" and set it to 'FE' mode. See attached screenshot:

5. While still in the MOD menu, press the up or down arrow, find "BAUD RATE". On my controller, my only choice was 2400. Leave it or set it to 2400. Note that this is the non-sequitur ... and what took me so long to figure out (specifically that the Heidenhain controller is set to 2400 baud while TNCServer is set to 9600 baud). WTF, one might ask ...

6. Turn on the PC and connect to the Heidenhain 151B controller which is in any normal operating mode (manual, automatic run, etc.). TNCServer should say "Ready" in the bottom left corner.

7. In TNCServer, set the "folder" to the correct folder having your programs. Note that ISO programs (what I'm using) have to be named the 'program number' <dot> 'I'. In this case, program number '1' must be a text file named "1.I". I'm told that Heidenhain programming language uses 'program number' <dot> 'H'.

Now, you're ready to drip-feed and run programs. Some notes:

* My controller loaded around 1700-lines of code before it stopped and waited for the controller to ask for more lines of code.
* I was getting a "BLOCK FORMAT INCORRECT" error at around line 1225. I spent a long time thinking that it was some sort of error associated with the TRANSFER BLOCKWISE (aka drip feed) function of the controller. Turns out that this error is generated when there is a bad dimension in a G02 or G03 command (in either I, J, X, or Y entries). In other words the controller is smart enough to be testing each line of code as it is entered to see if there are moves which cannot be made ... thus, by getting this error, it was saying that there was a bad line of code in the program rather than a fault in the communication between PC and controller.

I hope this helps someone fighting through this challenge ...

[John Bennett]

Good write-up!

[awemawson]

Presumably TNCServer auto senses baud rate and adjusts accordingly. My current TNC355 allows 9600 to be set on the control.

Glad you found the error.

[gus]

it does not on this level control

[xsa1]

Hi this may sound like a Silly Question but which file has the TNCServer in it cant seem to find the right one on the heidenhain website.

I to will be trying to link this into our TNC151 control.

thanks

JAck

[gus]

it is part of tncremote