Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Adrel Altimeter/Laptop Setup Help Needed
#1
I have been attempting to set up my new Adrel Altimeter on my Windows 10 laptop and I am having issues with it be recognized as a USB device.  Setup on my desktop went without a hitch, but the desktop is not very portable.
Anyone out there that may be willing to lend me some assistance?  I believe I have a hardware settings issue, but I am stuck.

Glenn
Reply
#2
This is what I received from the Adrel guy when I had the same problem a year ago.


Quote:See section 15
https://micro-manager.org/wiki/Installing_Micro-Manager_64_bit

Otherwise you can disable signatures drivers:

https://social.technet.microsoft.com/Forums/windows/en-US/9b6eee60-855d-47cc-9927-acae3fb6f971/permanently-disable-driver-signature-enforcement-on-win-7-x64?forum=w7itprohardware

https://support.hidemyass.com/hc/en-us/articles/202723596-How-to-disable-Driver-Signing-check-on-Windows

https://www.youtube.com/watch?v=hp9o90TwX2U

Regards
Leszek Szwed
Reply
#3
So the Adrel software still requires one to bypass Windows security to work? I had hoped that when NCR brought them into the US that that would be fixed. *sigh*
Bernard Cawley
NAR 89020
AMA 42160
“BEC” on YORF, TRF, RCGroups and a few other places
Reply
#4
I am having similar issues with my adrel The instructions provided by Northcoast Rocketry do not provide any data on how do deal with setting it up with Windows 7. I have a laptop with Windows 7 that I was going to primarily use for rocketry related items. The instructions give data for Windows 10 but nothing for Windows 7.
Reply
#5
The problem with the Adrel software is that the Windows 10 drivers are not signed - the cost was prohibitive for the tiny market that was in Eastern Europe, where only a few people (as contest officials) run the software. Microsoft's earlier versions of Windows did not require signed drivers.

It's a different issue in the US. As a result of the issue, I am having a set of signed drivers developed and approved for use on Windows 10. I'm hoping to have it ready by spring. I think that will solve the problem.

Matt
Reply
#6
Here's the general driver-signing policy from Microsoft:
 https://docs.microsoft.com/en-us/windows...-and-later-

For Windows version earlier than Windows 10, version 1607, you can override the driver-signing requirement.

I am using Win 7 and can override unsigned drivers using the following method from this link:
  
Quote:Disable Driver Signing in Windows 7 Using Group Policy Editor:
a. Click on Start, then click on run, type gpedit.msc to open the local group’s policy editor.
b. Expand ‘Administrative Templates’ (it’s under ‘User Configuration’). Expand ‘System’. Click ‘Driver Installation’.
c. In the right panel, double click on ‘Code Signing for Device Drivers’.
d. Choose ‘Enabled’ in the window that appears. In the underlying options, choose ‘Ignore’. This disables drivers signing in Windows 7, and now you can install unsigned drivers in Windows.
e. Click Apply, OK. Restart your computer to install unsigned drivers.


I'm currently developing a set of drivers for a printer manufactured by one of my clients. It's not too bad overriding things for development, but it's overly complicated making something for general release on all platforms.

 -John
Reply
#7
(01-11-2018, 10:27 PM)Matt Steele Wrote: It's a different issue in the US. As a result of the issue, I am having a set of signed drivers developed and approved for use on Windows 10. I'm hoping to have it ready by spring. I think that will solve the problem.

Matt

It’s been a problem really since Vista - certainly Windows 7 (which is why I never bought the more recent version of the USB). I never really was comfortable with the “download and install this little program that bypasses the need for signed drivers” bit.

That said, I’m glad to see that you’re addressing this. Thanks, Matt!
Bernard Cawley
NAR 89020
AMA 42160
“BEC” on YORF, TRF, RCGroups and a few other places
Reply
#8
A follow-up here. Between new hardware for the computer interface (available from NCR) which solves the driver issue and an updated Adrel application (available from Adrel.pl) which uses this new hardware, this issue is now very neatly addressed. I have been using the combination for a few weeks and it works well.

So - no more having to mess with going around Windows security to use an Adrel ALT-BMP.
Bernard Cawley
NAR 89020
AMA 42160
“BEC” on YORF, TRF, RCGroups and a few other places
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)