hexagon logo
Register Sign in
  • Replies 5 replies
  • Subscribers 15 subscribers
  • Views 82 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
  • As far as I'm understanding from some of those posts, you would need your IP to be within 1 of the controller. So if your controller is 192.168.1.45, your IP would need to be 192.168.1.46.
    That's weird.

    I had some IP related problems with our Optiv a while back. I didn't get the chance to find out why, but I found out, in the BIOS, theres an option for network boot or something, PCI boot? Something to do with booting the PC using the network. Well I disabled that, and it apparently disabled a network card (or the network card?) in such a particular way that I was not able to use the machine, but could still access the web.

    Hex-a-Tech's ended up getting things sorted out, but I imagine they just re-enabled that and made sure the IP address was correct.
    If anything, you could see if someone could remote in and take a look. Save you the waiting time and them a trip
Reply
  • As far as I'm understanding from some of those posts, you would need your IP to be within 1 of the controller. So if your controller is 192.168.1.45, your IP would need to be 192.168.1.46.
    That's weird.

    I had some IP related problems with our Optiv a while back. I didn't get the chance to find out why, but I found out, in the BIOS, theres an option for network boot or something, PCI boot? Something to do with booting the PC using the network. Well I disabled that, and it apparently disabled a network card (or the network card?) in such a particular way that I was not able to use the machine, but could still access the web.

    Hex-a-Tech's ended up getting things sorted out, but I imagine they just re-enabled that and made sure the IP address was correct.
    If anything, you could see if someone could remote in and take a look. Save you the waiting time and them a trip
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement