Jump to content

lockecaps

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by lockecaps

  1. Hello again, just bumping this thread to receive some support from the Diligent team.
  2. HI Fausto, Apologies for the delay. I couldn't keep troubleshooting due to medical reasons that required hospitalization. Now, to answer your questions: - Power supply is 5V / 3000 mA. I strongly doubt there's some issue with the power supply. - SPI Interface was enabled, but I2C wasn't. I enabled it now. - Problem is still the same, application still can't open the device. Note: I have, in total, 4 Pi hats. 2 of those don't work, 2 of those work. So I wouldn't point towards the Raspberry Pi being the fault one at this chain.
  3. Hi, One of my MCC 172 Hats is not working and I can't quite understand why. If I run "daqhats_list_boards", I get (Note: address 1 is the problem): Address: 0 Type: MCC 172 Hardware version: 2 Name: MCC 172 IEPE HAT Firmware version: 1.01 Address: 1 Type: MCC 172 Hardware version: 2 Name: MCC 172 IEPE HAT Can't open device And nothing I tried could fix it. running a scan_stop, scan_cleanup, the board doesnt respond to anything. Is this board simply permanently damaged, or is there something I could do to fix it?
  4. Hi John, Thanks for the response. I'm interested in start the recording with the script and having them synchronized without the need for external cables and/or external triggers. From your response, I think this is what you described. Can you expand a bit on how that would work? - I should set trigger_config() as a MASTER on my first hat, as SLAVE on the subsequent hats - I should send GPIO.setup(PIN=5, GPIO.HIGH) And that will initiate the data collection trigger without the need to physically affix a cable from the pin GPIO 5 to the trigger pin?
  5. Hi, I'm trying to acquire data with multiple MCC 172 Hats, using the first one as a "master". I'm following the example "multi_hat_synchronous_scan.py". The problem is it sets the triggers as: options = [ OptionFlags.EXTTRIGGER, OptionFlags.EXTTRIGGER ] samples_per_channel = 10000 sample_rate = 10240.0 # Samples per second trigger_mode = TriggerModes.RISING_EDGE ... for i, hat in enumerate(hats): chan_mask = chan_list_to_mask(chans[i]) hat.a_in_scan_start(chan_mask, samples_per_channel, options[i]) But I can't figure out how I change it to start recording as soon as I start the script. I tried looking in the documentation, but changing it to "options = OptionFlags.CONTINUOUS" doesn't work, and I'm running out of ideas. The documentation for the MCC is very lacking.
×
×
  • Create New...