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.
I was under the impression there is a specific IP you need to have. It would take me some time to find out exactly what, but I don't think it ends in 45...
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
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.
I don't see why that wouldn't work. As long as your IT can manage it there shouldn't be any problems; talk with them about your concerns and maybe they'll explain why it works, or you'll blow their mind and they'll have to think of another way.
As long as works, thumbs up to you!