Member Since: May 16, 2009

Country: United States

  • Any chance of starting a repo for this product? We’ve made an improved version of this board now which doesn’t require the RTS pin. The change makes use of the Max13487 chip which has a built in state machine to determine the Rx and Tx directions. No more struggling with getting the timing delays correct for the RTS triggering. We use the new board design to communicate reliably with industrial equipment such as HMIs and VSDs at anything up to 115200baud. We’d love to share the changes with you, but don’t want to start our own repo as it would be better placed under your original design. Thanks in advance…

  • Hi Mike, just a quick follow up on this. We played with this breakout board, as well as the Max485 for a few weeks. It is extremely sensitive to delays and timing in order to trigger the RTS line reliably. We decided instead to use the Max13487 chip which has a built-in state machine and handles the TX-RX latching by itself. This removes all of the delays from the Modbus library file and also frees up the RTS pin. We now have Modbus running flawlessly at 115200baud. This is only positive criticism, but I would highly recommend and suggest that you change your Modbus chips to the Max13487. I think the majority of us customers would rather just plug and play and the sadistic ones can buy their own Max485 with an RTS pin and spend weeks debugging :) Use it, don’t use it…

  • Hey, link seems to be broken. Any chance of a fix or a re-link? Thanks in advance… it may save my board from the bin…

  • “SoftwareSerial” library doesn’t compile… any ideas?

  • “SoftwareSerial” library doesn’t compile… any ideas?

  • “SoftwareSerial” library doesn’t compile… any ideas?

  • “SoftwareSerial” library doesn’t compile… any ideas?

  • And “SoftwareSerial” library doesn’t compile… again…any ideas?

  • I have bought four (4) pro-micro 3.3V boards. Two of them work fine and are listed at Port 11 in the device manager. The other two don’t even recognise and I get the “USB device not recognised” message from windows. (That is straight out of the packaging.) I am assuming that the problem is with the bootloader!? Or are the devices faulty? I am using Arduino 1.0 And I have uninstalled all hidden devices in device manager and re-installed the drivers…both for 3.3V and 5V pro-micro. Any help here please?

  • Guys, I have seriously just wasted an entire day trying to solve build issues with the HelloIOIO project and the IOIOLib library. I kept getting the red cross next to the SRC folder in IOIOLib. ECLIPSE was failing to compile the *.java files in “ioio.lib.impl” and “ioio.lib.util”…EVENTUALLY, after countless installs/reinstalls/rebuilds/cleans/SDK and ADT version updates, the problem was found to be the JRE version installed on the PC. You cannot use the IOIOLib library with either JRE version 1.5 or JRE 1.7!! It HAS to be JRE 1.6! This is assuming a setup of ECLIPSE 3.7.1; ADT v15 (required according to IOIOwiki for latest apk) and Android 4.0.3. (I tried with every Android API version and none worked unless I used JRE 1.6… Just thought I would post this here to save anyone else the anguish which I have just experienced…PEACE

No public wish lists :(