update wiringpi to support baud rate of 4800

[SnakeDoc]

Add support for baud rate of 4800 - this allows any serial device that requires 4800 baud to work, ex: GPS

[charliemciver]

Is this issue resolved?

[SnakeDoc]

just looked, it appears it's been fixed in the latest release (quietly, no commit for it specifically, so no idea which commit fixed it).

it appears wiringpi has been moved from GitHub to Gordon's own website and the GitHub repo abandoned. http://git.drogon.net/?p=wiringPi

no idea why, not to mention Gordon's git page is much harder to understand and find changes than the visual tools built into github... but i digress.

I guess we leave this ticket open until gordon updates the github repo?

[charliemciver]

Thanks SnakeDoc - so does this mean we can get Pi4J rebuilt and use 4800 baud - I'm hoping to use it for a marine NMEa application which all runs 4800!

[SnakeDoc]

lol, i originally found this "bug" because i too was writing a NMEA gps application! small world ;-P

i believe the pi4j guys grab the latest jar lib from http://wiringpi.net, so i'm assuming it has been fixed in pi4j. I've not verified myself... for my app, i just ended up reading gps data over the serial port raw using the Process.class and Runtime.getRuntime().exec(cmd); which worked well for my purpose.

of course, you can always download pi4j sources from github, replace the wiriginpi lib with the latest from wiringpi.net and compile it to a jar yourself. :)

[wbphelps]

I like wiringpi for GPIO but why not use PySerial for serial I/O like GPS? Supports 4800 and 9600 BPS, I've been using it on several RPI's without any problems.

[SnakeDoc]

because pi4j is a java library (and wraps wiringpi) ;-P

[charliemciver]

I found another Java Serial library jSSC which also seems to be multi platform - Windows Mac, etc... so thats kind of useful. Shame I have to abandon pi4j

[SnakeDoc]

if you prefer jSSC, of course use it, but i see no reason to abandon pi4j, it's still a very nice library. This "bug" was not pi4j's issue, it is wiringpi, however it is fixed in upstream wiringpi and likely fixed in pi4j too.

[SnakeDoc]

if you look at the pull request attached to this Issue, you'll see it was a simple type-o and baud 4800 was accidentally left out. this is the same fix Gordon put into upstream.