My HPS 50 will not connect with my Windows 7 computer. The velleman software displays the grid but it will not connect to the HPS50.
Windows 7 cannot find the required driver. Please can you tell me where I can download a suitable driver?
Make sure the driver (HPS50.inf) file which comes with the software package is installed prior to the launching the scope software. If Windows 7 doesn’t ask for a driver when the HPS50 is plugged in, you can open your Device Manager (Start -> Run… -> devmgmt.msc), look for the HPS50 and update its driver.
Thank you. I have now installed the driver, HPS50.inf and my Windows 7
computer (32 bit) now recognises that the driver is installed. But when
I run the velleman software to display the grid and use file > connect,
the connect window which opens is blank and does not detect the HPS50.
I have been using the SEND > Binary setting all the time.
I have just checked and tried again but I still cannot get
your software to connect to my HPS50. Windows 7
reports that the driver is correctly installed and working.
But no device is displayed in the device window when I do
file > connect.
Helou!
For first Scuse me please for my English!
I get today a new HPS 50 Scope and i try to learn it. My PC have Windows 7 and vith your driver don’t work.
When i plug in USB cable ask me for device …
Thanks
Heloo!
Now work onli for 2-3 second and remain bloked.
If I close the aplication; and after that I open again the HPS50 SoftWare Set the Com and “CONECT” Work again for two second.
Control Panel said now that COM work property.
After That I try to instal in my home computer (acer mini one) with Windows XP
Control Panel said now that COM 10 work property. But when I try to conect he said
"CAN’T conect the device.
Heloo!
Again. I am very disapoint because I buy 2 pcs. Hps 50 for Work (for o school wen I work) .
I had helped by our IT-specialist ; and it isn’t normal to have problem with the instal a new device!!!
In the last 20 Years i Instal hundreds of periferical device …
The computer chois the COM 8 because he know that the first 7 COM is in use.(at the DELL-computer INTEL I5 core with Windows 7Pro). How I said before, now (after i instal the driver from you said)when I start HPS50 program , I CONECT on COM8 and for 1-2 seconds onli a screen if i start dhe HPS vith an signal i can see on the PC. I try to send With the MEMORY KEY presed a long time. The scope write in right corner " Transmit" but nating hapend.
The port COM 9 is right set for 38400 Baud; 8 bit…etc the scope is set in Binary mode…I don’t know what I can do.
That HApend on Window 7PRO
AT home on two pc with Windows XP can,t conect the device (after instal the dryver) and is set on a port witch is free and corect set the 38400 baud rate…ETC.
Allredy I waste 2 Days with this problem… You must think on that.
Best regards Stefan
You are 100% certain that the HPS50 is installed under COM8 and that no other software is occupying the port. Why are all other ports in use?
You see a moving signal on the screen of the HPS50 for 1 or 2 seconds? Please provide a screenshot if possible of the software when the signal is no longer “visible”/“blocked”
The software does not react to the memory key, screenshots are made in the software itself.
Before you were talking about COM8… there is no way to set the baud rate in the HPS50 software…
The scope and software should work perfectly on Windows 7 Professional Edition. There have not yet been similar cases or problems in the past…
Hello again.
Of corse I am sure that the port COM 8 was free before.
In device manager you can see How in instaled one device (well or wrong with yellow sign) and all device (present or not) when is instled have designed one com witch is sown like “in use”.
Your scope have set 38400 Boud rate . You said that can’t change. No problem but you must to tel for us to change the port seting witch start with 9600 boud.
Maybe the next week somebody from our company will go with your scope to the dealer (CONEXELECTRONIC romania) …
You don’t replay nothing about Windows XP.
I said before he ask me “Please select a device” but he answer “could not connect to COM 23”
Your Device Manager shows you which devices are in use!?
Do NOT change any settings on the driver itself in Device Manager. Windows software can choose the baud rate (and other properties) at which it wants to connect, there is no need to tamper with those settings.
Open the dropdown in the connection dialog and select the COM port that is in the list. Try not to type anything in yourself. The software always tries to list all ports that are recognized as HPS50. This way you will be certain that you have the correct port. If you can’t connect to that port, then other software is using it, and you will need to find out what software.
I still can not figure out your exact problem. In your first posts you say that you are able to connect but you only see a valid signal for one or two seconds. Now it seems you can no longer connect. Your port number also changes irratically (COM8, COM9, COM23, …) which is very strange. COM port numbers usually remain the same per physical port on your computer.
Normally you just plug in the HPS50, install the driver and software et voila, it works.
If you believe your unit is defective you can return your unit for repair.
Good day
Finaly I am happy because Velleman Team solved the problem NOT YOU “VEL448” .
yOU MUST LEARN TO UNDERSTAND THE CUSTOMER AND RESPECT THEM.
ALSO YOU MUST VERIFY WHAT WE WANT.
The new soft version 3.3 work well (on WIN 7pro and on XP) and can have the back ground WHITE.
Thanks again to Velleman team.
Best regards Stefan Martin
I think the language barrier was preventing us from finding a solution quickly, but it’s good to see that your problem is solved!
I’m the writer of the HPS50 software and driver, I added the white theme because of another post on the forum that I had missed before of someone that wanted to project the scope, I hope this view is better for those users. It seems you prefer this lighter theme too…
A bug was discovered with COM ports > 10 where windows requires the port name be prefixed by “\.”. This was fixed in version 3.3. Also, the connection dialog sometimes misinterpreted the COM port as not being filled in.