ZmqCamera giving constant black output

I was having a very similar issue to the one detailed here: Jetbot "road_following" example long camera lag. I tried to do the answer given, though it did not work. The ZmqCamera simply gives a constant black output. When I switch back to using the OpenCV camera, it begins to work again. This is the log when I run zmq_camera_publisher.py

root@nano-2gb-jp441:/jetbot/scripts# python3 zmq_camera_publisher.py
0
nvarguscamerasrc sensor-mode=0 ! video/x-raw(memory:NVMM), width=816, height=616, format=(string)NV12, framerate=(fraction)21/1 ! nvvidconv ! video/x-raw, width=(int)224, height=(int)224, format=(string)BGRx ! videoconvert ! video/x-raw, format=(string)BGR ! appsink name=sink
starting camera
GST_ARGUS: Creating output stream
CONSUMER: Waiting until producer is connected...
GST_ARGUS: Available Sensor modes :
GST_ARGUS: 3264 x 2464 FR = 21.000000 fps Duration = 47619048 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 3264 x 1848 FR = 28.000001 fps Duration = 35714284 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1920 x 1080 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1280 x 720 FR = 59.999999 fps Duration = 16666667 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: 1280 x 720 FR = 120.000005 fps Duration = 8333333 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: Running with following settings:
   Camera index = 0 
   Camera mode  = 0 
   Output Stream W = 3264 H = 2464 
   seconds to Run    = 0 
   Frame Rate = 21.000000 
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.

Hi tony.baston,

Sorry for the late response, have you managed to get issue resolved?
Or this is still an issue to support?

Thanks

Yes, I could get the issue resolved. It turns out I did not run setup.py correctly, which is what caused the issue. I just ran python3 setup.py when I should have run python3 setup.py build and then python3 setup.py install