bentwookie
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Posts posted by bentwookie
-
-
I don't see a great dedication to customers or product in this thread, especially in Dec '16, where I gave up on your product in order to make deadline. I see plenty of "hey is anyone here", "I never got this to work". I see customers flailing around trying to decipher Python search paths over a year's time. Those aren't traits I associate with a great product, or great support. Maybe you've turned it around in a new version. I'll never know.
-
Good luck buddy! If it doesn't work, you'll never hear from Attila again. The reason this thread died is because everyone I know gave up on it. There are plenty of other USB scopes out there. Go find one where they actually support their product.
-
1 hour ago, malexander said:
@Naoshi
I was checking this thread regularly for a few days and then got distracted and forgot about it. Anyway, ERC 3090 means that there was an error while initializing DPCOMM. There are a number of reasons why this could happen. Thankfully there is a way to enable an error log. Can you please do the following:
1. Execute "export ADEPT_RT_LOGDETAIL=1"
2. Execute "export ADEPT_RT_LOGFILE=~/adept_erc.log"
3. Re-run your modified version of digi_enum.py and post the output of the log file here.
Thanks,
Michael
You've asked for and received a number of these. What's the plan? Is there a bug? Is there a new version? What are the "number of reasons this can happen"?
-
They don't care. Return your scope while you can.
-
FWIW, I never did get it to work. I installed Linux into a VM and ran it there. If it doesn't work, and they're clearly not going to support it, they shouldn't advertise that it works on a Mac.
-
There are two FTDI drivers on my system. The top one is the one that comes with the OS. It's not going anywhere.
121 0 0xffffff7f82f07000 0x7000 0x7000 com.apple.driver.AppleUSBFTDI (5.0.0) 797D6BEE-10AD-30B0-97AE-157463D700AF <120 17 5 4 3 1>
122 0 0xffffff7f82f0e000 0x2000 0x2000 com.digilent.driver.DigilentFtdiDriver (1.0.3) 04D22EC0-C800-389F-A0FD-F0F759897EEE <18 4 3>
The records for the two drivers in play. The internal one isn't loaded in this case:<dict>
<key>_name</key>
<string>AppleUSBFTDI</string>
<key>spext_architectures</key>
<array>
<string>x86_64</string>
</array>
<key>spext_bundleid</key>
<string>com.apple.driver.AppleUSBFTDI</string>
<key>spext_has64BitIntelCode</key>
<string>spext_yes</string>
<key>spext_hasAllDependencies</key>
<string>spext_satisfied</string>
<key>spext_info</key>
<string>5.0.0, Apple USB FTDI driver</string>
<key>spext_lastModified</key>
<date>2016-09-09T01:19:58Z</date>
<key>spext_loadable</key>
<string>spext_yes</string>
<key>spext_loaded</key>
<string>spext_no</string>
<key>spext_obtained_from</key>
<string>spext_apple</string>
<key>spext_path</key>
<string>/System/Library/Extensions/AppleUSBFTDI.kext</string>
<key>spext_runtime_environment</key>
<string>spext_arch_x86</string>
<key>spext_signed_by</key>
<string>Software Signing, Apple Code Signing Certification Authority, Apple Root CA</string>
<key>spext_version</key>
<string>5.0.0</string>
<key>version</key>
<string>5.0.0</string>
</dict>The Digilent kext looks like it's loaded. It's just not finding anything.<dict>
<key>_name</key>
<string>DigilentFtdiDriver</string>
<key>spext_architectures</key>
<array>
<string>x86_64</string>
</array>
<key>spext_bundleid</key>
<string>com.digilent.driver.DigilentFtdiDriver</string>
<key>spext_has64BitIntelCode</key>
<string>spext_yes</string>
<key>spext_hasAllDependencies</key>
<string>spext_satisfied</string>
<key>spext_lastModified</key>
<date>2014-08-29T16:34:33Z</date>
<key>spext_load_address</key>
<string>18446743521855594496</string>
<key>spext_loadable</key>
<string>spext_yes</string>
<key>spext_loaded</key>
<string>spext_yes</string>
<key>spext_obtained_from</key>
<string>spext_identified_developer</string>
<key>spext_path</key>
<string>/Library/Extensions/DigilentFtdiDriver.kext</string>
<key>spext_runtime_environment</key>
<string>spext_arch_x86</string>
<key>spext_signed_by</key>
<string>Developer ID Application: Digilent (3GQCL4AKGN), Developer ID Certification Authority, Apple Root CA</string>
<key>spext_version</key>
<string>1.0.3</string>
<key>version</key>
<string>1.0.3</string>
</dict> -
What's the conclusion on this? I'm having the same problem. kextstat shows:
155 0 0xffffff7f83a82000 0x2000 0x2000 com.digilent.driver.DigilentFtdiDriver (1.0.3) 04D22EC0-C800-389F-A0FD-F0F759897EEE <18 4 3>
but WaveForms shows: No device detectedI'm on 10.12.1 (16B2555)
Mac + Analog Discovery 2 + Waveforms 2015: No device detected
in Test and Measurement
Posted · Edited by JColvin
word choices
I had plenty of interest in getting it to work when I still had one in my possession and a job to finish.
You're right in wondering why I'm still bothered by it. The only answer I can give is that I've spent my entire career striving to build products that are as perfect as I can make them. Bugs happen, (I've had some real doozies) but when they do, it's on you and your support org to make it right; to fix the engineering and processes so it doesn't happen again. Quickly.
So when the product completely fails, and the support fails as well, I get itchy. The people I work with get itchy too, which is why we've made great stuff together over the years.
Anyway, when called out on it, excuses like "that guy is gone for weeks" or "we only have a few people" don't scratch my itchies. Proof of "good" reviews including a guy complaining that the serial driver scrambled his Mac really don't help either.
Regardless, you're right. It's not a great use of time. Thank you for the reminder.