Re: [Machinekit] How do I access the .ini file?

It sounds like you used a ready baked config so I assume the custom M104 command file is already where it needs to be and setup. You need to specify a value for the Mcode in MDI. Typing M104 isn't going to do anything. "M104 *P50"* would set the value of M104 to 50 This is assuming you have an

Re: [Machinekit] BBB and charge pump

Just a shot here cuz I don't use a BB, or MK much, or charge pumps and I haven't written a hal file in a year lol.. Anyway if I know the purpose of a watchdog timer and the issue you have is trying to generate reliable pulses from a hal software component running on a servo thread? Why not

Re: [Machinekit] Re: any info on the spiPRU mentioned

t; If you don't care about the smoothness of tour motion or use a buffered > approach, usb works fine. > > > Yes, buffered approach is one way to use USB. It really depends on for > what you want to use it, if your application can live with the latency of - > let's say - 5 ms,

Re: [Machinekit] Re: any info on the spiPRU mentioned

> > It's not that simple. USB2 has higher latencies, true, but if you are OK > with them, then the USB2 interface is as capable of real-time communication > as any other interface. There have been attempts to mitigate these > latencies with various results. (Search research papers online.) USB3 >

Re: [Machinekit] Bamboo cnc/limit switch errors

You didnt mention what type of limit switches you're using or how your spindle works. The Y axis itself shouldn't be under any special stress while cutting but the spindle generally takes a hard hit as soon as a tool enters the cut. Is the spindle motor powered by the same power supply your

Re: [Machinekit] question about motion.spindle-on

motion.spindle-on is a pin, "spindle-enable" is your signal. You don't need to trip the "stepgen.NN.enable" pin to have a step/direction servo hold position, you just stop sending it pulses which "m3 s0" should do with no further interaction. disabling the stepgen does not cause the servo to

[Machinekit] SPI ADC hal component?

Just to clarify, I'm interested in using the adc to read voltage not temps. -- 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

Re: [Machinekit] Should I consider Machinekit?

There it is: https://forum.linuxcnc.org/41-guis/38430-replacing-openpnp-motion-controller?start=0 On Sat, Jun 27, 2020 at 2:23 AM justin White wrote: > What kind of host machine are you using? Machinekit has better support for > Beaglebones and some other ARM boards but I believe Li

Re: [Machinekit] Should I consider Machinekit?

What kind of host machine are you using? Machinekit has better support for Beaglebones and some other ARM boards but I believe LinuxCNC is probably better with RaspberryPi's specifically. MK was forked from LinuxCNC long ago, hence the similarities. LinuxCNC has better Mesa support, Machinekit

Re: [Machinekit] Seeed to design and build Machinekit focused Cape for BeagleBone Black/AI

> > > BeagleBone AI uses AM5729, which in contrast to the one used in BBB should > have a Ethercat slave support. You can then use the PRU for exchange of > Ethercat messages and create distributed, multi-node system (multi > Machinekit instances). > I didn't realize that, looking into it it

Re: [Machinekit] Seeed to design and build Machinekit focused Cape for BeagleBone Black/AI

channel or 2 On Wednesday, June 24, 2020 at 6:09:06 PM UTC-4, ce...@tuta.io wrote: > > Hi, > Jun 23, 2020, 20:45 by jkri...@beagleboard.org : > > > On Thu, Mar 12, 2020 at 7:14 PM justin White <> blaz...@gmail.com > > > wrote: > > > >>> On Thursday,

Re: [Machinekit] Re: halcmd setp equivalent in python

Yeah, I forgot Machinekit is in a perpetual state of "this might work the way it used to".or "maybe not". I've recompiled components to swap parameters for pins but I don't think I'd try with a hm2 driver. If all you want to do is set a parameter from an .ini line you don't have to do

[Machinekit] Re: halcmd setp equivalent in python

import hal and: hal.set_p("pinname","value") set_p or "setp" should be universal between pins and parameters. hal.Pin is specifying the Pin class, but you are trying to set a parameter. hal.Param may also work in the same vein as your original attempt on a parameter. On Sunday, May 17, 2020

[Machinekit] Re: Rpi4b instead of BBB

d for them. ;-) > > Hang in there, stay safe! > > Dave > On 3/18/20 5:40 PM, John Dammeyer wrote: > > > > > > *From:* machi...@googlegroups.com [ > mailto:m...@googlegroups.com ] *On Behalf Of *justin White > *Sent:* March-18-20 5:24 PM > *To:* Joh

Re: [Machinekit] Seeed to design and build Machinekit focused Cape for BeagleBone Black/AI

Wow that has absolutely nothing to do with seeed's cape. On Wed, Mar 18, 2020, 7:37 PM John Dammeyer wrote: > Would someone perhaps be able to describe simply (like MachineKit for > Dummy's) how exactly the step pulse and direction shows up on the Beagle > pin relative to the motion command

Re: [Machinekit] Seeed to design and build Machinekit focused Cape for BeagleBone Black/AI

> > On Thursday, March 12, 2020 at 6:32:52 PM UTC-4, Chris Albertson wrote: Isn’t that something the Beagle is strong at with the eQEP and PRUs? >> > > > Strong only until you hit up against the limited number of I/O pins. A > PRU based solution is cheap and simple but can't scale. > > In

Re: [Machinekit] Re: PICnc with Machine Kit.

're on different pages. > > Thanks for your input. > > John > > > > > > *From:* machi...@googlegroups.com [mailto: > machi...@googlegroups.com ] *On Behalf Of *justin White > *Sent:* March-03-20 5:35 PM > *To:* Machinekit > *Subject:* Re: [Machinekit] R

Re: [Machinekit] Re: PICnc with Machine Kit.

> > I thought I was quite clear about this. Not at all, probably because you are misunderstanding the purpose of the hardware you are mentioning in this post. > This PICnc version requires Ethernet. LinuxCNC through a MESA Ethernet > 7i92H or MACH3-4 through an Ethernet Smooth Stepper

Re: [Machinekit] Re: PICnc with Machine Kit.

the idea of using a PIC32 or > something like that for the ELS-MILL. > > > > John > > > > > > *From:* machi...@googlegroups.com [mailto: > machi...@googlegroups.com ] *On Behalf Of *justin White > *Sent:* March-02-20 5:56 PM > *To:* John Dammeyer >

Re: [Machinekit] Re: PICnc with Machine Kit.

Yeah, there is no reason to use ethernet when almost everything has a uart. SPI is a viable rt interface and there is no reason to tie up the processor boards ethernet port. Mesa is using spi with the raspberry pi boards, the 7c80 and the 7c81, so you are pretty much guaranteed it works. Also

Re: [Machinekit] Re: 4-axis CNC running Machinekit won't fully home.

You are going to have to do a bit of digging there, nothing really popping out at me in your ini/hal files and with a home sequence of 0 for all nothing other than a stop request should stop the other axis from homing. Like Charles says, home the Axis' individually to see where your problem

Re: [Machinekit] 4-axis CNC running Machinekit won't fully home.

Give all of your axis a home offset of 10mm and a home of 25mm to get started. Some of them are at 0.0 and probably getting stuck on the switches while homing. On Fri, Feb 28, 2020, 2:34 AM Nathaniel wrote: > Hi, > > I am new to Machinekit and Linux. I am working on an academic project; a >

Re: [Machinekit] Re: DE10 Nano suggested development environment?

a problem deploying MK itself. On Wed, Feb 26, 2020, 4:41 AM Bas de Bruijn wrote: > > > > On 26 Feb 2020, at 01:34, justin White wrote: > > > > Its amazing that mksocfpga doesn't get more interest/support, I dont > think people realize how powerful t

Re: [Machinekit] Re: DE10 Nano suggested development environment?

linux framebuffer driver. --> mksocfpga > > perhaps with some helping hands this functionality can be ported over from > the mister emulator. > > > On Saturday, February 22, 2020 at 9:58:21 PM UTC+1, justin White wrote: > > Any plans to add this to the build script? Playi

Re: [Machinekit] Re: DE10 Nano suggested development environment?

> > It's unfortunately not as simple as the frame buffer is hardwired to the > display parameters in quartus. Resolution change requires changing the FB > parameters in quartus... Generating a new bit file and then generating an > altered device tree with the new display paramete

Re: [Machinekit] Re: DE10 Nano suggested development environment?

> screens if the above doesn't work for you. > > On 2/16/2020 7:46 PM, justin White wrote: > > Been away from this project for a short bit but I had a pretty good use > > come up for it recently. Main thing I'm having a problem with is the FB > > resolution that wa

Re: [Machinekit] Re: DE10 Nano suggested development environment?

Been away from this project for a short bit but I had a pretty good use come up for it recently. Main thing I'm having a problem with is the FB resolution that was configured, 1024x768 is a dead resolution. Only old monitors natively support it and nothing with HDMI does. Larger HDMI monitors

Re: [Machinekit] VFD for 180v DC motor

That KBMG can easily handle that 1hp motor, it's designed for up to 2hp. On a brushed DC motor the torque is directly related to current. If you have a problem with low end torque you probably did not setup the IR comp and CL pots correctly. That drive needs to be setup in speed mode as you are

Re: [Machinekit] VFD for 180v DC motor

Good you got it working. I still dont understand why your pid has 0 Pgain. That's more or less your basic starting point for a pid On Fri, Jan 17, 2020, 7:25 AM Aurelien wrote: > Hello > > Firstly another time many thanks for your help ! > > Yesterday the kbmg was delivered after so much

Re: [Machinekit] VFD for 180v DC motor

I don't know what you mean by "set the index pin as general gpio" if the hpg encoder hardware pins are setup as they should be you shouldn't have a problem. index-enable doesn't reset counts, if "arms" the index-pin itself to reset the counts and the index-enable pin on the next index pulse.

Re: [Machinekit] VFD for 180v DC motor

I don't really understand what you mean here. I thought your problem was the hardware outputs "stick". If "losing" the software enable from Machinekit will drop an output and disconnect a relay then why isn't that relay the drive enable for the KB drive? That's the only relay that needs to

Re: [Machinekit] VFD for 180v DC motor

It does Connect the spindle-vel-fb-rps signal to the pid fb pin. On Thu, Jan 2, 2020, 12:19 PM Aurelien wrote: > One more things, your setup doesn't need "pid.spindle.feedback" ? > > -- > website: http://www.machinekit.io blog: http://blog.machinekit.io github: > https://github.com/machinekit

Re: [Machinekit] VFD for 180v DC motor

The and2 component is fine but what I was assuming was that you were saying the hardware pins were staying frozen in state when the display program crashed. All software enables already drop out so it sounds like the hardware has hungdont think and2 will help you with that. Which is why I

Re: [Machinekit] VFD for 180v DC motor

> > What do you think of this ? > > I think that you should stop changing everything to try to make up for hardware issues. the output of offset needs to stay linked to MAX_OUTPUT as I had it. It needs to match the max output or it's defeating the purpose. you were better off where you

Re: [Machinekit] VFD for 180v DC motor

Why is the PWM pin outputting anything if the input value is 0? You should try commenting out tthe line with hpg.pwmgen.00.out.00.value pin and setp that pin to 0.0. Zero is zero no matter how you scale it. I don't know if maybe your meter is seeing some type of noise on the board or something

Re: [Machinekit] VFD for 180v DC motor

Try increasing the PWM_OUTPUT_SCALE. I don't think the HPG PWM thing is particularly well sorted. I don't know what to tell you about the outputs staying on after a crash. It might be something to do with the way MK controls PRU pins or something. If there is another output pin that does not

Re: [Machinekit] VFD for 180v DC motor

ur dac may not like the PWM frequency it is receiving either changing hpg.pwmgen.00.out.00.pwm_period [SPINDLE]PWM_PERIOD might help that. I would certainly be using a scope to verify the PWM in this case, there's just too much going on here. On Wednesday, January 1, 2020 at 1:50:42 PM UTC-5, ju

Re: [Machinekit] VFD for 180v DC motor

Do you have your motor hooked up, attached to the spindle and your encoder installed and wired in? If not why are you worried about adjusting the PID? you are chasing your tail here. First I have to ask, do you understand that the PID is trying to close the control loop but without having a

Re: [Machinekit] VFD for 180v DC motor

You really shouldn't bother with the pid stuff right now. If you don't have a motor that is driving the encoder you dont have proper feedback to operate the pid. I understand what your trying to see, I'm no pid tuning wizard but I don't think you ever want to add I to a Pid and have P at 0. You

Re: [Machinekit] VFD for 180v DC motor

It's not clear whether you are using the Ebay controller of the KBMG drive. Personally I don't like the 0% DC= max revers, 50% DC = 0, 100% DC = Max forward type of control, but that's upto you. If you are still using the ebay controller why don't you just use the F/R pin on the drive to

Re: [Machinekit] Re: mb2hal?

t; is a couple other user comps. > >>> >> > > >>> >> > I'm not requesting a special lcnc flavored mb2hal, As modbus is a > protocol I would expect a working modbus component to work generically. > What I'm asking is is there a particular reaso

Re: [Machinekit] Re: mb2hal?

y, December 27, 2019 at 6:50:45 PM UTC-5, Michael Brown > wrote: > >> > > >> >> As things are currently I'm certain that if you convert any "simple" > existing mk userspace component and replace the functional code with > >> >> that lcnc m

Re: [Machinekit] Re: mb2hal?

back then. Here is my base source for Modbus > information: http://www.modbus.org/specs.php . They seem to stress that > Mobus and the transport systems are separate but cooperative entities -- > maybe like TCP is separate from IP. > > > On Sat, Dec 28, 2019 at 7:41 AM justin

Re: [Machinekit] Re: mb2hal?

cted and lastly create a PR.. > >> Someone eventually will forward the pr request into the repo ... :-) > >> > >> Best wishes > >> Michael Brown > >> > >> On Friday, December 27, 2019 at 4:46:09 PM UTC+1, justin White wrote: >

[Machinekit] Re: mb2hal?

PR.. > Someone eventually will forward the pr request into the repo ... :-) > > Best wishes > Michael Brown > > On Friday, December 27, 2019 at 4:46:09 PM UTC+1, justin White wrote: >> >> Bump...not alotta interest in modbus in my eh? > > -- website: http://www

[Machinekit] mb2hal?

Bump...not alotta interest in modbus in my eh? -- 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

[Machinekit] mb2hal?

It was suggested to me to use mb2hal for some remote communication from a LinuxCNC box to a MK box which actually seems to be a good idea. It looks like MK does not include this component. Without looking too far into it yet it just looks like a simple userspace component. Any particular reason

Re: [Machinekit] Is there any simple MK approach to a remote UI?

9 at 10:40:20 PM UTC-5, mlampert wrote: > > I believe the functionality you're looking for is in > > https://github.com/mlampert/Machinekit-Workbench/blob/master/MKServiceHal.py > > Anyway, it is indeed a programming interface and not a remote hal shell. > > > On Thu, 5 Dec

Re: [Machinekit] Is there any simple MK approach to a remote UI?

K2 uses for signals/notifications. > > Other than that you are expected to call _update() in machinekit.py > periodically for service discovery and message processing. > > HTH and let me know if you have any questions. > > > On Wed, 4 Dec 2019 18:17:42 -0800 (PST) > j

[Machinekit] Is there any simple MK approach to a remote UI?

Every once in a while I sit down and try to get something going in QT creator for remaking My project machine LinuxCNC GUI to QT for use with a remote instance of Machinekit. Right now this machine runs LinuxCNC with a mesa 7i96, and it works just fine, however my ideal setup is to use

Re: [Machinekit] Re: side-by-side install linuxcnc and machinekit

LinuxCNC was the open source continued developement of EMC > EMC2 which was developed by NIST as a government awarded contract then dropped. Some years ago Machinekit was forked off of LinuxCNC because I believe some of the LinuxCNC devs were not happy with progression and the time it took to

[Machinekit] Re: side-by-side install linuxcnc and machinekit

I went through the JA switch with LinuxCNC when I started using a Mesa 7i96 which was only supported in 2.8pre1 not 2.7. 2.8+ will prompt to rewrite the hal and ini files automatically, but I had a PIA of a time with Python stuff because they added an extra argument to select control of the

Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96

t; >> Secondly you have to compare this unique bargain in the right direction >> (not with a BB AI / rRPI4 or the like), but with >> something that has the same chip like this: >> >> https://www.xilinx.com/products/boards-and-kits/zcu104.html >> >

Re: [Machinekit] Re: OSHW release DE10-Nano Daughtercard

udo apt update && sudo apt upgrade > The new bitfiles are then pulled into his/hers system and automatically > placed in the correct folders. > > > > > On Monday, 30 September 2019 23:21:07 UTC+2, justin White wrote: >> >> Forked and created a new P

Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96

I want to like the ultra96 but for the price..I dunno. Not that it's bad, it's just the DE10-Nano fits the mksocfpga idea I had in mind better. The whole Idea was to keep the graphics and everything off the cpu running HAL and hal as close as possible to the FPGA. I do like the framebuffer

Re: [Machinekit] Re: OSHW release DE10-Nano Daughtercard

; in order else place your corrections as a commit message. > Best wishes > Michael B. > > On Monday, 23 September 2019 05:34:48 UTC+2, justin White wrote: >> >> I've decided to release the board I've been working on pretty much as is, >> just with some open source consider

Re: [Machinekit] Re: Rotary CNC + Bamboo + BBB + CRAMPS?

On Saturday, September 28, 2019 at 11:44:17 AM UTC-4, Bas de Bruijn wrote: > > > > Why the BB AI? What holds you back in the BBB? > > Bas > Kind of an old thread but as he said above he wants to use machine vision cameras with it. The BB AI still has minimal cpu and ram, but apparently it has

Re: [Machinekit] Re: What potential hal implementation change could a low cost soc-fpga bring to the table ?

most MK setups we do the motor commutation of > brushless motors and stepper motors in special controllers that we buy. > But if you look inside these controlerss they are not much more than a > microcontroller (or DSP chip) and some MOSFETS. An FPGA would be good at > this. > > &

Re: [Machinekit] Re: What potential hal implementation change could a low cost soc-fpga bring to the table ?

So what is special about socfpga that makes this specific to socfpga chips rather than just an FPGA communicating to the CPU in another form? If I'm following the idea right we're basically talking about running hal components individually as FPGA soft cores. I follow that idea but what is the

Re: [Machinekit] OSHW release DE10-Nano Daughtercard

etest the 8i20 on a different setup to confirm that it works > correctly, > if so can you reference this exact setup (software HW etc) ? > > Michael B > > On Wednesday, 25 September 2019 23:40:11 UTC+2, justin White wrote: >> >> So i got my 7i66 and I have no probl

Re: [Machinekit] OSHW release DE10-Nano Daughtercard

the 8i20 hm2 driver in MachineKit is broken unless someone knows otherwise. Any of the MK devs able to take this on? On Tuesday, September 24, 2019 at 10:09:58 PM UTC-4, justin White wrote: > > It was brought to my attention that I should probably have termination > resistors on the dif

Re: [Machinekit] OSHW release DE10-Nano Daughtercard

It was brought to my attention that I should probably have termination resistors on the differential encoder inputs. While it was fine in testing, after doing some research I'd have to agree. I slapped some pdf schematics in there as well. Also improved the differential signal routing. On

Re: [Machinekit] Re: OSHW release DE10-Nano Daughtercard

cfpga oshw daughtercard release :-) > > Michael > > > > On Monday, 23 September 2019 17:02:56 UTC+2, justin White wrote: > >> > >> [image: DE10nano interface.jpg] > >> > >> [image: Photo Sep 23, 10 50 34 AM.jpg] > > -- > Charles Ste

[Machinekit] Re: OSHW release DE10-Nano Daughtercard

If there is interest I may offer assembled boards. Not sure what they would cost exactly, probably $100-$150 but I haven't tried to figure that out yet. -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message

[Machinekit] OSHW release DE10-Nano Daughtercard

I've decided to release the board I've been working on pretty much as is, just with some open source considerations. It was intended for a specific machine, but I rung out all of the I/O possibillities I could, no DE10 GPIO pin went unused. There is an onboard 5v regulator that will power the

Re: [Machinekit] Weird idea?

is for cell phones and don't realize how powerful it really can be if the support and infrastructure exists..instead, cobbled up images relying on vendor patched Linux Kernels. On Sat, Sep 21, 2019 at 4:08 AM Bas de Bruijn wrote: > > > On 21 Sep 2019, at 03:10, justin White wrote: >

Re: [Machinekit] Weird idea?

The FPGA is LinuxCNC's magic bullet because FPGA's in general are magic bullets. IMHO, mksocfpga could also be Machinekit's magic bullet in a way that is even more potent that off the shelf Mesa hardware. This is what LinuxCNC is missing, and Machinekit is not quite exploiting enough. The

Re: [Machinekit] Weird idea?

The bbb I/o is 3.3v so you’ll want to take a look at the manual for the driver and see if it can accept 3.3v or it must be 5v. The if it must be 5v you would need a level shift solution which is what most cape hardware does for you. If bbb gpio is sourcing and your motor driver has both plus

[Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96

What's the I/O on this thing look like in hm2? On Thursday, September 19, 2019 at 8:19:55 PM UTC-4, Michael Brown wrote: > > I have released a Ultra96 beta sd Image including (a) mksocfpga bitfile > > For those

Re: [Machinekit] Weird idea?

@cern Curious, what is the state of machinetalk? I am at some point planning on running a remote GUI, pretty much as you described with a de10 nano as the RT pc/FPGA and some ARM or small X86 running the interface. I didn’t get too far in depth of what I need to do with remotely controlling

Re: [Machinekit] Weird idea?

What do you need to control the 3 servo drives? Are they step/direction with encoder feedback to the controller or the driver? Sent from my iPhone > On Sep 18, 2019, at 10:26 AM, Berkdan Kara wrote: > > Thank you Justin and Bas for quick response. > > I know about Mesa cards, but it takes

Re: [Machinekit] Weird idea?

He obviously wants to use something small so a pc with a PCIe FPGA probably isn’t his goal. But I agree, it’s not really a good idea, the raspberry pi can’t be used “like an FPGA” because it’s not an FPGA. Generating steps in software on a RPI and sending them out over GPIO while remotely

Re: [Machinekit] mksocfpga DE10-Nano encoder index issue (latency?)

re - for example - only counting something improperly in > Machinekit-HAL (can be - as I said - the problem with non-RT access to HAL > from GUI), or if the whole FPGA firmware is shot. > > So, please, tell me exactly what you are doing inside the HAL. > > Cern. > > &

Re: [Machinekit] Odroid N2 RT kernel readiness?

I’m not sure what device the s922x is used in but yes, it’s meant for an Android set topthen again that’s exactly what the RK3399 is designed for, hence the Mali gpu’s. Almost anything running a Mali GPU is meant for an Androidtv box or phone. What’s important is the ARM cores on the chip

[Machinekit] Odroid N2 RT kernel readiness?

As I mentioned in another post, I'm a big fan of this SBC, It's got the most powerful consumer ARM chip I've used and there seems to be a major interest in bringing the board into the mainline kernel, which may be well on it's way by now. I haven't had the time to try building an RT-preempt

[Machinekit] Re: ROCKPro64 + Mesa 6i24 or 6i25 What are your thoughts on this low cost mini combo

That's pretty much how it goes on ARM SBCs, the vendor has to apply a varying amount of patches to the Linux kernel for it to have decent functionality because the SOCs are generally designed to be run on Android with all sorts of proprietaryness. I went on an ARM board kick and bought up all

Re: [Machinekit] ROCKPro64 + Mesa 6i24 or 6i25 What are your thoughts on this low cost mini combo

Is the appeal the direct PCI slot? Mesa has a just released 7c81 that the raspberryPi sits right on top using SPI but it’s not an anything I/O card therefore you have to use it with another card. Last I checked they didn’t release the 7c80 yet but that card has useable I/O onboard. The 7c80

Re: [Machinekit] mksocfpga DE10-Nano encoder index issue (latency?)

ut it looks like using a timer with a negative value helps account for latency issues in hm2 reads. Probably won't help with the index thing but the encoder velocity feedback tends to be all over the place below 100rpms, figured it may help with that. On Saturday, September 14, 2019 at 5:41:06 PM UTC-4, ju

Re: [Machinekit] mksocfpga DE10-Nano encoder index issue (latency?)

UTC-4, justin White wrote: > > The "GUI" isn't counting the pulses. As I said/ I'm using the hal > component "updown" which is a RT component as any other. That component > outputs an unsigned integer that I just push to a gladevcp hal label. So > it's being &

Re: [Machinekit] mksocfpga DE10-Nano encoder index issue (latency?)

The "GUI" isn't counting the pulses. As I said/ I'm using the hal component "updown" which is a RT component as any other. That component outputs an unsigned integer that I just push to a gladevcp hal label. So it's being "counted" at the servo thread rate of 1ms or the .5ms that I briefly

[Machinekit] Re: mksocfpga DE10-Nano encoder index issue (latency?)

at 2:48:24 PM UTC-4, Michael Brown wrote: > > I would find it easier to follow you line of thought in this bug report if > you would state the purpose.. > So why ? > And what are you trying to achieve ? > > On Saturday, 14 September 2019 20:04:42 UTC+2, justin White wrote: >>

[Machinekit] mksocfpga DE10-Nano encoder index issue (latency?)

Doing a little testing on my hardware I noticed there is an issue with encoder indexes being missed while trying to count them. It's difficult in hal to see the index pin change state on an encoder with reasonable resolution because the change in state is very short. So I added the function in

Re: [Machinekit] Re: DE10 Nano suggested development environment?

I had to make some changes to the pin routing of my board for the encoders. I assume the quartus config changes haven't been applied to the docker environment yet? @ Michael, if not can you build firmware with this .vhd file? On Friday, August 30, 2019 at 12:12:02 AM UTC-4, justin White

Re: [Machinekit] Re: DE10 Nano suggested development environment?

t; > A board schematic (with pins connectors wires components etc...) ? > preferably open source... > > > On Thursday, 29 August 2019 23:42:04 UTC+2, justin White wrote: > > What are you looking for? > > > On Thursday, August 29, 2019 at 1:00:54 PM UTC-4, Michael Brown wr

Re: [Machinekit] Re: DE10 Nano suggested development environment?

bug efforts here to have the physical > board(s) on hand. :-) > > I can PM you my street address when you have it build t and ready... > > On Wednesday, 28 August 2019 03:54:49 UTC+2, justin White wrote: > > After looking at it I wonder if it is not just the 8i20 portion of SSer

Re: [Machinekit] Re: DE10 Nano suggested development environment?

to give you bad info since I'm not totally sure I understand why I'm getting the results I'm getting. On Tuesday, August 27, 2019 at 8:26:00 PM UTC-4, justin White wrote: > > New deb is still not working for SS although there is a minor change that > I did not see before. the card sta

Re: [Machinekit] Re: DE10 Nano suggested development environment?

packages, > then you don't have to build yourself. > > > > > On Tuesday, 27 August 2019 00:51:56 UTC+2, justin White wrote: >> >> BTW, have the DExx-cramps changes been merged in a way that I can do a >> docker build on my end yet? >> >> On Monday, Augu

Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96

allel GPIO pins > (DExx style) ? > > >> On Tuesday, 27 August 2019 01:01:43 UTC+2, justin White wrote: >> Curious what the current use case for the ultra96 might be. There's >> mezzanines available that are suitable for machine control as far as I'm >> aware. T

Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96

Curious what the current use case for the ultra96 might be. There's mezzanines available that are suitable for machine control as far as I'm aware. The "high density" "low density" gpio connectors look like a PIA to work with. If they stuck that SOC on a form factor similar to the DE10 Nano

Re: [Machinekit] Re: DE10 Nano suggested development environment?

BTW, have the DExx-cramps changes been merged in a way that I can do a docker build on my end yet? On Monday, August 26, 2019 at 6:49:23 PM UTC-4, justin White wrote: > > There are comm errors thrown after discovery as mentioned on git, trying > to determine if its the hardware or

Re: [Machinekit] Re: DE10 Nano suggested development environment?

There are comm errors thrown after discovery as mentioned on git, trying to determine if its the hardware or MK's hm2 driver ATM, Still a bit difficult to determine without a verifiable working instance of SS in current MK systems. -- website: http://www.machinekit.io blog:

Re: [Machinekit] Re: DE10 Nano suggested development environment?

tretch_armhf.deb >> >> I added the other one just in case... >> >> On Saturday, 24 August 2019 20:19:36 UTC+2, Michael Brown wrote: >> >> Got some scope results: >> https://github.com/machinekit/mksocfpga/issues/107#issuecomment-524570613 >> >>

[Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96

On Sunday, August 25, 2019 at 11:54:32 AM UTC-4, c.gl...@cox.net wrote: > > The Ultra96 is simply the most powerful embedded processor I've ever used! > > When loaded with PYNQ, a Python environment that runs in Jupyter it turns > into a powerful platform for FPGA development. Using a Ultra96

Re: [Machinekit] Re: DE10 Nano suggested development environment?

: > Got some scope results: > https://github.com/machinekit/mksocfpga/issues/107#issuecomment-524570613 > > > On Saturday, 24 August 2019 19:31:04 UTC+2, justin White wrote: >> >> @Michael, if ya need any info from my LCNC machine let me know. It's not >> MK bu

Re: [Machinekit] Re: DE10 Nano suggested development environment?

, might be useful if you get an SS remote on hand. On Saturday, August 24, 2019 at 1:20:09 PM UTC-4, justin White wrote: > > I'm not sure if this helps you but SS pins always look like normal I/O if > they don't detect a remote on the channel after coming up. Since I have it > out I connec

Re: [Machinekit] Re: DE10 Nano suggested development environment?

I'm not sure if this helps you but SS pins always look like normal I/O if they don't detect a remote on the channel after coming up. Since I have it out I connected the 8i20 to my project machine's 7i96 that I don't typically use SS with. This is LinuxCNC 2.8pre1 No 8i20 connected, note IO

Re: [Machinekit] Re: DE10 Nano suggested development environment?

ost the exact hal commands for probing the tx line here ? > I have a Pisoscope 3206D MSO, so I can test that on my (Dev) DE10_Nano > > > On Friday, 23 August 2019 23:53:58 UTC+2, justin White wrote: > > Still no go for SS on the 8i20. Can anyone confirm that SS actually works &g

Re: [Machinekit] Re: DE10 Nano suggested development environment?

t;> OK found the flaw in that commit (leading to currupt io), and was able to >> fix it. >> Expect a new bit file in about 2 docker compile times :-), 1/2 hour >> or so... >> >> On Friday, 23 August 2019 15:56:59 UTC+2, justin White wrote: >> >> lol thanks, I

Re: [Machinekit] Re: DE10 Nano suggested development environment?

uartx8:\makeUARTTXs:0:auartx 75.2 (56.5) 102.7 (56.8) 27.5 (0.3) 0.0 >>>>> (0.0) 0.0 (0.0) 95 (95) 197 (63) 0 (0) 0 0 0 0 0 >>>>> SRL16E:\fifosrl:0:asr16e 3.7 (0.0) 4.8 (0.0) 1.2 (0.0) 0.0 (0.0) 0.0 >>>>> (0.0) 0 (0) 16 (0) 0 (0) 0 0 0 0 0 >>>&

Re: [Machinekit] Re: DE10 Nano suggested development environment?

.2 (56.5) 102.7 (56.8) 27.5 (0.3) 0.0 >>>> (0.0) 0.0 (0.0) 95 (95) 197 (63) 0 (0) 0 0 0 0 0 >>>> SRL16E:\fifosrl:0:asr16e 3.7 (0.0) 4.8 (0.0) 1.2 (0.0) 0.0 (0.0) 0.0 >>>> (0.0) 0 (0) 16 (0) 0 (0) 0 0 0 0 0 >>>> look fine now >>>> >>>>

  1   2   >