Advanced Search

Traj section in the ini file, velocities are much lower than in the display section, try setting those same as display section.

Now, after the first start of the generator, a file is created:

riocore/toolchains.json

there you can enter the paths to your toolchains, these are then transferred to the makefile.

under windows please note that backslashes must be double

 

so you do not need to add the toolchains to your enviroment variables
 

Now i am quickly getting out of my depth, It looks like you maybe missing the link to the XML file in your hal? as you are not showing the EK1100 in the list of Pins.

do you have something similar to
loadusr -W lcec_conf ethercat-conf.xml

You also seem to be missing the Readall / writeall for lcec can you post your hal?

In your xml? and when you start from the cmdline are you getting any errors?

 

 

substituted with cam_align.ui and cam_align_handler.py from github source shows nicely that the correction works perfectly

thank you, Chris
 

So not that long ago FreeCAD V0.22 AKA V1.0 was released.as the stable version. I have been using Autodesk Fusion 360.
for years now and for the most part it works fine. That said with Windows 10 being EOL this coming October and Fusion 360
not officially released for Linux ( plus all the B.S. with Win.11 NO THANK YOU! )  I started fumbling my way around FreeCAD.
I have played with the program in the past V0.19, V0.20, V0.21 but no real motivation to truly learn it. Going from one to the
other definitely has a learning curve. How about everyone else what has been your experience using the new FreeCAD?

Thank you for your reply. Then I should have an issue with my config I guess

here is my result of ethercat slaves:

0 0:0 PREOP + EK1100 EtherCAT-Koppler (2A E-Bus)
1 0:1 PREOP + EL2008 8K. Dig. Ausgang 24V, 0.5A
2 0:2 PREOP + EL1008 8K. Dig. Eingang 24V, 3ms
3 0:3 PREOP + EL1018 8K. Dig. Eingang 24V, 10�s

my xml file is attached

and a print screen of what I have in Hal show. My pins are not visible
 

Hi Tommy
This is my ini file .

i have removed the IO_TYPE from the cst pinfile generation,
you need to checkout the newest dev branch and generate the files new

Ups, I have just seen the correct IO standard can be configured /edit in the plugin of the blink module in the riocore software. Hence, it is not necessary to do it manually in the pins.cst file.

have tried to get linuxcnc from buildbot 
... any such change will see no buildbot to help, or that help is delayed ... 
so I have to build LinuxCNC from source

   


qtvcp_panel_preferences already work perfectly here 

 

I did not know about the LED on the FPGA board. Now it makes sense.

However, as the bank 3 of the FPGA is powered by 1.8V, the IO_TYPE should not be LVCMO33, which is in conflict with the power of bank 3 causing an error during place & route.

I have not tried the toolchain of the riocore, as Compile does not work with my Windows setup. I may look into it later as I can live with the Gowin IDE.

File pins.cst:

// ### blink3 ###
IO_LOC "PINOUT_BLINK3_LED" 10;
IO_PORT "PINOUT_BLINK3_LED" IO_TYPE=LVCMOS33 DRIVE=8;

IO_TYPE=LVCMOS18 solves the problem.

Pins of bank 3 are 3 to 11, 13 to 16 and 79 - 88 (some of the pins are used for the right sight of the board)

Just for the case that somebody else uses the IDE....

If you create a component (called comp, with a float pin named length) in your script, you can use this for the box:

Box(comp, 60, -30, -30, 'length', 30, 30)

or with no component in the script this should work:
Box(60, -30, -30, 'comp_name.length', 30, 30)

All the other entries can use a string to force evaluation of a HAL pin too.

Chris

Spammer and their post removed.