|
|
Post by jamesbowman on Jun 12, 2018 16:33:53 GMT -8
I just launched a new project called SPIDriver. It's a USB <-> SPI adapter with a built in graphical display.  In the video you can see it driving a Gameduino 3 directly from the PC. It's on Crowd Supply: www.crowdsupply.com/excamera/spidriverThanks! |
|
|
|
Post by jasonharper on Aug 28, 2018 7:57:12 GMT -8
Do you have a specific discussion area for the SPIDriver? Mine just arrived, and seems to power up properly, but the software from GitHub won't actually talk to it - I get "CreateFile failed with error 2: The system cannot find the file specified." from spicl, and "SetCommState failed with error 87: The parameter is incorrect." from spigui. OS is Windows 7.
|
|
|
|
Post by jamesbowman on Aug 28, 2018 19:37:16 GMT -8
Maybe a ticket in the SPIDriver repository? github.com/jamesbowman/spidriverDo you know which COM port SPIDriver is on. There may be a problem with COM10 and up. |
|
|
|
Post by jasonharper on Aug 28, 2018 19:47:47 GMT -8
Yes, it was on COM11 - I'll try forcing it to a lower port number tomorrow.
|
|
|
|
Post by jasonharper on Aug 29, 2018 5:53:30 GMT -8
Ok, after forcing the device to COM2 instead of COM11, spicl now works just fine. Yay!
However, spigui still fails with the SetCommState error. I suspect it is finding my COM1 (built-in serial port) first, and failing to set it to the oddball baud rate the SPIDriver uses.
One other issue I've noticed - when I'm writing data with the spicl "w" command, any activity on MISO is being ignored, it shows as constant low regardless of the actual state of the input. It would appear that spicl cannot be used with any device that actually takes advantage of SPI's capability for bidirectional communications.
|
|
|
|
Post by jamesbowman on Aug 29, 2018 17:30:55 GMT -8
|
|
