Advanced Search

Oh, can't believe I hadn't even searched for Syntec here.
I have literally spent the last week looking for used SK panels and trying to figure out what's what with them.I would be very, very interested in hearing more about your exact board and what's underneath your Arduino and next to it.  
Now, feel free to skip to the bottom as next I was asking questions that you have actually answered already - I just didn't know enough to realize:)

Skip From Here...
Newer SK panels have a small "matrix chip" surface mounted to the button side of the PCB (just inbetween button switches), older ones have a larger one on the backside (often a Holtek) and even older ones have a whole daughter board attached to the back side with a what Syntec calls a "decoder module". I always assumed the chip would spit out a proprietary serial link. I had no idea they were talking PS/2... Well, I thought perhaps the older ones were based on the Holtek model numbers.

But I have been trying to avoid newer boards because I wanted easy access to the matrix. I also had no idea the matrix is actually availble on the "HK Connector" - but that's how it looks from your picture. It looks like the Arduino is connecting to the HK. Or is the HK sending out PS/2 to your arduino? In which case your panel must indeed still have a "matrix chip somewhere" and your Arduino turns PS/2 into USB? 

Also, how do you control the button LEDs? 

If you could find time to share some more on how you made this work, I would be very grateful. I would mostly likely go this way as apart from ideally wanting more overide knobs, the SK4/6M panels have a really nice set of control buttons - plus the alphanumeric keys, too.

On a related note - as for turning the matrix into USB, when I asked AI about how to hack older SK panels it suggested this approach but to also make a combo USB protocol of HID plus a gamepad or joystick library. That way, supposedly, when doing the HAL connections you don't have to venture into weird combo USB presses to map the buttons that HID has no library for. So, you'd use HID for the regular stuff it already has and then gamepad library for everything "CNC" and it would just be passed through as button 1, button 2, etc. 

Also, I did talk to a Chinese vendor had to check back with the factory on the protocols and how open they actually are but between the language barrier and me only wanting to buy one, he kinda lost interest, haha. But I think he said they could deliver bare matrix, USB-HID and more.  

Skip To Here:)
[EDIT] I really should learn to read. You specifically explained the SK panel does both PS/2 and matrix. So, now I think the PS/2 signal may be coming into your arduino from that 5 pin connector in the corner of the board that says "to keyboard" and the matrix comes out of the HK Connector. Also, you even said the matrix is shared for both buttons and LEDs. So, there we have it:) What wonderful detective work you have done to make these panels work! 
So... would you be inclined to share the code and pin mapping to help others along:)? 


 

The only time I've used SDO's is to configure the drive. Maybe your drive does not need any configuration.
SDO's are not required to use cia402 commands

does lcec_configgen create a XML file?

First the Linuxcnc version you quote is invalid. What is it really?
Second, 256  is a very signiicant number for computers because an 8 bit number (1 byte) counts from 0-255 which a computer's way of counting from 1-256.
The  G54 values are stored in the var file. I could not see exactly what us the varibale number on a quick look. I would check this after you close to make sure its not being incremented on close,

My guess is that Linuxcnc will be OK but somehow outside of LinuxCNC, your encoder value is incremented by 1 X  8 bit byte.

Hi there.

When choosing the PROBE tab with the file in the indicated directory, a pop-up window comes with this error:
"Traceback (most recent call last):
File "/usr/share/qtvcp/screens/qtdragon_hd/qtdragon_hd_handler.py", line 626, in main_tab_changed
self.adjust_stacked_widgets(index)
File "/home/izan/linuxcnc/configs/QtDragon/qtvcp/screens/qtdragon_hd/qtdragon_hd_handler.py", line 126, in adjust_stacked_widgets
self.w.setCurrentIndex(num)
~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 493, in __getitem__
return getattr(self, item)
^^^^^^^^^^^^^^^^^^^
AttributeError: 'VCPWindow' object has no attribute 'dro_button_stack_4' "

(Attached the report)

In the other hand, I´ve set 99 tool number to probe, and after running a program if I go to TOOL tab, select it and push the M61 button to choose, it runs pretty good despite the down yellow line appears with the "cannot switch pages while in AUTO mode"

that is essentially the commands Ive been trying.

below shows the error that keeps cropping up

i havn't been able to manually find a matching header either,  only some very close but older revisions and i dont know enough about linux to go about building it up to suit the above revision, or if thats even something that could be done.
 

It is Qtdragon_hd, that's right.
I will try along the day and feedback.

-the thing with C axis going from approx. 110 to -280 in about 10 lines of gcode does not seem OK

sounds like you might have downloaded the first version of the filter script which I modified shortly after posting to fix exactly this issue. So make sure you use the current one with the transition handling:


I have tested this with all three {1,2,3}.pts files and the result looks fine to me. (The C axis values never goes negative)

Attached are the Python files that I modified for my M6 remap with auto-tool measurement.  My changes are tagged with "JHK".
Enjoy
John 

Almost forgot, also swapped in hal the X and Z axis, so now if you turn the machine on the left side it is exactly as in the Vismach preview, and set the ini for A axis to home at 90, so i do not have to do that at every start.

Yeah, not really that easy though, I'm really going to have to write one so it's more like an easy to write cycle on the machine. Like a conversational control.

Ok here is the right file for 2.9 version.

As for the other error, set a probe tool number on the probe page - it defaults to black which won't be read correctly.

hold on I did it for the wrong version of linuxcnc... stay tuned

I assume you are using qtdragon_hd:
Ok in your config folder there should be a folder: qtvcp/screens/qtdragon_hd
In that folder add the file included here, name it qtdragon_hd_handler.py
Then run as normal.
If any thing goes wrong just remove or rename the file.

Chris

i believe all non-cnc encoders (OSA/OBA 14,17,18,24) answer on both MR and MD pairs simultaneously. OSA253/104/105 only answer on MD so you need to use 4 wire connection with them.

I've made my own motordrive and used the Mitubishi encoders extensively.
I have tested several motors, from the MR-PQ, MR-MFS, MR_SFS and MR-KP
series. They all seem to use the same protocol and checksum. Some types
use full-duplex communication and others use a single bi-directional
version.

From what I have seen, it is important to poll the motor at a fixed
frequency of 4.5kHz.

My source code is available at:

github.com/mark-v-d/motor_control/blob/h...4400/src/encoder.cpp

The class mitsubishi_PQ_t is the full-duplex version of the protocol,
and mitsubishi_MFS13_t is the half-duplex implementation.

Basically start sending 0x1a at 2.5Mb/s at 4.5kHz and the encoder starts
responding. There is a checksum at the end of the packet.