Advanced Search

Not my stuff.
Very detailed modeling and sketching tutorial for FreeCAD version 1.1 to full dimensionaly accurate 3D model.
All credits go to DeltaHedra on youtube.

Quite a few people have used 500 Hz servo thread instead of normal 1000 Hz on Raspberry Pi etc so I wonder how much of a difference it really makes? Ethercat would still be doing its thing internally. You'd have to test.

Not just in the states but to governments the world over in general.

What does it mean to set sync0 Cycle="*2"?
Should it be set for every drive?

I think that with a value of 2, instead of the default 1, the drive updates the PDOs after two master cycles. If so, I don't know if this is correct for machines that need to interpolate; it would be better to be faster.

It would just be a way to avoid the problem we're trying to solve.

Indeed, those functions do appear in the Qtdragon version, and it also automatically switches from Manual to MDI, but the problem of not finding the Oword route persists. This was also updated in Qtdragon HD, but not in Qtdragon HD. I thought they were the same, but now I realize they are different projects.

That sounds like the noise produced when synchronization is lost during motion. My solution was to change the parameters to `refClockSyncCycles="-1" sync0Cycle="*2"`. After making this adjustment, I no longer experienced any synchronization loss. I am using an Inovance SV660N drive. You can also add the following line to the XML configuration to monitor the number of synchronization loss events: `<pdoEntry idx="200e" subIdx="19" bitLen="16" halPin="SyncLossCount" halType="s32" />`.


The entry `<pdoEntry idx="200e" subIdx="19" bitLen="16" halPin="SyncLossCount" halType="s32" />` is effective only for Inovance SV series drives; it cannot be used with other drive models.

There seems to be a misunderstanding; I don't think I've been clear. I'm using a QTDragon HD, and this screen is also from QTDragon. I don't know if that has anything to do with the problem.

Sometimes if you have to run master branch, its so much easier to learn to build from source. The docs are now pretty good with this.
a run in place version can be updated to todays latest just by doing
git pull
make
sudo make setuid

and it often only takes a few seconds

Does the settings page look like this?

 

Yup. Ran that and variants like it many times. It would say something along the lines of: 0 updates available 0 updates installed 2 not updated. I couldn't find out why it wouldn't upgrade it.
I tried:
"sudo apt update
sudo apt full-upgrade"
Then I tried:
"sudo apt purge --autoremove raspi-firmware
sudo apt update
sudo apt upgrade"
Gave me another error.
Then I went went into Synaptic, I reloaded "linuxcnc", marked the new version for upgrade, and then clicked apply. It gave me yet another error.
During a cursory search of the internet and that's when I learned that it's most likely due to an outdated repository link.
Then I asked here about finding a good repository address.
In the meanwhile I tried several different addresses from internet searches, tried them and all gave me errors.
Check back, found the post was moved and had no replies.
I used balena etcher, backed up the entire drive image just in case what I wanted to try didn't work, made copies of the INI and HAL files and their respective backups, loaded up a fresh linuxcnc to a bootable drive, used the installation to wipe the partition and installed it fresh.
Other than the new version being picky about what letters were capitalized in the name of the HAL file, and a couple of minor tweaks in Debian including reinstalling the Etouch driver so the touchscreen drivers would install, everything seems to be working fine now.

I'll swap them both and see if that solves the problem. Otherwise, it'll be difficult.

That makes sense, the 75175 is likely the differential encoder input circuit
and the 75174 is used for an emulated encoder output or some such...

 

I traced the path on the circuit board a bit and came across the following two components: 75174N-H and SN75175N.

Unfortunately, during testing yesterday, we blew out one of the outputs.

Ouch!

A bit late, but one trick is when testing, to have a say 470 Ohm resistor in series with the +24V used for
sensing the output, that way the current is limited to ~50 mA in the event of a wrong connection.

What chip does the encoder input use? If it's differential it may be something common like a 26LS32

 

Thank you very much for your help. Your description provided the solution!
Unfortunately, during testing yesterday, we blew out one of the outputs. I have already ordered a new optocoupler. I also have a second inverter, but it has a fault at the encoder input, as the signal is not being detected. I installed this circuit board and on that board, the output switches correctly as well.

Perhaps someone here is familiar with the Yaskawa board. There must be a defective component somewhere on the board preventing the encoder signal from being processed. The encoder input is connector 2CN.