Problems with HeidenHain TNCRemo and Windows 7
Close
Login to Your Account
Results 1 to 9 of 9
  1. #1
    Join Date
    Feb 2004
    Location
    Napa, CA
    Posts
    2,632
    Post Thanks / Like
    Likes (Given)
    45
    Likes (Received)
    698

    Default Problems with HeidenHain TNCRemo and Windows 7

    I've run this on XP for years with no problems. I am forced to use Windows 7 now as OneCNC no longer runs on XP. I cannot get TNCRemo to work on Windows 7. I've tried both 3 and 3.3 revisions with similar results. It installs with no errors, everything looks good but it will not transfer files to the control. If the online converter is enabled and I try to transfer to the control, I get and error (can't download the DLL) from 3.0, and a different error (install error, can't activate the DLL) from 3.3 - these may be the same thing I suppose. I can transfer from the control, and it appears to be fast whether or not the online converter is active.

    If I try to transfer to the control with the online converter not active, it appears to attempt to transfer very slowly, makes very little progress, and then fails and looses the connection. The file on the control is created but will show zero bytes. In fact there are some lines transferred, then a bunch of error lines, then it ends. This file cannot be deleted from the control ("Access denied") until the control is restarted.

    I can go back to exactly the same version of TNCRemo on XP and it still works fine.

    Any ideas?

  2. #2
    Join Date
    Feb 2004
    Location
    Napa, CA
    Posts
    2,632
    Post Thanks / Like
    Likes (Given)
    45
    Likes (Received)
    698

    Default

    I discovered a couple of things. One is that there are some write permissions that Win7 has that prevent the app from writing into the TNCRemo folder, this is why it could not download the DLL and create the machine specific online transfer folder. It will not let me change the permissions (or perhaps I don't know how), but installing the program at the C;/ level allows it to write the file and folder. That eliminated the DLL error. Now the behavior is normal, says it is transferring the file with bogus progress indication (that is normal), it completes in about the right amount of time, but then goes off the rails, loses the connection. The file written to the control is again locked, showing 0 bytes. It cannot be accessed without rebooting the control, when that is done the file exists but is empty.

  3. #3
    Join Date
    Jun 2015
    Country
    UNITED STATES
    State/Province
    Colorado
    Posts
    571
    Post Thanks / Like
    Likes (Given)
    1167
    Likes (Received)
    230

    Default

    My memory is a bit foggy on TNCRemo but I didn't have any luck with it and Windows 7.

    TNCServer works just fine though. I use it all the time.

  4. #4
    Join Date
    Jun 2006
    Location
    Near Seattle
    Posts
    4,952
    Post Thanks / Like
    Likes (Given)
    3409
    Likes (Received)
    1419

    Default

    @swarf_rat: I'm too far away to see what is really going on, but I ran tncremote on win7 from 2007 until 2018 or so, when I was finally forced to win10 (where it also runs just fine.)
    If I remember I'll look at the version on the shop machine tomorrow - if memory serves you can download it from the heidenhain web site.

  5. #5
    Join Date
    Sep 2009
    Location
    Apex, NC
    Posts
    1,544
    Post Thanks / Like
    Likes (Given)
    1
    Likes (Received)
    761

    Default

    I'm running TNCServer (don't need TNCRemo) on Windows 7 (exactly the same version I run on XP, in fact just copied the file from the XP computer) on a Panasonic CF-51 "Toughbook" laptop with no problem. Note this laptop has a real serial port (Toughbooks are one of the only PC's remaining with a real serial port). If you're using a port emulator, that could possibly be the problem (while they "usually" work, my pc/sofware expert says you can't trust them if some problem is occurring).

  6. #6
    Join Date
    Sep 2002
    Location
    People's Republic
    Posts
    4,456
    Post Thanks / Like
    Likes (Given)
    433
    Likes (Received)
    2709

    Default

    Is it new OS or new computer?
    Serial port or emulator/USB or ethernet?
    Never any problems with 7 or 10

  7. #7
    Join Date
    Feb 2004
    Location
    Napa, CA
    Posts
    2,632
    Post Thanks / Like
    Likes (Given)
    45
    Likes (Received)
    698

    Default

    OK I did fix it this weekend. New OS, not a new computer, Enet.

    2 separate problems: First, TNCRemo must be run in supervisor mode. It installs by default in Programs x86 directory, which is write protected by the OS even from a program installed there apparently. TNCRemo reads the DLLs necessary for the binary translation from the control and writes them to the TNCRemo folder in that directory - except it can't as it is write protected. The error messages from both 3.0 and 3.3 TNCRemo are bogus in this regard, the OS gives no error, just doesn't allow it. You can install it outside of the Programs directory or change the compatibility settings of the program to run in supervisor mode and that problem is eliminated. WindowsXP didn't have these protections. I believe this may be particular to the 426/430 control, later controls do not require this file and earlier ones did not have this feature.

    Second, TNCRemo comm will not tolerate NAT in the outgoing network. This was particularly hard to chase, since files transferred TNC -> EXT worked fine, and files would start the other direction but then go off the rails between a few and a few hundred lines in, corrupting the data and eventually quitting while leaving the file open and undeletable. This was true with or without the binary translation. You must set up your network and firewalls such that NAT (and perhaps other firewall protections) are turned off. The default install of Win7 on this machine had NAT on.

    I also had problems with TNCServer communicating to the other Deckel, but that was a matter of finding the correct driver for the USB/serial converter. The one provided by the manufacturer for Win7 does not work on Win7, but allowing the Microsoft search for a driver eventually found one that did work.

    You'd have to beat me with a stick to make me run Windows10 (though I have to in some limited circumstances). The last stable release of Windows was XP3, sadly some apps these days are no longer running on it.

  8. Likes BugRobotics liked this post
  9. #8
    Join Date
    Sep 2009
    Location
    Apex, NC
    Posts
    1,544
    Post Thanks / Like
    Likes (Given)
    1
    Likes (Received)
    761

    Default

    Regarding Windows 10, also beware that certain old programs may not run on it, while they do work on Windows 7 (a couple of examples: cadkey=nogo, corel=nogo, and old versions of Word are unstable). So, I guess it's off to quarantining yet another PC from Windows "upgrades" and the internet, and get another cheapo for Windows 10 and the internet.

  10. Likes neilho liked this post
  11. #9
    Join Date
    Feb 2004
    Location
    Napa, CA
    Posts
    2,632
    Post Thanks / Like
    Likes (Given)
    45
    Likes (Received)
    698

    Default

    Speaking of old things that don't run on Windows 10, I'm one of them :-). Fortunately I run all of these in VM, so I've got XP3, 7, and 10 all isolated by VM on the same machine.


Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •