- #PROLIFIC USB TO SERIAL DRIVER 3.3 2.105 DOWNLOAD HOW TO#
- #PROLIFIC USB TO SERIAL DRIVER 3.3 2.105 DOWNLOAD INSTALL#
- #PROLIFIC USB TO SERIAL DRIVER 3.3 2.105 DOWNLOAD DRIVERS#
- #PROLIFIC USB TO SERIAL DRIVER 3.3 2.105 DOWNLOAD PASSWORD#
install an older driver).Īfter searching online I came across a few places offering the old driver. grr.įound the solution anyway - "upgrade" the driver to version 3.3.2._ (i.e. would be great if there was a working genuine one for sale but can't seem to find any.
#PROLIFIC USB TO SERIAL DRIVER 3.3 2.105 DOWNLOAD DRIVERS#
Prolific's latest windows drivers basically kill any counterfeit models - giving the Code 10 Error Turns out that the Prolific 2303 USB device I bought was fake.
#PROLIFIC USB TO SERIAL DRIVER 3.3 2.105 DOWNLOAD HOW TO#
any idea how to connect the raw wires to those black connector things?ģ. So it seems that no data is going over the Universal Serial Bus (USB) connection. (Telnet - no IP address even if connected to router or NVR which is double wired to router - so seems like no way to connect) using COM3 -just gives an error message So despite all this, when I go to device manager I still get an error message:Ī device which does not exist was specified."Īlso can't log in via Putty using a serial connection. (powered - but all failed & no IP address provisioned) Then tried with the LAN port's cable connected to: This is how it's connected for anyone interested/ following along. See further on for correct colour coded wiring This is how I wired it up - dodgy + not secure with electrical tape. The 3-pin does plug into the camera's port (see attached pictures). seller is in HK so not able to go back for any claims So I'm wondering - is there anything I can do to get the camera working again?
after speaking on the phone with Hikvision apparently they won't even answer 1 basic question on this Now if I'm honest I bought this camera off a seller in HK - so it's a grey market import into the UK. Reset button on camera doesn't do anythingĬan't find the camera in SADP or any other interface. Tested the NVR's POE port with another camera. so seems to be sending power but no data coming back but on the camera the red light is on + green light flickers
#PROLIFIC USB TO SERIAL DRIVER 3.3 2.105 DOWNLOAD PASSWORD#
only thing I changed was the password on my NVR but all other 7 cams (same model) still work fine Worked fine for about 1 month but in the last day decided to stop working properly. Why can't the programme at least detect that COM5 is there? if there's an issue, it should at least say: Yes, it's there, but there's something wrong.So I've got a Hikvision DS-2CD2742FWD-IS. I checks COM5, but doesn't offer it on the drop down list. The logs say:ġ9:56:05.830 Telescope Instance ID: 1, new: Driver ID: ġ9:56:05.862 Set Connected Set Connected 1 to: True, Alread圜onnected: Falseġ9:56:05.909 ConnectSerial unexpected serial exception System.ArgumentException: The PortName cannot be empty.Īt _Connected(Boolean Connecting) in C:\ASCOM Build\Export\ASCOM.Utilities\ASCOM.Utilities\Serial.vb:line 520Īt _Connected(Boolean value)Īt ()ġ9:56:05.924 Connected set True, id 1, error System.ArgumentException: The PortName cannot be empty.Īt (Int64 id, Boolean value)Īt _Connected(Boolean value)ġ9:56:07.900 Set Connected Set Connected 1 to: False, Successfully removed: Falseġ9:56:07.900 DisconnectSerial force Falseġ9:56:07.900 DisconnectSerial serial Disconnect error System.NullReferenceException: Object reference not set to an instance of an object.Īt (Boolean force)ġ9:56:07.900 Connected set False, id 1, error System.NullReferenceException: Object reference not set to an instance of an object.ġ9:56:10.576 Set Connected Set Connected 1 to: False, Successfully removed: Falseġ9:56:10.576 DisconnectSerial force Falseġ9:56:10.576 DisconnectSerial serial Disconnect error System.NullReferenceException: Object reference not set to an instance of an object.ġ9:56:10.576 Connected set False, id 1, error System.NullReferenceException: Object reference not set to an instance of an object.Ģ0:05:18.439 Telescope Instance ID: 2, new: Driver ID: Ģ0:05:20.549 IdentifySynScan Port COM5 - found nothing When I add COM5 to the 'force' option, it still doesn't appear. I have also downloaded the Skywatcher driver, which I am told is for my mount. I have a Synscan AZ, and the handset is broken. When I get to the properties, there is no COM5. I know this topic is old, but I thought I'd continue as it's one of the only few threads similar to mine.