Mesa 7I44-7I70/7I71
26 Jan 2012 09:33 #17150
by Nick
Replied by Nick on topic Re:Mesa 7I44-7I70/7I71
Hi!
Is there any firmware for 5i20 that supports working with resolvers trough 7i49. I saw a lint to one in this thread but it's written that that firmware is only for 5i23.
Is there any firmware for 5i20 that supports working with resolvers trough 7i49. I saw a lint to one in this thread but it's written that that firmware is only for 5i23.
Please Log in or Create an account to join the conversation.
26 Jan 2012 12:34 #17154
by andypugh
Replied by andypugh on topic Re:Mesa 7I44-7I70/7I71
Nick wrote:
Mesa almost certainly have one, but currently there isn't one as part of the default set supplied with LinuxCNC.Is there any firmware for 5i20 that supports working with resolvers
Please Log in or Create an account to join the conversation.
26 Jan 2012 13:06 #17155
by Nick
Replied by Nick on topic Re:Mesa 7I44-7I70/7I71
And unfortunately there's no such firmware at mesanet.com
Please Log in or Create an account to join the conversation.
26 Jan 2012 14:48 #17157
by andypugh
Replied by andypugh on topic Re:Mesa 7I44-7I70/7I71
Nick wrote:
Maybe not in the software pack, but I suspect that they do have one.
In principle you can make your own.
And unfortunately there's no such firmware at mesanet.com
Maybe not in the software pack, but I suspect that they do have one.
In principle you can make your own.
Please Log in or Create an account to join the conversation.
26 Jan 2012 15:42 #17164
by PCW
Replied by PCW on topic Re:Mesa 7I44-7I70/7I71
Unfortunately the 7I49 support firmware will not fit in the 5I20s Spartan 2 FPGA
(and I tried pretty hard)
The current firmware is big because its pretty brute-force (32 bit DSP, table driven waveform generator, Sine lookup table, synchronous DAQ system with double buffered dual ported RAM, 6 channel hardware position integrator etc etc)
It also uses lots of BlockRAMs for code/data/tables/waveform/DAQ, which are in short supply on the 5I20s FPGA. Whats worse, the DSP uses a 16X16 --> 32 hardware multiplier which is free on Spartan 3 and > but needs to be built with logic on the Spartan2
I think the best I ever got trying to make it fit in a 5I20 was 140% of resources
It will not fit in the 7I43-200 either.
Its entirely possible for a smart FPGA jockey to make a more elegant design that fits but its beyond my capabilities at least without months of time to spend on it.
(and I tried pretty hard)
The current firmware is big because its pretty brute-force (32 bit DSP, table driven waveform generator, Sine lookup table, synchronous DAQ system with double buffered dual ported RAM, 6 channel hardware position integrator etc etc)
It also uses lots of BlockRAMs for code/data/tables/waveform/DAQ, which are in short supply on the 5I20s FPGA. Whats worse, the DSP uses a 16X16 --> 32 hardware multiplier which is free on Spartan 3 and > but needs to be built with logic on the Spartan2
I think the best I ever got trying to make it fit in a 5I20 was 140% of resources
It will not fit in the 7I43-200 either.
Its entirely possible for a smart FPGA jockey to make a more elegant design that fits but its beyond my capabilities at least without months of time to spend on it.
Please Log in or Create an account to join the conversation.
27 Jan 2012 19:46 #17201
by Nick
Replied by Nick on topic Re:Mesa 7I44-7I70/7I71
Thanks a lot for detailed answer!!!
Can you advise me about Mesa 7i43+7i39, we've found one firmware, but I'm not sure it works properly.
After doing
halcmd loadrt hm2_7i43 CONFIG="firmware=hm2/7i43-4/SVST4_4_7I39.BIT num_encoders=3 num_3pwmgens=3 num_stepgens=2"
or
halcmd loadrt hm2_7i43 CONFIG="firmware=hm2/7i43-4/SVST4_4_7I39.BIT num_encoders=3 num_pwmgens=3 num_stepgens=2"
we got
RTAPI: ERROR: could not open shared memory (errno=2)
and segmentation error.
As for the firmware we've got it from here comments.gmane.org/gmane.linux.distributions.emc.user/29630
Can you advise me about Mesa 7i43+7i39, we've found one firmware, but I'm not sure it works properly.
After doing
halcmd loadrt hm2_7i43 CONFIG="firmware=hm2/7i43-4/SVST4_4_7I39.BIT num_encoders=3 num_3pwmgens=3 num_stepgens=2"
or
halcmd loadrt hm2_7i43 CONFIG="firmware=hm2/7i43-4/SVST4_4_7I39.BIT num_encoders=3 num_pwmgens=3 num_stepgens=2"
we got
RTAPI: ERROR: could not open shared memory (errno=2)
and segmentation error.
As for the firmware we've got it from here comments.gmane.org/gmane.linux.distributions.emc.user/29630
Please Log in or Create an account to join the conversation.
27 Jan 2012 19:56 - 27 Jan 2012 20:05 #17202
by PCW
Replied by PCW on topic Re:Mesa 7I44-7I70/7I71
Is this LinuxCNC 2.5?
I dont think the three phase PWMgen is supported by earlier versions
dmesg | tail -100 after EMC bails will probably show more diagnostic info
I dont think the three phase PWMgen is supported by earlier versions
dmesg | tail -100 after EMC bails will probably show more diagnostic info
Last edit: 27 Jan 2012 20:05 by PCW. Reason: command line error
Please Log in or Create an account to join the conversation.
27 Jan 2012 21:08 #17204
by Nick
Replied by Nick on topic Re:Mesa 7I44-7I70/7I71
Yep, it's 2.5 moreover we've tried 2.6. With same results.
I'll try to get dmesg output...
I'll try to get dmesg output...
Please Log in or Create an account to join the conversation.
28 Jan 2012 12:35 #17223
by Nick
Replied by Nick on topic Re:Mesa 7I44-7I70/7I71
after appling /etc/init.d/realtime start
we got this:
gena@gena-desktop:~$
we got this:
gena@gena-desktop:~$ sudo /etc/init.d/realtime start
[sudo] password for gena:
gena@gena-desktop:~$ halcmd loadrt hm2_7i43 CONFIG="firmware=hm2/7i43-4/SVST4_4_7I39.BIT num_encoders=3 num_3pwmgens=3 num_stepgens=2"
insmod: error inserting '/usr/realtime-2.6.32-122-rtai/modules/emc2/hm2_7i43.ko': -1 Unknown symbol in module
<commandline>:0: exit value: 1
<commandline>:0: insmod failed, returned -1
See the output of 'dmesg' for more information.
gena@gena-desktop:~$[ 94.980624] I-pipe: Domain RTAI registered.
[ 94.980643] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 94.980650] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) .
[ 94.980764] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
[ 94.980771] PIPELINE layers:
[ 94.980780] f8c11e20 9ac15d93 RTAI 200
[ 94.980787] c085cb20 0 Linux 100
[ 95.030826] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 95.031406] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <with RTAI OWN KTASKs>, kstacks pool size = 524288 bytes.
[ 95.031418] RTAI[sched]: hard timer type/freq = APIC/12500388(Hz); default timing: periodic; linear timed lists.
[ 95.031425] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 1799956000 hz.
[ 95.031430] RTAI[sched]: timer setup = 999 ns, resched latency = 2944 ns.
[ 95.031558] RTAI[usi]: enabled.
[ 95.658919] RTAI[math]: loaded.
[ 242.775976] hm2_7i43: Unknown symbol hm2_register
[ 242.777333] hm2_7i43: Unknown symbol hm2_unregister
[ 414.789699] hm2_7i43: Unknown symbol hm2_register
[ 414.790986] hm2_7i43: Unknown symbol hm2_unregister
[ 640.913148] hm2_7i43: Unknown symbol hm2_register
[ 640.914434] hm2_7i43: Unknown symbol hm2_unregister
[ 684.829110] hm2_7i43: Unknown symbol hm2_register
[ 684.830460] hm2_7i43: Unknown symbol hm2_unregister
[ 738.350656] hm2_7i43: Unknown symbol hm2_register
[ 738.351943] hm2_7i43: Unknown symbol hm2_unregister
[ 1081.514359] hm2_7i43: Unknown symbol hm2_register
[ 1081.515646] hm2_7i43: Unknown symbol hm2_unregisterPlease Log in or Create an account to join the conversation.
28 Jan 2012 15:53 #17235
by PCW
Replied by PCW on topic Re:Mesa 7I44-7I70/7I71
Is there some reason you are not simply running emc (LinuxCNC) from the command line?
I would first either install EMC2.5 or 2.6 or compile and run-in-place (remembering to set the run-in-place environment so you actually get 2.5/2.6) Then check that the sample 7I43 configs launch properly
If this works ok I would make a new config from the sample config. changing only the firmware
load line so the new firmware is loaded (but delete all the encoder/stepgen/pwmgen info on the load line so all modules are automaticaly enabled)
I would first either install EMC2.5 or 2.6 or compile and run-in-place (remembering to set the run-in-place environment so you actually get 2.5/2.6) Then check that the sample 7I43 configs launch properly
If this works ok I would make a new config from the sample config. changing only the firmware
load line so the new firmware is loaded (but delete all the encoder/stepgen/pwmgen info on the load line so all modules are automaticaly enabled)
Please Log in or Create an account to join the conversation.
Time to create page: 0.316 seconds