Hi folks, I believe a lot of you are into 3D printing industry and I think I'll get the help I need in choosing my 1st 3D printer. Here's the link, would you take a look?

Josh (or anyone who may know),

Just tried building the new v2.3 Bpod (hold up in a my garage trying to keep busy as Princeton is now shut down).  Everything seemed good except when I connect a nose port to jacks 1 and 4. Poke in events are not detected (other port functions, LED, water valve work fine in all jacks) and poke in events are detected if I connect the same nose port to jacks 2 and 3.  I've been trying to hunt around on the board for a short (seeedstudio did once send us a circuit board that was wired incorrectly with a hidden short in one of the layers) but so far can't seem to find anything.  The voltage input to IC12 seems off for those 2 jacks so I think IC12 is functioning fine, it's just getting a bad input and passing that along.  When I test the pins on the ethernet port on the Bpod board with a nose port connected everything looks identical between a functioning jack (2 or 3) and the non-functioning jacks (1 and 4).  Finally I measured the voltage across the phototransistor on the nose port itself.  When connected to a functioning jack I see a voltage of 0.15V when poked out and 4.55V when poked in.  However, when I connect the same nose port to a non-functioning jack I see a voltage of 0.15V when poked out but only 0.65V when poked in.  I get the same result after removing the new 22k pull-up resistors.  If I measure the voltage across the pads for the new pull-up resistors I get a similar behavior.  Functioning jack, poke out 4.85V, poke in 0.15V.  Non-functioning jack, poke out 4.85V, poke in 4.15V.  Any thoughts on what could be causing this? Any other tests I should run to try to find the source of the problem (teensy?, IC12?, PCB?)

Thanks
Chuck

Hi,
I could not find the assembly instructions for the newer Bpod modules could someone point me in the right direction or share them with me 

Best regards Max

Hello everyone!
I was wondering if the State Machine accepts a 0-5V logic (I want to use an arduino's digital input to trigger a new state) with 0 being the LOW level and 5V being the HIGH.

Thanks in advance!
Have a great day

Hello,

I am encountering a bug where Bpod freezes in the middle of a protocol: valves do not open/close, the trial does not advance, and the Bpod Console displays a single state with no transitions. This happens on only one of two Bpod machines that I have, despite the fact that they are running the exact same protocol. (They are, however, connected to different hardware, as I describe below.) I have to Ctrl+C in order to end the program, and when I do, the following error message is printed:

Hello,

I am new to Bpod programming and running into some basic roadblocks as I learn to develop my own protocol. 

For now, I just want to generate a TTL pulse with a specific delay from a specific BNC port on my Bpod r2 state machine. I have managed to launch the code, however I keep getting error messages that do not indicate (to me) what I am doing incorrectly.

Hi Josh,

I'm using Bpod r2. I found my Bpod becomes slower and slower as the task code running. After 2 hours of running, there is an obvious gap between touching the sensor port and the start of the trial, which affects animal performance a lot. I'm wondering is this because of the problem inside Bpod or computer memory? How should I fix it?

Thanks,
Charles

Hi there...How can I run the Analog Output Module as a PulsePalModule using the serial interface? Is the syntax similar to running the module as a WavePlayer? Thanks in advance...

Josh,

Basically I'm just tinkering so I can better understand how these things work.  I wanted to see if it was possible to increase the number of sounds (waveforms) the AOM can play running the BpodAudioPlayer_Live firmware.  I presume the two lines I need to adjust are:

const byte maxWaves = 20;
const uint32_t bufSize = 2000;

As currently configured almost all the teensy 3.6's memory is used up.  Therefore I figured if I wanted to increase the number of waves I'd need to decrease the buffer size.  And while I can decrease the buffer size to 1000 (things still play fine if maxWaves stays at 20), and I can decrease the maxWaves value below 20 (things play fine keeping maxWaves at 20 even if I increase bufSize above 2000), if I try to increase the maxWaves, say to 21 or 22 and decrease bufSize so a comparable amount of memory is used ~95%, the sounds simply don't play.  There are no errors in either Arduino when compiling and uploading, or matlab when running, just no sound output. Is there another variable or line I need to change?

Thoughts?

On a related note, are there any thoughts to upgrading Bpod and modules to run with teensy 4x at its core (high clock speed and more onboard memory could mean more sounds sampled at a higher rate than 44.1kHz)?

Thanks
Chuck

We've found that occasionally rebooting the Bpod and AOM helps things run smoothly (occasionally the system can get in a non-functional state and this is the only way to get it out, though we're still trying to figure out exactly what's causing the non-functional state).  Since the power comes from the USB hub on the computer, rebooting or even powering the computer down does not cut power to the teensy.  So to force a reboot in the bpod we added the following code to the firmware in the section that starts

if ((PC.available() > 0) && (smaPending == false)) {
CommandByte = PC.readByte();

switch (CommandByte) {

case 'Q':  // SYSTEM RESET
          digitalWrite(GreenLEDPin, LOW);
          analogWrite(BlueLEDPin, 250);
          analogWrite(RedLEDPin, 128);
          delay(1000);
          SCB_AIRCR = 0x05fa0004;
      break;

Sending a Q causes the LED to turn magenta for 1s before it reboots and the LED goes back to blue flashing.

For the AOM we added the following in the section that starts

if (newOpCode) {
newOpCode = false;
switch(opCode) {

case 'Q': // SYSTEM RESET
        stopPlayback();
        SCB_AIRCR = 0x05fa0004;
      break;

Sending a Q will stop sounds and reboot the teensy causing the orange light to blink. 

We've added these commands to the function EndBpod.m after the write Z command

 BpodSystem.SerialPort.write('Z', 'uint8');
 pause(1);
 BpodSystem.PluginObjects.SoundServer.Port.write('Q','uint8')
 pause(1);
 BpodSystem.SerialPort.write('Q', 'uint8');
              


Just a thought to maybe include in other module firmware if people are having any issues.

Chuck