You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/PROG test
/ATTR
COMMENT = "Test";
DEFAULT_GROUP = 1,*,*,*,*;
/MN
: ! test ;
: UFRAME_NUM=0 ;
: UTOOL_NUM=1 ;
: L P{test} 100mm/sec CNT0 ;
/POS
${FEXCEL_POSITIONS}
/END
Fexcel would automatically number positions and output the correct data in the /POS section.
e.g.
P[1:"test"]{
GP1:
UF : 0, UT : 1, CONFIG : 'N U T, 0, 0, 0',
X = 1592.000 mm, Y = 0.000 mm, Z = 1085.000 mm,
W = -180.000 deg, P = .000 deg, R = 0.000 deg
};
Could potentially support multi-group down the road, but let's assume GP1 for now... cartesian positions only.
It would be cool if fexcel could update the position data from a robot host/backup as well.
Fexcel would then have to grab all the TP/LS files on the target, parse them for position data, and write them to the provided sheet/cell. Would require adding program/position support to onerobotics/go-fanuc.
The text was updated successfully, but these errors were encountered:
I actually worked on this a bit, and I like storing position data outside of my programs, but I don't think the excel spreadsheet is the best place for it. Among other issues, I can't see the changes via git diff without some sort of git extension.
regardless of where position data is stored, fexcel must support updating the position data from a remote or file backup target. updating by hand is no good.
I hate maintaining position data within TP programs. The fexcel compiler should take care of it for me.
> fexcel compile spreadsheet.xlsx test.ls --positions SomeSheet:A2
Then within the TP program something like:
Fexcel would automatically number positions and output the correct data in the
/POS
section.e.g.
It would be cool if fexcel could update the position data from a robot host/backup as well.
> fexcel positions:update spreadsheet.xlsx 127.0.0.1 SomeSheet:A2
Fexcel would then have to grab all the TP/LS files on the target, parse them for position data, and write them to the provided sheet/cell. Would require adding program/position support to onerobotics/go-fanuc.
The text was updated successfully, but these errors were encountered: