hexagon logo
Register Sign in
  • Replies 5 replies
  • Subscribers 15 subscribers
  • Views 80 views
  • Users 0 members are here
Options
Related

IP Address conflict with Microcontroller !

rickylorduk
Hi Guys, can anyone help me out please?
I am a PCDMIS nooob, and I have just waited a month for a site visit to fix our Optiv that scrambled itself on an upgrade to 2017.
While we were waiting we had a clean install of win 7 done (to update to 64 bit). (just for info)
Eng turned up and installed PCDMIS 2017 (don't know why not 2018 like the Pioneer next to it, thats why we had 64 bit OS put on, because thats why we were stuck on 2017)
Eng also did the Calibration and left a report that all was hunky dory except the network connection that was probably suffering an IP address conflict.
It turns out the conflict is with the second network connection that goes to the embedded microcontroller in the CMM.
I need the machine on the network of course. IP of the PC connection to Embedded is 192.168.1.45 (don't know ip of the Microcontroller)
PC network card DHCP in the range of 192.168.1.x 255,255,255,0 , it is not feasible to change the the whole network address range, so
How do I change both ends of the embedded connection, or
Does anyone think I can resolve this with a ROUTE comand?
Machine works fine until you connect to the network, and PC works fine on the network until you fire up PCDMIS (error loading HSL.dll, paths have changed etc.)
Yes I have tried contacting support, still waiting for the call back, and I can't wait another month for a site visit.

Thanks
Ricky
Parents
  • Hi Jester,
    support ticket is open, still waiting for the call !

    In the mean time, we have the mc working, I stated the wrong ip address abaove, it was actually:-
    Microcontroller IP 192.168.1.45
    PC - to micro IP 192.168.1.5 (fixed IP, 255.255.255.0, no gateway)
    PC to net DCHP from range of 192.168.1, 40 to 192.168.1.100

    MC worked fine off the net, PCD could find the micro.
    Connect to the net and now when PCD locks for ...1.45 the request goes out to the net because of the ROUTE command added on connection.

    I.T. Dept would not change the DCHP range in the router, but they excluded ...1.45 from the range.
    Then had me connect the micro directly to the network !

    It works because PCD looks on the net for the micro and finds it, ( and there will not be another device with ...1.45)
    I am just a bit nervous of doing it this way because of timings, traffic etc.

    Thanks for your help
    Ricky
Reply
  • Hi Jester,
    support ticket is open, still waiting for the call !

    In the mean time, we have the mc working, I stated the wrong ip address abaove, it was actually:-
    Microcontroller IP 192.168.1.45
    PC - to micro IP 192.168.1.5 (fixed IP, 255.255.255.0, no gateway)
    PC to net DCHP from range of 192.168.1, 40 to 192.168.1.100

    MC worked fine off the net, PCD could find the micro.
    Connect to the net and now when PCD locks for ...1.45 the request goes out to the net because of the ROUTE command added on connection.

    I.T. Dept would not change the DCHP range in the router, but they excluded ...1.45 from the range.
    Then had me connect the micro directly to the network !

    It works because PCD looks on the net for the micro and finds it, ( and there will not be another device with ...1.45)
    I am just a bit nervous of doing it this way because of timings, traffic etc.

    Thanks for your help
    Ricky
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement