Forum Replies Created
-
AuthorPosts
-
April 28, 2016 at 8:19 am in reply to: Serial interface no longer shows after flashing a Due on Mac OS 10.6.8 #9622lincobMember
You’re right… My bad… I actually got the information from this page… having a couple of dozen of tabs opened, i haven’t realized until now the page was actually referring to the TinyG board only, which obviously have an FTDI chip… Since I can’t find how to edit the second post, it would be nice to delete the bold comment from it.
The status remains the same, it must be driver related but the info i provided about the FTDI drivers must be wrong.And now we know what the current Edge will build ($fb=89.03).
A precision though, the build actually failed… I’ve solved it commenting out those two lines from config_app.cpp.
{ "sys","mfoe",_fipn,0, cm_print_mfoe,get_ui8, set_01, (float *)&cm.gmx.mfo_enable, MANUAL_FEEDRATE_OVERRIDE_ENABLE}, { "sys","mfo", _fipn,3, cm_print_mfo, get_flt,cm_set_mfo,(float *)&cm.gmx.mfo_parameter, MANUAL_FEEDRATE_OVERRIDE_PARAMETER},
I’ve later on found this issue. Which have not been committed to the edge branch. I’ve edited the config_app.h file manually, and build was successful.
Using a wifi connected Pi as your SPJS target should work OK, if it seems sluggish consider a Pi2
I’m actually using a Pi2… I will report the results using wifi, but i have to build the CNC first 😉
I am actually a little surprised that changing the driver was the cause – DUE does not use FTDI devices, on Linux ports appear as /dev/ttyACM_, …. ?
Yes, on the Pi2, both serial ports show up straight from the Raspbian distrib :
pi@raspberrypi:~ $ ls /dev/ttyACM* /dev/ttyACM0 /dev/ttyACM1
As you probably realize, you could now run CP from a well performing tablet or phone, should you wish
Yes !… I’ve tried from my phone and it’s actually quite amazing !!
April 28, 2016 at 5:25 am in reply to: Serial interface no longer shows after flashing a Due on Mac OS 10.6.8 #9616lincobMemberHi,
Thanks for your answer… I’ve tried with the 72.08 but same problem occurred…
After further investigation, as i’ve found somewhere in some other post, it is actually driver related. The fact that i was actually lacking confidence about my ability to compile binaries sure didn’t help ! 😉
I was bothered not to have another computer around to test the serial port… But that was forgetting about my Raspberry Pi… I’ve installed the latest Raspbian, installed go (hint : don’t install from apt-get as it installs a really old version), compiled the serial json server… And the G2 now works flawlessly (with both FW versions)… Here is the start of the output of the $$ command :
{"r":{"fv":0.98,"fb":89.03,"hp":3,"hv":0,"id":"0213-2335-e323","msg":"SYSTEM READY"},"f":[1,0,1]} tinyg [mm] ok> [fb] firmware build 89.03 [fbs] firmware build " build" [fv] firmware version 0.98 [cv] configuration version 7.00 [hp] hardware platform 3.00 [hv] hardware version 0.00 [id] TinyG ID 0213-2335-e323
Used chilipeppr over network and seems to work fine for the moment.
I was first a bit scared of the process of building and configuring TinyG G2 on due (compared to other arduino IDE based solutions)… But i can tell you that even for a less than qualified person like me, the process is quite straightforward and easy.
About the Mac… the problem lies in the VCP FTDI drivers, which apparently requires the 2.3 version (only available from OS 10.9 though)… So basically, on all previous versions, you’re stuck with 2.2.18 version drivers and it simply doesn’t work.
However i’m still able to control the board from the mac through LAN/WLAN using the Pi, i don’t know if the network latency will do with buffers and stuff, but that’s another issue, i will find a workaround if i’d happen to run into problems with that.
So… now that i have a working G2 with Due… Let the adventure begin. Thanks for your help, i’ll sure come back with more questions 😉
-
AuthorPosts