[Machinekit] Re: DE10 Nano suggested development environment?
> > Have you whached the presentation Charles linked to ? > > Actually I've seen the presentation about twice before it was mentioned here. Just for reference, I'm not really trying to build the Quartus image right now I'm just trying to figure out the actual FPGA pin usage so I know how to interface it. My experience with Mesa cards is the AIO Eth cards like the 7i76e and 7i96. In those cases the actual pins are already hardware interfaced as in you wind up with a 6 pin differential encoder input, and 4 pin step gen outputs. Without looking at the vhd file, I probably would not have realized that it actually only uses 3 FPGA pins for the encoder and 2 FPGA pins for the stepgens. > The xxx_Cramps (quartus project) configs are the only current configs that > provide ADC functionality straight into the Hal, the tags are there so that > the hostmot2 soc hal driver can pick them up if needed. > > With the DE0_Nano_SoC board the (xxx_CRAMPS) ADC functionality works as it > is supposed to, for some mystical reason this is not the case with my 2 > DE!0_Nano boards, so I'm trying to debug this issue currently. > As for the ADC I just realized where I was getting confused there. I didn't realize the ADC was an SPI interface (had to read the manual again). I thought they were direct connections to the FPGA. That explains why the ADC header doesn't appear as a separate 8 pin section in the vhd file. Even though you may have written this earlier (someplace else) > I would be great for me if you can place a description or a link as to > what you are aiming to accomplish, so that I then can come up with more > presice answers pointing you in the right direction. > > That's kind of difficult to say. Specifically I want to work up an interface board for the DE10 Nano that's more or less specific to my project machine. While I don't really need half of what I want to stuff in there, ultimately a little extra time on the schematic and a couple of chips and resistors is really all that extra functionallity costs. Less specifically I've been working on a machine vision imaging system for some time now. It's kind of a niche thing so it's hard to explain it's actual purpose. This is like one of those probably never ending projects that have any rational reasoning behind it, other than I've had to teach myself quite a few different things every time I decided to do something different. First I built a raggedy "proof of concept" running on LinuxCNC/Mesa. Then I Converted a Small Mill to CNC once again running on LinuxCNC to prototype some more reasonable parts. After designing the whole thing I realized I wasn't super happy with all the bulk of the off the shelf components so I learned KiCAD and started whipping up PCBs. I built a a whole Glade GUI for it and a friend of mine has done all of the custom programming. It currently runs on a reasonably powerful x86 PC that I built to be small and use a DC-DC power supply so I can run the whole machine on a single 24v supply. What happens there is that I wind up needing More CPU than actually necessary because displaying the cameras uses quite a bit of processor and it leads to high jitter on a marginal PC. I've gotten on an ARM kick recently (I've got about 8 SBC's running all sorts of stuff, no Pi's though) and realized that if I can run Machinekit on something like the DE10Nano, I can keep the RT layer off the CPU that is connected to the camera's and there's the added bonus that the FPGA is built right into the same chip as the processor so that hardware becomes very small and low power. On top of that I no longer actually need a fast X86 at all. Image processing, without GPU acceleration spreads out very evenly along CPU cores so these newer 6 core ARM processors handle it pretty well. I picked up an Odroid N2 when it was released so it's not really wel developed under Linux but it still handled it pretty well So yeah there's quite a bit of work to be done to get it running under MK but I figured I'd start by trying to make the DE10 useable as a hardware controller first. https://www.dropbox.com/s/66sjfddnhj5u0mg/Video%20Sep%2007%2C%209%2014%2016%20AM_0.mov?dl=0 https://www.dropbox.com/s/tflf1rtmt8aof5q/remmina_Viewer1%20VNC_192.168.1.108_2019131-14244.932851.jpeg?dl=0 -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: DE10 Nano suggested development environment?
On 5/6/2019 4:42 PM, mib.holotro...@gmail.com wrote: > On Monday, 6 May 2019 19:32:47 UTC+2, justin White wrote: > > I'm still trying to find some info on some of the "tags" used in the hm2 >> vhd files, I don't suppose this is documeted somewhere? >> > Have you whached the presentation Charles linked to ? In addition to the recorded presentation, you can get the slides I used from github: https://github.com/cdsteinkuehler/Presentations/tree/master/2017.04.29.Machinekit_Meetup -- Charles Steinkuehler char...@steinkuehler.net -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
[Machinekit] Re: configure touchy
On Saturday, May 4, 2019 at 10:44:17 AM UTC-5, scala...@free.fr wrote: > > Hello everyone, > is there a step by step to configure machinekit with touchy? > > > Touchy requires an MPG (hand wheel encoder) and a start and stop button available as HAL pins. You scroll through file lists and a number of other things using the MPG, and you execute G-code programs with the start button. So, those are hardware requirements. Jon -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
[Machinekit] Re: DE10 Nano suggested development environment?
On Monday, 6 May 2019 19:32:47 UTC+2, justin White wrote: > > Wonder which human readable file you are refering to as the bitfiles are >> the binaries (*.rbf) generated by quartus from the *.vhd and *.sv, *.v >> source files... >> > Was talking about Mesa's .vhd files. > > I'm no electronics expert... The datasheet for my single ended encoder >> says max 30 mA, so I figured 220 ohm at 3.3volts gives max 15mA or so... > > That would be the current handling ability of the encoder's outputs, but > all you have to do is drive an FPGA pin. That takes almost no current to > do. Since you want to make sure that that FPGA pin has a defined state when > it's not being driven you need to pull it toward one side with a resistor. > If you use a strong pullup/down it requires more current to drive it toward > the other side. The 15mA is being wasted through that resistor. 15mA isn't > a big deal but if you have alot of I/O it'll add up. > Sure the 220 ohms are just for initial test purposes and to make certain I dont pickup noise as I'm running a 2 meter cable from the encoder to the soc. > > If your FULL error message is: >> > It literally just prints out "segmentation fault". I just tried it on one > of my other Linuxcnc machines and if LinuxCNC is running, I can open a new > terminal and cd to the halshow.tcl directory and ./ to execute it just as > if I started it in the GUI. That doesn't work on this image even after > using the export command you mentioned. I'll have to try updating the > packages you mentioned and see if that helps. > > you cannot update directly to the -cnc -hal machinekit packages I think... best way is to remove the old packages with sudo apt purge then sudo apt autoremove You may get some complaints (when installing the new packages) about yapps, when installing solution is to uninstall/purge that package also. I'm still trying to find some info on some of the "tags" used in the hm2 > vhd files, I don't suppose this is documeted somewhere? > > Have you whached the presentation Charles linked to ? > I see the "capsense" tags but I'm not sure what that is, something Cramps > related? > Capsense is a new touch sensor core I have added not mesa related..(You can safely ignore that). > > Some of the Mesa PWM implementations are a 3 pin deal with an enable and > direction pin. The MK configs only seem to use the "PWMAOutPin" per unit. > Looking at a top level vhd file it appears that the PWMBDirPin, and > PWMCEnaPin are there. I suppose it's just a matter of including these pins > in that unit? > As Charles stated earlier this is complicated stuff to understand and the options are vast. You have to be more verbose as to what you are aiming to get up and running. I only have the info you have provided in this thread and I have no idea of what your goal is. There is a NANOADCTag listed in the ModuleIDs but I haven't found any usage > of it other than that. Is that just a placeholder or does it have an > implementation? > The xxx_Cramps (quartus project) configs are the only current configs that provide ADC functionality straight into the Hal, the tags are there so that the hostmot2 soc hal driver can pick them up if needed. With the DE0_Nano_SoC board the (xxx_CRAMPS) ADC functionality works as it is supposed to, for some mystical reason this is not the case with my 2 DE!0_Nano boards, so I'm trying to debug this issue currently. Even though you may have written this earlier (someplace else) I would be great for me if you can place a description or a link as to what you are aiming to accomplish, so that I then can come up with more presice answers pointing you in the right direction. Best wishes Michael Brown -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
[Machinekit] Re: DE10 Nano suggested development environment?
> > Wonder which human readable file you are refering to as the bitfiles are > the binaries (*.rbf) generated by quartus from the *.vhd and *.sv, *.v > source files... > Was talking about Mesa's .vhd files. I'm no electronics expert... The datasheet for my single ended encoder > says max 30 mA, so I figured 220 ohm at 3.3volts gives max 15mA or so... That would be the current handling ability of the encoder's outputs, but all you have to do is drive an FPGA pin. That takes almost no current to do. Since you want to make sure that that FPGA pin has a defined state when it's not being driven you need to pull it toward one side with a resistor. If you use a strong pullup/down it requires more current to drive it toward the other side. The 15mA is being wasted through that resistor. 15mA isn't a big deal but if you have alot of I/O it'll add up. If your FULL error message is: > It literally just prints out "segmentation fault". I just tried it on one of my other Linuxcnc machines and if LinuxCNC is running, I can open a new terminal and cd to the halshow.tcl directory and ./ to execute it just as if I started it in the GUI. That doesn't work on this image even after using the export command you mentioned. I'll have to try updating the packages you mentioned and see if that helps. I'm still trying to find some info on some of the "tags" used in the hm2 vhd files, I don't suppose this is documeted somewhere? I see the "capsense" tags but I'm not sure what that is, something Cramps related? Some of the Mesa PWM implementations are a 3 pin deal with an enable and direction pin. The MK configs only seem to use the "PWMAOutPin" per unit. Looking at a top level vhd file it appears that the PWMBDirPin, and PWMCEnaPin are there. I suppose it's just a matter of including these pins in that unit? There is a NANOADCTag listed in the ModuleIDs but I haven't found any usage of it other than that. Is that just a placeholder or does it have an implementation? -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
[Machinekit] from fdm.config import velocity_extrusion as ve problem machinekit
Hi,I am trying to run Fabrikator-Mini configuration on BBB but it gives me error which is at below. 'from fdm.config import velocity_extrusion as ve' https://machinekoder.com/mini-3d-printer-from-hobbyking-running-with-cramps-board-and-machinekit/ I tried to copy fdm folder and remove config but it did not work. https://ibb.co/BGzqwWM this is my problem photo.Can you explain what the problem is ? Thank you -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
