View Single Post
  #2   Ban this user!
Old 11-22-2009, 06:34 AM
plankman plankman is offline
 
Join Date: Nov 2009
Location: canada
Age: 49
Posts: 11
plankman is on a distinguished road

Hi Hardtool,

I'm running a TNC426CE at work, using TNCRemoNT under Windows XP Pro with no problems. The control is of 1997 vintage and has the piggyback PLC on it and works flawlessly with TNCRemoNT. Our ethernet card was damaged by a spike on an uprotected computer we used as a loader/server for the machines in the shop. Here's what we did to check the ethernet card:

Change the settings in TNCRemoNT to run through a RS232 port. Connect a null modem cable RS232 9 pin to the connector on the side of the control itself in the cabinet and to the computer. Set TNCRemoNT to communicate through the COM1 or COM2 on your computer as needed, set LS/V protocol, and set the baudrate to something reasonably fast - I have a 30 foot test cable and use 115200 without any trouble. You will also have to go into the control to set the RS232 port to match settings. After changing the settings in TNCRemoNT, shut down and restart TNCRemoNT. Hit File|Connect and if everything is running correctly, your control's directories should show after a moment or two on the computer screen in TNCRemoNT.

I suggest trying the RS232 port alternative because depending upon the reason for your old machine dying, it may have damaged the ethernet card on the control. This method will tell you if your card is damaged, and at the very least you'll be able to communicate with your machine again until the ethernet card is replaced. We actually stayed with the RS232 cable and a local machine because it was so handy to have beside the mill!
(I didn't have to wait in line to load a program at the server station).

Just another thought here. A control that old, may need to have its hard drive replaced. We had to do that this past summer. Heidenhain recommends every 5 years. The screen kept freezing up - the machine would be in a contouring program cutting, the screen wouldn't update but would run until the execution buffer ran out and then just sit there. Cycle stop, nothing would work, except a hard power down shutdown/reboot. New hard drive installed, everything worked fine again. Just in case this happens to you. It took the tech about an hour and a half to do the job.

Good luck, and if you need any more help, let me know.
Reply With Quote

 

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361