Advanced Search

I had previously linked the PC directly to the Mesa and connected the PC via USB Ethernet Hub.
forum.linuxcnc.org/39-pncconf/52373-pncc...7i76?start=40#299443

please see the experiment I had connected like this until a week ago
forum.linuxcnc.org/39-pncconf/52373-pncc...7i76?start=50#299455

A week ago, however, I cancelled the attempt because, as I wrote, there were problems.
Now the PC has been connected directly to the Mesa 7i92 again for four days and the I-Net runs from the PC via the USB Ethernet adapter to the router.

The 13,566 are therefore generated with the last mentioned configuration
The suggested attempt by PCW

I followed this guide for discovery option. forum.linuxcnc.org/39-pncconf/52554-disc...n-unlisted-mesa-fpga
on readhmid I have:

Configuration Name: HOSTMOT2

General configuration information:

BoardName : MESA7I96
FPGA Size: 20 KGates
FPGA Pins: 256
Number of IO Ports: 3
Width of one I/O port: 17
Clock Low frequency: 100.0000 MHz
Clock High frequency: 200.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256

Modules in configuration:

Module: DPLL
There are 1 of DPLL in configuration
Version: 0
Registers: 7
BaseAddress: 7000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: IOPort
There are 3 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: StepGen
There are 5 of StepGen in configuration
Version: 2
Registers: 10
BaseAddress: 2000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: MuxedQCount
There are 10 of MuxedQCount in configuration
Version: 4
Registers: 5
BaseAddress: 3600
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: MuxedQCountSel
There are 1 of MuxedQCountSel in configuration
Version: 0
Registers: 0
BaseAddress: 0000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: OutM
There are 1 of OutM in configuration
Version: 0
Registers: 1
BaseAddress: B000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: PWM
There are 1 of PWM in configuration
Version: 0
Registers: 5
BaseAddress: 4100
ClockFrequency: 200.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: SSerial
There are 1 of SSerial in configuration
Version: 0
Registers: 6
BaseAddress: 5B00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 64 bytes

Module: SSR
There are 1 of SSR in configuration
Version: 0
Registers: 2
BaseAddress: 7D00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: InM
There are 1 of InM in configuration
Version: 0
Registers: 5
BaseAddress: 8500
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for TB3 -> 7I89
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

TB3-1,2,9,10 0 IOPort InM 0 Input0 (In)
TB3-4,5,12,13 1 IOPort InM 0 Input1 (In)
TB2-7,8,15,16 2 IOPort InM 0 Input2 (In)
TB3-17,18,TB2-1,2 3 IOPort InM 0 Input3 (In)
TB3-20,21,TB2-4,5 4 IOPort InM 0 Input4 (In)
TB3-23,24,TB2-7,8 5 IOPort InM 0 Input5 (In)
TB2-9,10,17,18 6 IOPort InM 0 Input6 (In)
TB2-12,13,20,21 7 IOPort InM 0 Input7 (In)
TB2-15,16,23,24 8 IOPort InM 0 Input8 (In)
TB1-1,2,9,10 9 IOPort InM 0 Input9 (In)
TB1-4,5,12,13 10 IOPort InM 0 Input10 (In)
TB1-7,8,15,16 11 IOPort SSR 0 Out-00 (Out)
Internal-EncMux 12 IOPort SSR 0 Out-01 (Out)
Internal-EncPower 13 IOPort SSR 0 Out-02 (Out)
TB1-19,20 14 IOPort SSR 0 Out-03 (Out)
TB1-21,22 15 IOPort OutM 0 Output4 (Out)
Internal-TXEn 16 IOPort OutM 0 Output5 (Out)

IO Connections for TB1/TB2 -> 7I96_1
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

TB1-2,3 17 IOPort StepGen 0 Step/Table1 (Out)
TB1-4,5 18 IOPort StepGen 0 Dir/Table2 (Out)
TB1-8,9 19 IOPort StepGen 1 Step/Table1 (Out)
TB1-10,11 20 IOPort StepGen 1 Dir/Table2 (Out)
TB1-14,15 21 IOPort StepGen 2 Step/Table1 (Out)
TB1-16,17 22 IOPort StepGen 2 Dir/Table2 (Out)
TB1-20,21 23 IOPort StepGen 3 Step/Table1 (Out)
TB1-22,23 24 IOPort StepGen 3 Dir/Table2 (Out)
TB2-2,3 25 IOPort StepGen 4 Step/Table1 (Out)
TB2-4,5 26 IOPort StepGen 4 Dir/Table2 (Out)
TB2-7,8 27 IOPort MuxedQCount 4 MuxQ-A (In)
TB2-10,11 28 IOPort MuxedQCount 4 MuxQ-B (In)
TB2-13,14 29 IOPort MuxedQCount 4 MuxQ-IDX (In)
TB2-16,17 30 IOPort SSerial 0 RXData0 (In)
TB2-18,19 31 IOPort SSerial 0 TXData0 (Out)
Internal-TXEn 32 IOPort SSerial 0 TXEn0 (Out)
Internal 33 IOPort SSR 0 AC Ref (Out)

IO Connections for P1 -> 7I96_2
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

P1-01/DB25-01 34 IOPort MuxedQCount 0 MuxQ-A (In)
P1-02/DB25-14 35 IOPort MuxedQCount 0 MuxQ-B (In)
P1-03/DB25-02 36 IOPort MuxedQCount 0 MuxQ-IDX (In)
P1-04/DB25-15 37 IOPort MuxedQCount 1 MuxQ-A (In)
P1-05/DB25-03 38 IOPort MuxedQCount 1 MuxQ-B (In)
P1-06/DB25-16 39 IOPort MuxedQCount 1 MuxQ-IDX (In)
P1-07/DB25-04 40 IOPort MuxedQCount 2 MuxQ-A (In)
P1-08/DB25-17 41 IOPort MuxedQCount 2 MuxQ-B (In)
P1-09/DB25-05 42 IOPort MuxedQCount 2 MuxQ-IDX (In)
P1-11/DB25-06 43 IOPort MuxedQCount 3 MuxQ-A (In)
P1-13/DB25-07 44 IOPort MuxedQCount 3 MuxQ-B (In)
P1-15/DB25-08 45 IOPort MuxedQCount 3 MuxQ-IDX (In)
P1-17/DB25-09 46 IOPort MuxedQCountSel 0 MuxSel0 (Out)
P1-19/DB25-10 47 IOPort None
P1-21/DB25-11 48 IOPort SSerial 0 RXData1 (In)
P1-23/DB25-12 49 IOPort SSerial 0 TXData1 (Out)
P1-25/DB25-13 50 IOPort SSerial 0 TXEn1 (Out)


is this normal :
IO Connections for TB3 -> 7I89
IO Connections for TB1/TB2 -> 7I96_1
IO Connections for P1 -> 7I96_2

that should be 7i89 on p1 I think. The discovery option worked and, in pncconf, 7i89 inputs is at P1. I just had some pain to found the input tab of the Help window to paste the 7i96s_7i89d.pin file content. And the channel numbers are a little bit messed up inside each tab. Is there a chance of damaging a pin if there is a mistake in the file made with pncconf ? I will check in the hal file

Maybe this helps:
kcjengr.github.io/probe_basic/quick_start.html

Yep, the fake ones are a pain in ... everywhere.
I'm lucky to have a good reseller nearby, they have never failed to deliver good components during the last ~20 years.

Are you saying that you are using a USB --> Ethernet adapter to connect the the 7I92?
This is never suggested, you should use the motherboard Ethernet to connect the the 7I92
(and use a USB- -> Ethernet adapter if needed for normal internet access)

Ha, I saw someone mention this on the mailing list the other day. Usually I use some bs where I connect the arduino cnc shield to a regular BOB, I think I saw it on V1engineering forum. But since I made a similar board I was gonna do a cheapo one for the stepstick to DB25. 

It seems no problem for a4988/drv8825, but I wasnt sure how it would go with TMC2009 in regards to using 5v and how to do the serial configuration. Personally I wasnt going to add any of the other stuff, but it could be added for pretty cheap. 5 optos and an op amp to do pwm -> analog and a relay. I was also going to just copy the db25 pinout so it could be a standard thing.

... so I'm not offended if your statement concerns me? ;o)

Although I'm usually very precise, I make it easy for myself and make a reference to topics that are already written somewhere. Please also excuse my English - it's not my mother tongue - I run everything I want to write through the translator, otherwise I could never write so much in such a short time, hahaa :o)

Are you saying that you are using a USB --> Ethernet adapter to connect to the 7I92?
if so, this is not likely to work.

Normally you would connect the 7I92 to the motherboard Ethernet port
and if needed, use a USB --> Ethernet adapter for internet access

Yes, I connected the USB Ethernet adapter between the PC and Mesa until the beginning of this week - but in the last few weeks there have been repeated disconnections, first with the Internet, but then also with the Mesa card. So the card no longer responded to the ping. After shutting down and restarting the PC, the connections were restored after a few minutes.

But in this case I have to connect the adapter again and do the same tests as PCW suggested, maybe it will give a better result?

You recommended a Maxwell 5V power supply at the beginning of the thread and I wrote to you that I was already using one which I think delivers 5.06V. I understood your feedback to mean that this is ok?
forum.linuxcnc.org/39-pncconf/52373-pncc...7i76?start=20#298909
Well, I mean the current one is new and if I had to get another one I would buy the same Maxwell again, purely because of the space available. But what does the power supply unit have to do with the 13,566?

Hey, no problem - I wanted to save myself some time and saw my comment as the shortest possible answer. Please don't take it personally, sorry ?
This should not be understood as a reproach. I can only begin to imagine what you do with your support for LinuxCNC, to which I am deeply indebted.
I have also decided that when my machine is running and I return to my usual working environment (CAD/CAM/FEA), I will donate to you who live for Linux ;o)

garja wrote:

Vt-d (Enabled) ==== disable



Package C State Limit (Auto) ===== can this be disabled or turned off?

The active core options I have is All, 1, 2 or 3. Would it help to reduce the number of cores?

Reducing the number of cores might help but would make the PC sluggish to some degree.
You can certainly give it a try and see how it influences latency.

I checked the settings you listed above. I was able to find everything you listed except hyper-threading. Under Advanced; CPU configuration, I only have the following:
Active Processor Cores (All)
Intel Virtualization Technology (Disabled)
Vt-d (Enabled)
Intel Text Support (Disabled)
SW Guard Extensions (Enabled)
Enhanced Speedstep (Enabled)
Turbo Mode (Disabled)
Package C State Limit (Auto)

The active core options I have is All, 1, 2 or 3. Would it help to reduce the number of cores?

PCW wrote:

Repeating a post from a month ago:
 

Ooohh i had that thought on the back of my mind when typing that, just was not sure, hence the sorry there as i was certain i am missing something.
Thank you.
Edited the above post to remove the offending info.

ississ wrote:

I think your suggestion is missing almost a zero at the end to be on the correct scale.
4.7kohm will result in ~1mA base current which is the maximum value for model A, ~8kohm for model B and 17kohm for model C. So a 1kohm is small enough for all models, there is no need to use lower resistor values.

Agreed and correct, thank you.
I went for values that will work in worst case scenarios as the chip market is worse than a minefield, just do a quick search for counterfeit transistor, any transistor, especially the universally used ones.

Dave2024,

Do this in steps:

• Encoder on motor
  • Install encoder
  • Program encoder PPR with AMT software and programming cable.  The USB cable will power the encoder.
    • Determine what the max pulse frequency can be (based on U3k input ceiling and max RPM) and set the encoder PPR to something that gives you a bit of headroom.  1024 or 2048 should be fine, but you may need to go lower if you get some noise.
  • Auto-phase the encoder simulated hall signals
    • Follow the YT videos from AMT/CUI.
    • A 9v battery works well to get one of the phases locked in position.  Just connect one of the 3 wires to 9v+, and another wire to the negative terminal.  The rotor will jump and lock in position.  Disconnect the battery and keep the rotor from turning with a bit of tape or something while you run the AMT auto-phase process.
• Set up U3k to work with encoder & motor (Ultraware)
  • Power up the U3k and connect via Ultraware.  This will allow you to determine (via the diagnostic features) what is causing the status LED's to do what they're doing now (perpetual self-test)
  • You MUST have a 'crossover' cable or crossover adapter to connect the USB to serial cable adapter to the U3k.
    • Search for "DB9 NULL MODEM ADAPTER" on Amazon or similar suppliers
    • Without the crossover you won't be able to connect your PC/Ultraware to the drive, no matter what the COM port settings - period.
  • Use Ultraware to configure motor & encoder parameters
    • Create a new motor project and enter the values from the BLDC data plate.  You will have to guess on some of those (rotor inertia, etc.) since you don't have a detailed datasheet.
  • Verify U3k can 'see' the encoder signals with the ultraware motor monitoring function
    • If the U3k isn't receiving the encoder counts/signals, you can't proceed until you sort this out.
  • Optional - the U3k doesn't need hall signals.  It has an optional mode where on first enable after power-up the drive will wiggle the motor slightly to determine the winding phase(s) relationship to the encoder.  This is sometimes called 'wake & shake' and is used if a motor doesn't have commutation signals.  Search for 'self-sensing' in the Ultraware manual.
• Test the motor/encoder via Ultraware
  • If you've got everything sorted to this point, you can use Ultraware to move the motor in both positioning and velocity modes.
  • You will need to provide full bus voltage to the U3k from this point on.
• Program U3k for use with LCNC
  • Once the motor & U3k are working together you can program the command mode (step & direction) and drive IO signals.  We can go over that stuff in detail once you get there.

tommylight wrote:

ississ wrote:

Simplified:
- logic level low on base (via a resistor): Transistor is "off" and current does not flow from C to E. "The switch is open"
- logic level high on base (via a resistor): Transistor is "on" and current flows from C to E. "The switch is closed"

That is correct and nicely explained, thank you.
And the base of the transistor does need a resistor, something like 100-470 OHm should do just fine, otherwise the base will draw to much current for the PWM output and most probably will not work at all without it.
 

Actually, by looking the BC547 datasheet the minimum current amplification (hfe) is 110 (BC547A), 200 (BC547B), or 420 (BC547C).
Maximum collector current is 100mA so the minimum base current in the worst case (model A, minimum hfe) is 100mA/110 = 0.91mA.
With that base current the transistor is already fully open. Of course there should be a small margin and the resistor size has also some effect on switching speed. So a 1-2mA is normally enough.
The datasheet also lists some values with a base current of 5mA, which is roughly a 1kohm resistor with a 5V drive (calculated worst = 4.1mA).
I think your suggestion is missing almost a zero at the end to be on the correct scale.
4.7kohm will result in ~1mA base current which is the maximum value for model A, ~8kohm for model B and 17kohm for model C. So a 1kohm is small enough for all models, there is no need to use lower resistor values.
And if the load requires a current that is in the transistor limit the transistor should be changed, there should always be some margin... which also affects the base drive needs.
Using a too high base current may even damage the transistor. Calculating the minimum current and using about 2 or 3 times that is usually suitable with these small transistors.