On 3/1/2016 10:05 AM, Sebastian Kuzminsky wrote: > On 02/29/2016 10:26 PM, dan...@austin.rr.com wrote: >> Well I spent several hours on this now. I do see the format is wrong, I >> changed to: >> >> loadusr -W wj200_vfd baud=19200 >> >> But I've got it on a scope and it's still 9600 baud. And if I change it to >> "baud=hahahhaha", there's no error for it being a non-number either. >> >> Could the wj200_vfd code have a bug in accepting arguments? > It's certainly possible that there's a bug in the WJ200 driver, but at > this time I don't know of any. > > Looking at the code, i see that it expects arguments to have two leading > dashes, for example "--baud=12345". > > I also see that it does not attempt to validate the --baud=NUMBER > argument, so it makes sense that giving the argument "--baud=huehuehue" > leaves the baud rate at 9600 and does not complain. (I'm not saying it > *should* be that way, just saying that's what the code currently does.) >
Can you set the drive to 9600 baud and see if you can establish a comm link? Dave ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
