Advanced Search

Thanks Greg, I've beem away for years and find a bug in 5 minutes 
In this case the the config to upgrade was nothing more than a sim!
Issues:

1. The m_files folder was in ~/linuxcnc/nc_files/examples/plasmac, copied it into ~/linuxcnc/nc_files
2. The files in the m_files folder under examples were owned by root and the user did not have permissions to the M codes
3. The INI M_CODE variable in the ini file was not updated in qtplasmac_metric_ini.inc. I suspect this was because its not the top level ini file (I'm not sure if you actually write to that folder)
4. The error message should refer to plasmac so the user knows its specific to Plasmac. I had to deduce that by checking other configs
5. The version number reported does not reconcile with the version details displayed on startup 2.10.0-pre-4165-xxxxxxxxxxxxxxxx
6. Let me introduce you to Python try/except error handling www.w3schools.com/python/python_try_except.asp This would ensure the user is less bewildered when it  fails. There is nothing displayed on the screen when it fails
7. Perhaps the message could be a little more specific eg "updating qtplasmac mcode folder"
8. Perhaps the upgrade message could also be printed on the console. Displaying Top right when console is in bottom left meant I did not even see the error the first couple of times!

I might add Joco is also in trouble over this for adding these gcodes!   

rodw wrote:

Snowgoer

Greg … just in case you somehow missed it after all these years

rodw wrote:

Can Phill or Snowgoer have a look at this issue?

That particular message is to let you know your config has been update to 001.017, and that you need to restart for things to take effect.

If you are seeing it repeatedly, seeing you had a permissions issue in another post, I’d guess you still have some permissions issue(s) going on.

Otherwise if you wanted to zip your config and post it here, I’ll try to make time to take a look.

In particular, that update is looking for 'nc_files/plasmac/m_files' in your USER_M_PATH, to be able to see the Mxxx files. It’s not seeing it so it’s trying to update the ini file to fix it.

Awesome advice! Thank you for the guidance - it's exactly what I needed!

OK, so the cute little Atom board is a no-go. I also have a Supermicro board laying around, with a 6-core Opteron on it. I figured it was overkill - but apparently not!

Yes, Pico Systems' boards are parallel port. However, they are not like typical parallel port breakout boards. They are more like Mesa boards - where the processing occurs on the board. Given the fact that Jon is one of the "OGs" of the LinuxCNC world and happens to be local to me, I've debated about whether to go with the standard Mesa board or a board that might come with more personalized service from the engineer who designed it. I don't want to spend a money on stuff that's already outdated, though.

I will reach out to Mesa, and see what they have to say. Their site has a lot of technical information about their boards, but it's difficult for a "newbie" to interpret.

I was hoping you would say that about a touchscreen. That will make the system a lot "cleaner." Having a wireless keyboard tucked away is a great compromise.

Just email This email address is being protected from spambots. You need JavaScript enabled to view it. with your address and request
and we can put a couple in an envelope.

Encoder 2 on the 7i85S is used for the spindle and is actually single-ended, but it's still working fine. So I guess I’ve been lucky there, considering the damage on the board.

I’d really appreciate it if I could get two replacement chips, if it’s possible to have them shipped to Germany.
-
Max

I meant the BOM for the missing parts. As in all motors, controller boards, cables, router spindel etc.
Might need quite some help with that, I guess

As for the weight, they seem to got there a bit of mixup, I guess the apprentice maintaining the site, missed some spots after c&p . IN the end, it will be delivered on a palette anyways..

Sadly the german punctuality has gone big style (the trains are 70% in time at best), but in exchange we got even more bureaucracy.

BUT!!! metric system!

For the parallel port output pins 4 and 5, you would first check
the pinout as  shown previously, this shows that DB25 pin 4 is GPIO 47
and that DB25 pin 5 is GPIO 49

PIN                             GPIO
P1-01/DB25-01          41   IOPort             
P1-02/DB25-14          42   IOPort          
P1-03/DB25-02          43   IOPort       
P1-04/DB25-15          44   IOPort     
P1-05/DB25-03          45   IOPort 
P1-06/DB25-16          46   IOPort     
P1-07/DB25-04          47   IOPort         
P1-08/DB25-17          48   IOPort         
P1-09/DB25-05          49   IOPort    

so

net spindle-cw      => parport.0.pin-05-out
net spindle-ccw     => parport.0.pin-04-out

become

net spindle-cw      => hm2_7i95.0.gpio.049.out
net spindle-ccw     => hm2_7i95.0.gpio.047.out

But there is one more step needed, because GPIO bits default to inputs at startup,
you must set these GPIO pins to output mode:

setp hm2_7i96s.0.gpio.049.is_output true
setp hm2_7i96s.0.gpio.047.is_output true

As far as the connections below  go, they are no longer relevant,
because both the PWMgen generation and encoder counting would likely
be done in hardware:

net spindle-pwm     => parport.0.pin-01-out

net spindle-phase-a <= parport.0.pin-10-in
net spindle-index   <= parport.0.pin-12-in

Note that this will only work on stock 7i95t firmware or 7i95t_5abob firmware
if you disable the stepgens on DB25 pins 4,5 and on.



 

I am a slow learner... yes, the plug was the problem....

 

One phase disconnected, but loosely held in contact by the wire. I cut off the old ferrule, reterminated it with a new ferrule and now the machine is getting all phases.

It is still not clear to me whether this 7i84 can be saved with replacement NCV7608s or whether it is trash.

 

I will order a 7i84u for the Maho, but if this 7i84 can be rescued, I would use it in the Schaublin, where I ran out of 24V outputs, and bodged switching chinese relay boards with 5V outputs.

I'm not really surprised that this isn't related to my file, as I created it the same way I always do. I finally got it to load, but I'm not sure how. I tried kernels 6.1.0-28 and 6.1.0-32. I also tried 2.9.4-19-gd3a1da65b7, same result as with 2.10.0-pre0.
Now I have the same issue with the next file.

I will try on another hardware

Hi

Attaching the hal file I used with parallel port.
Please guide how I can connect the  spindle and encoder on the 5ABOB with 7i95t board. Upon checking pin file I can see PWM on pin ! and pin 4 (Step) and pin 5 (Direction)  and inputs on 10 and 12 pins for 5ABoB for the 7i95t mesa board, 

addf pwmgen.update servo-thread

addf abs.0 servo-thread
addf scale.0 servo-thread
addf lowpass.0 servo-thread
addf near.0 servo-thread

net spindle-cmd-rpm => pwmgen.0.value
net spindle-on <= spindle.0.on => pwmgen.0.enable
net spindle-pwm <= pwmgen.0.pwm
setp pwmgen.0.pwm-freq 100.0
setp pwmgen.0.scale 238
setp pwmgen.0.offset 0.01
setp pwmgen.0.dither-pwm true
net spindle-cmd-rpm     <= spindle.0.speed-out
net spindle-cmd-rpm-abs <= spindle.0.speed-out-abs
net spindle-cmd-rps     <= spindle.0.speed-out-rps
net spindle-cmd-rps-abs <= spindle.0.speed-out-rps-abs
net spindle-at-speed    => spindle.0.at-speed
net spindle-cw <= spindle.0.forward
net spindle-ccw <= spindle.0.reverse

setp encoder.0.position-scale 1000
setp encoder.0.counter-mode 1
net spindle-position encoder.0.position => spindle.0.revs
net spindle-velocity-feedback-rps encoder.0.velocity => spindle.0.speed-in
net spindle-index-enable encoder.0.index-enable <=> spindle.0.index-enable
net spindle-phase-a encoder.0.phase-A
net spindle-phase-b encoder.0.phase-B
net spindle-index encoder.0.phase-Z

net spindle-cmd => near.0.in1
net spindle-velocity => near.0.in2
net spindle-at-speed spindle.0.at-speed <= near.0.out
setp near.0.scale 1.01



net spindle-cw      => parport.0.pin-05-out
net spindle-ccw     => parport.0.pin-04-out
net spindle-pwm     => parport.0.pin-01-out

net spindle-phase-a <= parport.0.pin-10-in
net spindle-index   <= parport.0.pin-12-in

Please help!

It is a CEE 16A five pin. No changes on the wall, socket or cable. The MAHO has been working without wiring change from this socket for about 6 years.

Yes, neutral is wired in, but unused by the machine. Since the original Phillips PC used 110VAC generated by the 6T1, I wired the LinuxCNC PC and monitor into the same service.

Okay, this got weirder. I just went down to the machine,  manually switched off 1Q1 (I misunderstood that as Q1), plugged in and switched the machine on (with Q1, the main power switch), and PC powered up normally. Switched Q1off, reset 1Q1 to on, switched the machine on again, and it again powered up the PC normally. measured 114VAC between pins 150/151.  I could see from the Mesa LED's that the 24VDC rail 204 was also powered. I changed nothing other than waiting a couple of hours and plugging / unplugging the socket a couple of times.

Writing this, I just realised I need to open up that CEE plug on the machine cable, and see if I have a loose connection in there.

That wire is on a 5V regulator pin, so maybe related, hard to tell.

Yes, NCV7608s are obsolete, we do have spares if you need a few.

Thanks, Tommy.
The shop is heated and very dry, especially during the German winter, so moisture is probably not the issue.
-
Max

Picture 2, that looks like arcing across those two parts, moisture can do that, but the rest of the boards look like there is no moisture in quantities to cause that.