Jump to content

NicR

Members
  • Posts

    15
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

NicR's Achievements

Member

Member (2/4)

0

Reputation

  1. I have a stack of 7 MCC172s. The set up was working fine & recording all channels with no problems but recently I keep getting the following error, There was a timeout while obtaining a resource lock This happens when trying to set up Device 0 Any clue what's happening here?
  2. I'm trying to run the C example data_logger for the MCC128. I got all the prerequisites & it compiled with no issues If I just & click start ./logger I get the error, Unable to open the log file. If I, sudo ./logger I get the error, There was a timeout while obtaining a resource block. Click 'OK' and the program closes There were no problems running the other examples, I can read the EEPROM, the channels show up in the MCC128 App, single_value_read, finite_scan & continuous_scan all work. Any clue what's causing this? Nic
  3. Found the problem as soon as I posted, the DAQ channel & the CT need the same ground reference. Connected both -ve terminals to pin 39 on the Pi GPIO & its all working fine.
  4. I have an MCC 128 attached to an AT 50 B10 split core current transformer. I'm running the logging demo & getting some odd results. I have a mains cable (UK) running through the CT which sould be reading 0 as both the live & the nutral are threaded through but I'm getting a ±7 VAC signal instead! Sketch of set up, The CT should be giving a voltage between 0-10V depending n the current through the threaded cable (& in this case it should be 0 as the nutral is included) but instead I get.. Any idea whats going on here?
  5. Thanks John, I'll only be reading one channel so hopefully this will be fine.
  6. I have a MCC-128 and want to acquire data from an AT 50 B10 current transformer. The MCC 128 data sheet says the input impedance is 2 GΩ and the AT data sheet says the output load should be > 2 MΩ. Am I correct in thinking that I can just wire the AT up to one of the MCC analogue inputs?
  7. They physically dont fit so that's that option out of the window
  8. Hi, I've got a stack of 7 MCC172s & they all running fine. Will it be OK to stack them on top of a Power Over Ethernet hat?
  9. I've notice that no matter what I set the sample_rate to I always get ~51KHZ sampling which is leading (I think) to buffer overflow as I'm reading out only a fraction of what is being produced? So I guess I'm confused by the fact that mcc172_a_in_clock_config_write uses sample_rate yet mcc172_a_in_clock_config_read uses &actual_sample_rate. Is there a way of explicitly setting the read rate? or do I have to use actual_sample_rate?
  10. I'm using multiple MCC172 hats & want continuous sampling. How do I include both OPTS_EXTTRIGGER and OPTS_CONTINUOUS. I checked mcc172.c and the mcc172_a_in_scan_start() function declares uint32_t options so can I only use one of the above options?
  11. Any idea why it would throw a segmentation error? It falls over when checking while (channel_mask > 0) Isn't the channel mask the same for every device? What would be different for the 3rd device in the stack do you think? EDIT:: I found it, I hadn't declared all the channels in the chan_mask declaration
  12. I have a stack of 7 hats, I have read all the EEPROMS & they can all be seen when I list the hats. I have given each hat its own number using the jumpers on the board 0-6 with the MASTER being 0, all the lights are green. I am using the multi_hat_synchtonous_scan code as my base & have changed DEVICE_COUNT = 7 The code was working fine for 2 hats but now I get a segmentation error during the trigger set up as soon as it tries to configure device 2. The line that throws the error, convert_chan_mask_to_string(chan_mask[device], chan_display[device]); What am I missing here?
  13. Hi I have 8 MCC172 hats on a Raspberry Pi and am reading in synchronized data. The program was hacked together from the C examples library. The acquisition starts with a trigger input to the master hat & I was wondering if it was possible to stop the acquisition in the same way? Is it possible to poll the trigger status without reading in data? Nic
×
×
  • Create New...