Member Since: November 16, 2011

Country: United States

  • Imho, that could be a serius internal bug and something on which many parts of the system rely. In that case you can't just go to a safe-mode as the system is "unstable", like in a kernel panic. In that case the only thing you can do is a) reboot automatically b) show some debug info to help identify the issue

    I prefer (b) because i don't want to hide issues (and if the thing reboots in the middle of something it's not good at all). What i would do is probably write something like "Sorry, something went very wrong: please restart the machine. If you could call our support team and provide this data to help fix the issue it would be much appreciated". Well, okay, probably not exactly like this, but you get the idea :)

    The only problem i see is this happend for a while without getting solved (according to the post).

  • "50 shades of... LED"

  • Owling: you're doing it w... oh cmon dude, just don't do it.

  • I think supply and communication voltages should be better specified. According to the latest version of the datasheet, GT-511C3_datasheet_V1 1_20130411[4].pdf, the module has an "Operating voltage" in the range 3.3-6V. With just this information one could conclude that the supply and communication voltages are equal and in that range, so this module could be used at both 3.3V and 5V without any level converter. But this may not be the case. Please improve the description on this matter.

    EDIT: the datasheet specifies on the last pages the pinout and there it also specifies that supply is 3.3-6V while communication is 3.3V. Also, i measured the idle voltage of the TX pin with 5V supply and it was 3.3V. This confirms such data.

  • I'd like to give my 2cents too about FTDI: the reason i really like it is that you can use it as a simple virtual com port but you can also use their libraries to transfer data and in that case you can refer to a device using the name instead of a com port number. This is very nice in my opinion as plugging a device in a different port will create new (different) virtual com ports and i always have to check which port was assigned.

  • Arduino stacking design: you're doing it wrong.

  • Even if your PC probably won't die because of this, there are situations where it would be surely better to not have those alligators clips hanging out. Think about non-properly designed USB hosts and hubs (i don't even want to know...). Or powering your circuit with the plug and then having the clips make a short on ICs.

    Detachable clips sounds like a good compromise to me.

  • A widely used rule of thumb indicates that cables more than 50 feet (15 m) long will have too much capacitance, unless special cables are used. By using low-capacitance cables, full speed communication can be maintained over larger distances up to about 1,000 feet (300 m)."

    Aside from the special cables to reach that distance, i'm worried for Electromagnetic interference to the electronics. Of course "it can be done", but i won't recommend it. RS485 is not harder/expensive/complex too.

  • RS232 suitable for long distance communications? O_o I don't agree with this one. Unless "long" is a few meters.

  • Moustache + Red hat = WIN! Even if you're number 13.

No public wish lists :(