I have two analogoutput_8ch modules (different pair than the two I mentioned in a previous post) which have firmware updated to the PulsepalModule. They successfully interface with the Bpod (i.e., show up as Pulse Pal in the Bpod console). However, I am unable to drive any voltage changes in any of the channels. 

For example: 

Bpod('COM3')
P1 = PulsePalModule(BpodSystem.ModuleUSB.PulsePal1); % COM7

Creates a PulsePalModule object (nchannels = 8). 

P1.restingVoltage(1:8) = 5; 

has no effect on the output of any of the channels. 

This is particularly confusing to me because I updated the firmware on these two boards in an identical manner to two other analogoutput_8ch boards (referenced in previous post). The only difference I can see is that the boards are connecting on different COM ports (even when I connect one at a time). Also, I should note that I'm doing this on a laptop connected through a thunderbolt dock so they are being connected through multiple layers of daisy-chaining (in case its a known problem). I couldn't figure out how to force one module to connect via the same COM port to test this possibility. 

Please advise! 

Thanks!

Doug

5 days later
dstorace wrote[quote='dstorace' pid='4475' dateline='1665520849']

I have two analogoutput_8ch modules (different pair than the two I mentioned in a previous post) which have firmware updated to the PulsepalModule. They successfully interface with the Bpod (i.e., show up as Pulse Pal in the Bpod console). However, I am unable to drive any voltage changes in any of the channels. 

For example: 

Bpod('COM3')
P1 = PulsePalModule(BpodSystem.ModuleUSB.PulsePal1); % COM7

Creates a PulsePalModule object (nchannels = 8). 

P1.restingVoltage(1:8) = 5; 

has no effect on the output of any of the channels. 

This is particularly confusing to me because I updated the firmware on these two boards in an identical manner to two other analogoutput_8ch boards (referenced in previous post). The only difference I can see is that the boards are connecting on different COM ports (even when I connect one at a time). Also, I should note that I'm doing this on a laptop connected through a thunderbolt dock so they are being connected through multiple layers of daisy-chaining (in case its a known problem). I couldn't figure out how to force one module to connect via the same COM port to test this possibility. 

Please advise! 

Thanks!

Doug

This problem was confirmed and fixed in an updated PulsePalModule firmware released on 10/15/22.