**** BEGIN LOGGING AT Tue Jun 20 03:00:04 2017 Jun 20 08:35:24 hi ds2: I used CRO today to checkout waveforms, it was a naive setup, as the concerned lab faculty was not present today Jun 20 08:37:06 What I observed was when I sent the square wave, the receiver output was in sine waves, Jun 20 08:38:41 the pulse was generated from wave generator, at 40kHz and at 2.8V and 30Vpp Jun 20 08:40:17 I connected this output directly to the transmitter and connected the receiver directly to CRO Jun 20 08:41:10 what I received were like sine waves in distorted form, may be this was due to the loose conections Jun 20 08:41:42 now I have access to the lab, what would you like me to do in the lab?? Jun 20 13:17:26 jkridner: hi, any success? spl device gets opened? Jun 20 13:50:55 jkridner: SPL's this error "The remote end did not respond in time" means actually what? like what does it expect from host before the bootp broadcast? Jun 20 14:07:40 jkridner: now, I'm also not seeing any bootp broadcast after spl transfer on windows, getting same error Jun 20 14:08:44 don't know how it showed up yesterday Jun 20 14:10:10 jkridner: I've run out of ideas now on how to proceed to fix this problem :( Jun 20 17:05:26 thetransformerr[: you're using the murata tx/rx parts? Jun 20 17:05:41 yes Jun 20 17:06:49 30 Vpp sounds lilke a lot Jun 20 17:07:19 so not the prudaq just straight into a scope inptu? Jun 20 17:07:28 20Vpp was the req I guess Jun 20 17:07:29 *input even Jun 20 17:07:46 no I didnt done anything with prudaq Jun 20 17:08:55 so in that case we'd need a separate power supply to dtive the sensor circuit? Jun 20 17:10:08 how big is the signal coming out of the rx side? Jun 20 17:10:33 of course we need to cchange the voltage level, we discussed it earlier and that's why we decided to try with already built circuit Jun 20 17:10:45 yup Jun 20 17:11:30 can you get a picture of the scope output? Jun 20 17:11:46 the signal strength was good, but they had some distortion and I dont know why they looked like sine waves and Jun 20 17:11:55 yes I m uploading them now Jun 20 17:13:33 i would think a noisy sine wave is about right Jun 20 17:18:11 yeah I also think this, but I cant do much experiments today as I didnt knew how to create trigger pulses from wave generator and incharge was not present today Jun 20 17:19:13 * thetransformerr[ uploaded an image: DSC_0028.jpg (574KB) Jun 20 17:19:17 * thetransformerr[ uploaded an image: DSC_0029.jpg (580KB) Jun 20 17:19:17 * thetransformerr[ uploaded an image: DSC_0030.jpg (621KB) Jun 20 17:19:21 * thetransformerr[ uploaded an image: DSC_0027.jpg (486KB) Jun 20 17:19:40 and somehow I forgot to click receiver output, the very most objective I went to college :( Jun 20 17:20:21 the wave shown in scope is from wave generator directly Jun 20 17:22:13 so you did get an output signal from rx? Jun 20 17:22:28 and in the wave function generator image, now I get to know why I Jun 20 17:22:56 lost receiver output afterwards Jun 20 17:23:48 yes I connected the receiver the same way as shown in breadboard transmitter image, and I received a noisy sine waveform Jun 20 17:26:43 now nerdboy: I am planning to do these things, create a code for PRU to trigger the transmitter, so how should I trigger them, whether I should use GPIO or eCAP module of PRU?? Jun 20 17:29:29 and then store receiver and transmitter waveform from ADC and then use cross correlation to find TOF using some python library like scipy etc Jun 20 18:05:56 mdp's ecap driver is for pulse capture Jun 20 18:06:23 hi ravikp7 Jun 20 18:06:51 jkridner: hi Jun 20 18:08:49 I've not been able to clone the repo on my Windows machine for some reason. Jun 20 18:08:50 jkridner: you got my last messages here earlier today? Jun 20 18:09:55 on-line, are you seeing anyone having been successful with booting code via SPL RNDIS/TFTP? Jun 20 18:10:01 vvu, hints? Jun 20 18:10:04 thetransformerr[: i think this is more what the output side should look like => https://gist.github.com/shirriff/2a7cf2f1adb37011da827f1c7f47b992 Jun 20 18:11:53 jkridner: I could find only vvu's code and email threads of not succeeding on Windows, so sign of success anywhere Jun 20 18:12:04 *no Jun 20 18:13:02 jkridner: https://sourceforge.net/p/libusb/mailman/message/32740724/ Jun 20 18:14:01 jkridner: I tried the windows-partial branch of BBBlfs, it gets upto getting tftp request for spl but couldn't transfer spl Jun 20 18:15:58 ravikp7: but, the firmware works on Linux and OSX, so I have my doubts to the vacuous responses. Jun 20 18:15:59 jkridner: SPL's this error "The remote end did not respond in time" means actually what? like what does it expect from host after spl transfer and before the bootp broadcast? I can't understand this :( Jun 20 18:16:42 ravikp7: seems like there isn't host enumeration even of the SPL device. If I had a bus analyzer, I could look at the enumeration process and see if it even sets and endpoint. Jun 20 18:17:08 ravikp7: on Linux, usbmon should tell you. Jun 20 18:17:33 looks like OSX has something similar: https://developer.apple.com/library/content/qa/qa1370/_index.html Jun 20 18:25:04 jkridner: http://www.usblyzer.com/ should I try this on windows? Jun 20 18:26:27 looks reasonable. Jun 20 18:27:53 trying this Jun 20 18:49:07 ravikp7: seems like Windows requires a fair amount of driver install. :( Jun 20 18:56:01 jkridner: for what? getting whole thing working? Jun 20 18:56:04 ravikp7: with the driver installed on Windows 7, I'm able to see the device from node-usb, but opening it fails. :( Jun 20 18:56:36 LIBUSB_ERROR_NOT_FOUND Jun 20 18:57:09 jkridner: you must be getting libusb_not_supported? Jun 20 18:57:57 jkridner: node-usb description says that without those drivers, device won't open Jun 20 18:58:31 hmmm... Installed the libusb-win32 drivers for the particular VID/PID. Jun 20 18:58:42 had to make a .INF using the wizard. :-/ Jun 20 18:59:51 there's option to list all connected usb devices and install required drivers Jun 20 19:00:14 why did you use vid/pid to install? Jun 20 19:04:23 ravikp7: to get the driver to associate with the device and load/run. Jun 20 19:04:41 ravikp7: the open to list the connected devices didn't show my board. Jun 20 19:05:21 the board shows up as a device, but the device.open() call fails with LIBUSB_ERROR_NOT_FOUND. Jun 20 19:05:44 I know the device is correct, because the idVendor/idProduct match. Jun 20 19:06:12 this.__getConfigDescriptor() native call fails. Jun 20 19:06:37 jkridner: was getting same when using usb 2.0 port Jun 20 19:07:27 jkridner: try with a usb 3.0 port, it worked only this way for me Jun 20 19:07:48 I checked with another pc also Jun 20 19:08:19 ravikp7: https://github.com/tessel/node-usb/issues/61 claims a work-around, but I don't yet have it working. Jun 20 19:12:03 jkridner: developer closed the issue with description of solution see last comment Jun 20 19:21:34 jkridner: I checked with usb analyzer tool, when I connect to a 2.0 port, it lists only device description in properties, while on connecting to 3.0 port, it shows device description, config description and interfaces also in usb properties Jun 21 00:56:22 thetransformerr[: you are seeing a sine like wave probally because of the limited response of the transducer. Jun 21 02:55:05 ds2: why is transducer having limited response Jun 21 02:56:11 due to loose conections??? Jun 21 02:56:30 aur no interfacing **** ENDING LOGGING AT Wed Jun 21 03:00:03 2017