Advanced Search

Is that just a y thing?

Is it possible to run all these things together: 

Mesa 7i76 E  ---- 7I84 (Isolated remote field I/O card). Will use it to output quadrature signals to the Ultra3000s, it will generate this quadrature output from the Fanuc encoders [is this possible?], remaining I/O used elsewhere. 
                               
                         ---- 7I85 (4 Channel encoder 5 channel Serial RS-422 interface). Will hook up the 4 Fanuc redcaps to 4 of these RS-422 ports. And the encoder inputs are good to have around incase I want to add linear scales (2 axis) and maybe two MPG wheels. 

Sure would be great if this system worked because it happens to be two fairly inexpensive boards. Canadian dollar isn't so great right now 
I would be pleased to have those encoder inlets, too. 

Progress pic from a little while ago: 
 

Licenses were reviewed in depth by Debian as part of getting into their distros. (There are many different licenses) I think you can say the differences in licenses is not a conflict or we would not be in Debian

If the axis do not move, I would check:

1. That you don't have a watchdog bite
(If you are running "Axis" it will report this if not,
you may need to check with halshow)


2. The physical wiring (remember I asked what were the
connections between TB2 pins and drive signals?)


3. The timing specifications of the drives (the current timings should work
with most drives but there are so oddball drives with really slow inputs)


 

Y cannot jog until it is homed.

andypugh wrote:

Is there any chance that this corresponds to something in the kinematics? Maybe an inflection point in one of the joints?

Its possible that at that point another joint starts contributing to the motion.
Think of 2D motion on X & Y at 45 deg at max velocity. Both axes will be moving at their max, but the total combined axis velocity  will be about 40% higher.

okay update. 

I reran the pncconf, reassigned the second y as a tandem and also corrected what turns out was mis-assignment by me initially. Everything should be good to go now in terms of what the board thinks is assigned and what is actually. Updated hal and ini attached. 

Still no movement from any axis:
X: Does nothing physically but machine thinks its jogging (DRO updating)
Y: Throws an error: "Cannot Jog Joint 1 because home_sequence is synchronized 
Z:Does nothing physically but machine thinks its jogging (DRO updating)
A: Does nothing physically but machine thinks its jogging (DRO updating)

totally make sense thanks for your help.

I just went to restart the pncconf and i only have three options when it comes to kinematics: XYZ, XYZA, OR XZ lathe. I believe i am missing some options here in this drop down.

edit: im stupid, trying again now. 

AlexMagToast wrote:

Good that you mention Python. A couple weeks ago I learned how to build custom .comp components and I was thinking about moving the communication and logic Part into one.
But I am not sure how much this would improve anything. I guess the Bottleneck is the USB Serial anyway? What do you guys think?
 

Yeah, problem there is you can only access a serial port from userspace otherwise it would be good. USB you would probably have to throw out the window, but if someone wrote an actual real-time serial port driver it'd probably be great.

I'll probably fork your repo and push my changes for the I2C IO expanders if you want to take a look at that. Could use some work around the ifdef's for enabling the I2C IO aside from the normal Arduino IO but on my Mega setup it's working great.

Unfortunately I didn't have enough interrupt pins when I made that board and I figured they probably wouldn't be necessary for just knob type encoders but that was a mistake. My MPG uses both interrupts and it works fine, my other encoders work terrible. Now I'm trying to resurrect the board I made for a Teensy 4.1 since they are all interrupt pins. Having a bit of trouble with the I2C on that one for some reason.

Just a note, the 7i90, FPGA (not having a go but there is always some that breaks the rules) can be used as smart serial device. Just digital i/o and 3 mpgs, but the firmware that runs on the softcore can be modded for 4
Mpgs. Tho it was a little frustrating to do at first. 

Yeah, you could use those cards for whatever you want but there's no analog IO on the 7i90/7i92 so you can't really call it a control panel card unless it can do a basic potentiometer reading.

I don't have any pots so I was thinking about using a 7i92 I have laying around. The smart serial cards don't work out well for my case cuz they run off the host card. So I'd be mounting PC inside the control panel  and the ethernet host card in the machine cabinet. So ethernet from the control panel to the machine cabinet and smart serial back to the control panel. That's kind of messy and the control panel can't work standalone.

With a 7i92 I'll just tie up the 2nd ethernet port on my mini-pc, but that's probably not a big deal. I've already used modified 7i92's on custom daughtercards so I already have the PCB footprints and schematic symbols made.....

 

Problem there is there's no I2C module for hm2 that I'm aware of so I'd have to remake my key panel again to use spi IO expanders then BSPI is a bit tough to deal with. I got BSPI almost working for the board in the pic because it has 2 small microcontrollers that communicate with the 7i92, one is actually just for reading analog inputs. I got busy and left that project on the shelf too.

I'll probably just stick with the Arduino-connector setup once I get my Teensy 4.1 version working right for now. The mini-PCs I use have the Intel UARTs so if there's ever a real-time serial port solution I can just migrate over to that.

Motor current.