jDrones News: jD-IOBoard v1.0



jDrones News: jD-IOBoard v1.0 update


You had some problems on driving LED strips or something else?? Well no problems anymore.... We have seen people making all type of darlington/transistor and similar hacks to drive their LEDs, Sirens and so on but they all need a lot of hacking and they might not be suitable for long term solution. 

We answered on this call and made fully Arduino compatible called jD-IOBoard that can run Single LEDs, LED Strips, Loudspeakers, Buzzers, Power switches and so on. It's upto your own imagination on what all you can control with this board. 


So what does this board actually do?? It has fully Arduino compatible ATMEGA 328 MCU and Darlington array to driver high power outputs. Also I2C pins are exposed and same as many TTL level IO and Analog pins. As you can see from picture above. 


Board has:

- 6 x High power outputs, max. 500mAh / 50 Volts

- 4 x Analog inputs (6 if you don't use I2C port)

- I2C port for controlling, listening I2C messages

- 6 x TTL level GPIO pins (8 if you don't use FTDI)

- 1 x FTDI port


3 high power outputs can also be controlled by PWM output while another 3 are just normal "On/Off" outputs



How those Arduino pinouts looks like:


Connecting LED's,Buzzers etc is really simple. Just use one of output pins on end of the board. Below you can see examples on how to connect LEDs or LED Strips on it.





Pictures does not give enough credit for how it works so we made small video to show just few examples on how to use it. There are many other ways to do it but this should give at least some idea what/how to run it. So have fun watching it.


Get yours from jDrones Store: jD-IOBoard and have a blink blink.


Ps. There are some nice features coming to this board shortly...


E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones


  • Developer

    @Mohd, we are releasing new document site later at this week and there will be more connection guides for all our boards. In generally you connect 5Pin connectors from APM to Telemetry board and continue to Telemetry modems. All other will go on those 4 pin headers that are middle of board.

    @Stefan you should not need to do any powercycle for it. Just use normal Arduino IDE to upload sketches or even Mission Planner to do that and use ready made HEX files. 

  • Now I had some time to start tinkering with my jdio 1.1...

    Is there any way to program it without powercycling? It seems like the usual reset-to-bootloader function is not implemented - can't program it with a normal FTDI without powercycling and the board doesn't have a standard ICP header. That's a bit annoying.

  • Hi Jani !! i already connected the distribution board as per your suggested but my mission planner cannot connect to APM 2.5 (Error ! Heartbeat Packets Received)

  • Hi Jani my distribution board have arrived !! any diagram or guide on how the connection to APM ??

  • I received my JD-IOBoard v1.1 today, cabled everything and things look somehow basically OK, but I did not figure out, how to configure/use JD-IOBoard with a X-frame type quadcopter properly. 

    The drawing in the Configurator shows for both front arms, "REAR" should be used? Is this a typo, or do I really have to recable something then?

    thanks a lot,


  • Jani

    Where is the new doc (link) for the new Jd ioboard 1.1?

    Need pin to see pins assignment for 12 volt and all the changes between version 1 &1.1

    "Also we have new jD-IOBoard v1.1 out. Few nice changes compared to v1.0.

    Battery input has not both +12V/GND pins nicely arranged. One high input port was moved to be as on side of the board and side pin moved to high input. They are Digital PINs 2 and 7. We basically did swap them and this way we have now Interrupt capable pin exposed on side of the board."

    Also silkscreens have been updated on IOBoard.

    We are now updating storepages and also jDoc pages for it. 

  • @ mohd fitri -- if you look back to either page 1 or 2 of this thread, you will notice that I was the first to bring up the issue that was inability to communicate with bootloader as a result of doing nothing but running the software provided.  To this day I have still never gotten to try the two boards I purchased right when they were made available as neither one can successfully be programmed.  Last night, I decided to give them another go and try whatever possible to get them working again.  That's when I read your post, in which you appear to have finally gotten to the bottom of this dreadful issue and have the hardware working as advertised... IS THIS CORRECT?  Congrats!  Feel like sharing whatever you did (exactly) so I might have the same satisfaction -- nearly a year after buying it?

    Thanks very much , in advance, for yours and whomever else's guidance might possibly get my jDrones ioBoard'd be about f(*&*ing time... :)

  • OK and I will order a 1.1 from you also. Just waiting for your reply on support request.

  • Developer

    Steve, that might be a bug in first beta software. I will take a look and update those as there will be small update for v1.1 users too.

    Also we are looking programmers to work with us so in close future updates will be more frequent.

  • Jani do you know how to solve the problem of the left and right lights flashing when flying. You told me before that it indicated a loss of mavlink. I don't see the condition the GCS but does your Telemetry Distribution help with this problem? I now just wire my green and red directly to the lip and bipassing the ioboard but I prefer to control them with the ioboard.

This reply was deleted.